Filesystem problem with Lenovo 310
I have installed Ubuntu 18.04 in a Lenovo 310 and I have some problems after some time (the problem usually happens after watching flash videos on the browser) the filesystem gets read-only. For instance when I try to do ls, the following error appears:
bash: cannot create temp file for here-document: Read-only file system
and with dmesg I find the following:
[ 1113.452578] mmc1: mmc_hs400_to_hs200 failed, error -110
[ 1113.452615] mmcblk1: timed out sending r/w cmd command, card status 0x400e00
[ 1113.452617] mmcblk1: command error, retrying timeout
[ 1113.452908] mmc1: mmc_hs400_to_hs200 failed, error -110
[ 1113.452931] mmcblk1: timed out sending r/w cmd command, card status 0x400e00
[ 1113.452933] mmcblk1: command error, retrying timeout
[ 1123.552180] mmc1: Timeout waiting for hardware interrupt.
[ 1123.552209] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 1123.552216] mmc1: sdhci: Sys addr: 0x20000008 | Version: 0x00001002
[ 1123.552223] mmc1: sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008
[ 1123.552229] mmc1: sdhci: Argument: 0x02400988 | Trn mode: 0x0000002b
[ 1123.552235] mmc1: sdhci: Present: 0x1fff0001 | Host ctl: 0x0000003d
[ 1123.552241] mmc1: sdhci: Power: 0x0000000b | Blk gap: 0x00000080
[ 1123.552248] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x00000207
[ 1123.552254] mmc1: sdhci: Timeout: 0x00000006 | Int stat: 0x00000000
[ 1123.552260] mmc1: sdhci: Int enab: 0x02ff000b | Sig enab: 0x02ff000b
[ 1123.552266] mmc1: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 1123.552272] mmc1: sdhci: Caps: 0x546ec881 | Caps_1: 0x80000807
[ 1123.552278] mmc1: sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
[ 1123.552285] mmc1: sdhci: Resp[0]: 0x00400e00 | Resp[1]: 0x00000000
[ 1123.552291] mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00400e00
[ 1123.552296] mmc1: sdhci: Host ctl2: 0x0000000d
[ 1123.552303] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x000000016f310200
[ 1123.552306] mmc1: sdhci: ============================================
[ 1123.552579] mmcblk1: error -110 sending stop command, original cmd response 0x0, card status 0x400900
[ 1123.552619] mmcblk1: error -110 transferring data, sector 37751176, nr 8, cmd response 0x0, card status 0x0
When I reboot, there is a terminal telling me to run fsck and after doing that and rebooting again the system is again fine (for a while).
I have read that this might be a kernel problem, but that might be also be a problem with my hardware.
Could someone help me to discover which is the problem? Which log information can I provide to clarify this?
filesystem lenovo emmc
add a comment |
I have installed Ubuntu 18.04 in a Lenovo 310 and I have some problems after some time (the problem usually happens after watching flash videos on the browser) the filesystem gets read-only. For instance when I try to do ls, the following error appears:
bash: cannot create temp file for here-document: Read-only file system
and with dmesg I find the following:
[ 1113.452578] mmc1: mmc_hs400_to_hs200 failed, error -110
[ 1113.452615] mmcblk1: timed out sending r/w cmd command, card status 0x400e00
[ 1113.452617] mmcblk1: command error, retrying timeout
[ 1113.452908] mmc1: mmc_hs400_to_hs200 failed, error -110
[ 1113.452931] mmcblk1: timed out sending r/w cmd command, card status 0x400e00
[ 1113.452933] mmcblk1: command error, retrying timeout
[ 1123.552180] mmc1: Timeout waiting for hardware interrupt.
[ 1123.552209] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 1123.552216] mmc1: sdhci: Sys addr: 0x20000008 | Version: 0x00001002
[ 1123.552223] mmc1: sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008
[ 1123.552229] mmc1: sdhci: Argument: 0x02400988 | Trn mode: 0x0000002b
[ 1123.552235] mmc1: sdhci: Present: 0x1fff0001 | Host ctl: 0x0000003d
[ 1123.552241] mmc1: sdhci: Power: 0x0000000b | Blk gap: 0x00000080
[ 1123.552248] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x00000207
[ 1123.552254] mmc1: sdhci: Timeout: 0x00000006 | Int stat: 0x00000000
[ 1123.552260] mmc1: sdhci: Int enab: 0x02ff000b | Sig enab: 0x02ff000b
[ 1123.552266] mmc1: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 1123.552272] mmc1: sdhci: Caps: 0x546ec881 | Caps_1: 0x80000807
[ 1123.552278] mmc1: sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
[ 1123.552285] mmc1: sdhci: Resp[0]: 0x00400e00 | Resp[1]: 0x00000000
[ 1123.552291] mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00400e00
[ 1123.552296] mmc1: sdhci: Host ctl2: 0x0000000d
[ 1123.552303] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x000000016f310200
[ 1123.552306] mmc1: sdhci: ============================================
[ 1123.552579] mmcblk1: error -110 sending stop command, original cmd response 0x0, card status 0x400900
[ 1123.552619] mmcblk1: error -110 transferring data, sector 37751176, nr 8, cmd response 0x0, card status 0x0
When I reboot, there is a terminal telling me to run fsck and after doing that and rebooting again the system is again fine (for a while).
I have read that this might be a kernel problem, but that might be also be a problem with my hardware.
Could someone help me to discover which is the problem? Which log information can I provide to clarify this?
filesystem lenovo emmc
2
check the output ofdmesg
for error messages regarding the disk subsystem
– Sebastian Stark
Jun 11 at 17:53
I have installed it in an eMMC (in Lenovo Yoga 310).
– Alex Grilo
Jun 13 at 12:23
Only half the bounty??? What happened?
– Fabby
Jun 22 at 19:08
add a comment |
I have installed Ubuntu 18.04 in a Lenovo 310 and I have some problems after some time (the problem usually happens after watching flash videos on the browser) the filesystem gets read-only. For instance when I try to do ls, the following error appears:
bash: cannot create temp file for here-document: Read-only file system
and with dmesg I find the following:
[ 1113.452578] mmc1: mmc_hs400_to_hs200 failed, error -110
[ 1113.452615] mmcblk1: timed out sending r/w cmd command, card status 0x400e00
[ 1113.452617] mmcblk1: command error, retrying timeout
[ 1113.452908] mmc1: mmc_hs400_to_hs200 failed, error -110
[ 1113.452931] mmcblk1: timed out sending r/w cmd command, card status 0x400e00
[ 1113.452933] mmcblk1: command error, retrying timeout
[ 1123.552180] mmc1: Timeout waiting for hardware interrupt.
[ 1123.552209] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 1123.552216] mmc1: sdhci: Sys addr: 0x20000008 | Version: 0x00001002
[ 1123.552223] mmc1: sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008
[ 1123.552229] mmc1: sdhci: Argument: 0x02400988 | Trn mode: 0x0000002b
[ 1123.552235] mmc1: sdhci: Present: 0x1fff0001 | Host ctl: 0x0000003d
[ 1123.552241] mmc1: sdhci: Power: 0x0000000b | Blk gap: 0x00000080
[ 1123.552248] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x00000207
[ 1123.552254] mmc1: sdhci: Timeout: 0x00000006 | Int stat: 0x00000000
[ 1123.552260] mmc1: sdhci: Int enab: 0x02ff000b | Sig enab: 0x02ff000b
[ 1123.552266] mmc1: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 1123.552272] mmc1: sdhci: Caps: 0x546ec881 | Caps_1: 0x80000807
[ 1123.552278] mmc1: sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
[ 1123.552285] mmc1: sdhci: Resp[0]: 0x00400e00 | Resp[1]: 0x00000000
[ 1123.552291] mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00400e00
[ 1123.552296] mmc1: sdhci: Host ctl2: 0x0000000d
[ 1123.552303] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x000000016f310200
[ 1123.552306] mmc1: sdhci: ============================================
[ 1123.552579] mmcblk1: error -110 sending stop command, original cmd response 0x0, card status 0x400900
[ 1123.552619] mmcblk1: error -110 transferring data, sector 37751176, nr 8, cmd response 0x0, card status 0x0
When I reboot, there is a terminal telling me to run fsck and after doing that and rebooting again the system is again fine (for a while).
I have read that this might be a kernel problem, but that might be also be a problem with my hardware.
Could someone help me to discover which is the problem? Which log information can I provide to clarify this?
filesystem lenovo emmc
I have installed Ubuntu 18.04 in a Lenovo 310 and I have some problems after some time (the problem usually happens after watching flash videos on the browser) the filesystem gets read-only. For instance when I try to do ls, the following error appears:
bash: cannot create temp file for here-document: Read-only file system
and with dmesg I find the following:
[ 1113.452578] mmc1: mmc_hs400_to_hs200 failed, error -110
[ 1113.452615] mmcblk1: timed out sending r/w cmd command, card status 0x400e00
[ 1113.452617] mmcblk1: command error, retrying timeout
[ 1113.452908] mmc1: mmc_hs400_to_hs200 failed, error -110
[ 1113.452931] mmcblk1: timed out sending r/w cmd command, card status 0x400e00
[ 1113.452933] mmcblk1: command error, retrying timeout
[ 1123.552180] mmc1: Timeout waiting for hardware interrupt.
[ 1123.552209] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 1123.552216] mmc1: sdhci: Sys addr: 0x20000008 | Version: 0x00001002
[ 1123.552223] mmc1: sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008
[ 1123.552229] mmc1: sdhci: Argument: 0x02400988 | Trn mode: 0x0000002b
[ 1123.552235] mmc1: sdhci: Present: 0x1fff0001 | Host ctl: 0x0000003d
[ 1123.552241] mmc1: sdhci: Power: 0x0000000b | Blk gap: 0x00000080
[ 1123.552248] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x00000207
[ 1123.552254] mmc1: sdhci: Timeout: 0x00000006 | Int stat: 0x00000000
[ 1123.552260] mmc1: sdhci: Int enab: 0x02ff000b | Sig enab: 0x02ff000b
[ 1123.552266] mmc1: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 1123.552272] mmc1: sdhci: Caps: 0x546ec881 | Caps_1: 0x80000807
[ 1123.552278] mmc1: sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
[ 1123.552285] mmc1: sdhci: Resp[0]: 0x00400e00 | Resp[1]: 0x00000000
[ 1123.552291] mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00400e00
[ 1123.552296] mmc1: sdhci: Host ctl2: 0x0000000d
[ 1123.552303] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x000000016f310200
[ 1123.552306] mmc1: sdhci: ============================================
[ 1123.552579] mmcblk1: error -110 sending stop command, original cmd response 0x0, card status 0x400900
[ 1123.552619] mmcblk1: error -110 transferring data, sector 37751176, nr 8, cmd response 0x0, card status 0x0
When I reboot, there is a terminal telling me to run fsck and after doing that and rebooting again the system is again fine (for a while).
I have read that this might be a kernel problem, but that might be also be a problem with my hardware.
Could someone help me to discover which is the problem? Which log information can I provide to clarify this?
filesystem lenovo emmc
filesystem lenovo emmc
edited Jun 12 at 8:09
muru
1
1
asked Jun 11 at 16:01
Alex Grilo
664
664
2
check the output ofdmesg
for error messages regarding the disk subsystem
– Sebastian Stark
Jun 11 at 17:53
I have installed it in an eMMC (in Lenovo Yoga 310).
– Alex Grilo
Jun 13 at 12:23
Only half the bounty??? What happened?
– Fabby
Jun 22 at 19:08
add a comment |
2
check the output ofdmesg
for error messages regarding the disk subsystem
– Sebastian Stark
Jun 11 at 17:53
I have installed it in an eMMC (in Lenovo Yoga 310).
– Alex Grilo
Jun 13 at 12:23
Only half the bounty??? What happened?
– Fabby
Jun 22 at 19:08
2
2
check the output of
dmesg
for error messages regarding the disk subsystem– Sebastian Stark
Jun 11 at 17:53
check the output of
dmesg
for error messages regarding the disk subsystem– Sebastian Stark
Jun 11 at 17:53
I have installed it in an eMMC (in Lenovo Yoga 310).
– Alex Grilo
Jun 13 at 12:23
I have installed it in an eMMC (in Lenovo Yoga 310).
– Alex Grilo
Jun 13 at 12:23
Only half the bounty??? What happened?
– Fabby
Jun 22 at 19:08
Only half the bounty??? What happened?
– Fabby
Jun 22 at 19:08
add a comment |
1 Answer
1
active
oldest
votes
You have a hardware problem, but you might be able to save the eMMC by doing the following:
- plug the eMMC into another computer running Ubuntu
install ddrescue:
sudo apt-get install gddrescue
copy the eMMC to an image on the HDD of the other computer:
ddrescue --direct --retry-passes=3 /dev/XdY /tmp/eMMC.img /tmp/eMMC.log
The above command will tells ddrescue to:
--direct
use direct disk access and ignore the kernel’s cache
--retry-passes=3
retry bad sectors 3 times before giving up.
/dev/XdY
is the MMC we are rescuing whereX
andY
denominate the identifier of the MMC
eMMC.img
is the name of the image file
eMMC.log
is the name of the logfile. Always use a logfile. This allows you to resume an interrupted image at the point you left off, or to retry bad sectors after an initial pass. Without a logfile, you will have to start over again!
After that completes, unmount the MMC if needed
Insert a new MMC in the MMC slot of the computer and execute:
ddrescue --force /tmp/eMMC.img /dev/XdY /tmp/eMMC.restore.log
insert the new MMC back into your Lenovo and reboot
Done!
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1045652%2ffilesystem-problem-with-lenovo-310%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You have a hardware problem, but you might be able to save the eMMC by doing the following:
- plug the eMMC into another computer running Ubuntu
install ddrescue:
sudo apt-get install gddrescue
copy the eMMC to an image on the HDD of the other computer:
ddrescue --direct --retry-passes=3 /dev/XdY /tmp/eMMC.img /tmp/eMMC.log
The above command will tells ddrescue to:
--direct
use direct disk access and ignore the kernel’s cache
--retry-passes=3
retry bad sectors 3 times before giving up.
/dev/XdY
is the MMC we are rescuing whereX
andY
denominate the identifier of the MMC
eMMC.img
is the name of the image file
eMMC.log
is the name of the logfile. Always use a logfile. This allows you to resume an interrupted image at the point you left off, or to retry bad sectors after an initial pass. Without a logfile, you will have to start over again!
After that completes, unmount the MMC if needed
Insert a new MMC in the MMC slot of the computer and execute:
ddrescue --force /tmp/eMMC.img /dev/XdY /tmp/eMMC.restore.log
insert the new MMC back into your Lenovo and reboot
Done!
add a comment |
You have a hardware problem, but you might be able to save the eMMC by doing the following:
- plug the eMMC into another computer running Ubuntu
install ddrescue:
sudo apt-get install gddrescue
copy the eMMC to an image on the HDD of the other computer:
ddrescue --direct --retry-passes=3 /dev/XdY /tmp/eMMC.img /tmp/eMMC.log
The above command will tells ddrescue to:
--direct
use direct disk access and ignore the kernel’s cache
--retry-passes=3
retry bad sectors 3 times before giving up.
/dev/XdY
is the MMC we are rescuing whereX
andY
denominate the identifier of the MMC
eMMC.img
is the name of the image file
eMMC.log
is the name of the logfile. Always use a logfile. This allows you to resume an interrupted image at the point you left off, or to retry bad sectors after an initial pass. Without a logfile, you will have to start over again!
After that completes, unmount the MMC if needed
Insert a new MMC in the MMC slot of the computer and execute:
ddrescue --force /tmp/eMMC.img /dev/XdY /tmp/eMMC.restore.log
insert the new MMC back into your Lenovo and reboot
Done!
add a comment |
You have a hardware problem, but you might be able to save the eMMC by doing the following:
- plug the eMMC into another computer running Ubuntu
install ddrescue:
sudo apt-get install gddrescue
copy the eMMC to an image on the HDD of the other computer:
ddrescue --direct --retry-passes=3 /dev/XdY /tmp/eMMC.img /tmp/eMMC.log
The above command will tells ddrescue to:
--direct
use direct disk access and ignore the kernel’s cache
--retry-passes=3
retry bad sectors 3 times before giving up.
/dev/XdY
is the MMC we are rescuing whereX
andY
denominate the identifier of the MMC
eMMC.img
is the name of the image file
eMMC.log
is the name of the logfile. Always use a logfile. This allows you to resume an interrupted image at the point you left off, or to retry bad sectors after an initial pass. Without a logfile, you will have to start over again!
After that completes, unmount the MMC if needed
Insert a new MMC in the MMC slot of the computer and execute:
ddrescue --force /tmp/eMMC.img /dev/XdY /tmp/eMMC.restore.log
insert the new MMC back into your Lenovo and reboot
Done!
You have a hardware problem, but you might be able to save the eMMC by doing the following:
- plug the eMMC into another computer running Ubuntu
install ddrescue:
sudo apt-get install gddrescue
copy the eMMC to an image on the HDD of the other computer:
ddrescue --direct --retry-passes=3 /dev/XdY /tmp/eMMC.img /tmp/eMMC.log
The above command will tells ddrescue to:
--direct
use direct disk access and ignore the kernel’s cache
--retry-passes=3
retry bad sectors 3 times before giving up.
/dev/XdY
is the MMC we are rescuing whereX
andY
denominate the identifier of the MMC
eMMC.img
is the name of the image file
eMMC.log
is the name of the logfile. Always use a logfile. This allows you to resume an interrupted image at the point you left off, or to retry bad sectors after an initial pass. Without a logfile, you will have to start over again!
After that completes, unmount the MMC if needed
Insert a new MMC in the MMC slot of the computer and execute:
ddrescue --force /tmp/eMMC.img /dev/XdY /tmp/eMMC.restore.log
insert the new MMC back into your Lenovo and reboot
Done!
edited Jun 20 at 21:32
answered Jun 19 at 21:21
Fabby
26.4k1360159
26.4k1360159
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1045652%2ffilesystem-problem-with-lenovo-310%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
check the output of
dmesg
for error messages regarding the disk subsystem– Sebastian Stark
Jun 11 at 17:53
I have installed it in an eMMC (in Lenovo Yoga 310).
– Alex Grilo
Jun 13 at 12:23
Only half the bounty??? What happened?
– Fabby
Jun 22 at 19:08