You are not logged in.
Pages: 1
I am facing some serious problem today.
When I try to boot my laptop, I get an error:
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] unhandled sense code
...
end_request: I/O error, dev sda, sector xxxxxxxxxx
ata1: EH complete
JBD: Failed to read block at offset xxxxxxxxxxx
JBD: recovery failed
EXT4-fs (dm-0): error loading journal
mount: mounting /dev/mapper/root on /new_root failed: Invalid argument
ERROR: Failed to mount the real root device.
Bailing out, you are on your own,. Good luck.
I was doing my things when suddenly, the system froze and entered a loop (i noticed because of the music that was playing started looping) and i had to hard reboot.....
The root partition, as like the home one, are encrypted with luks.
Any idea? Did my HDD blow?
Last edited by Xi0N (2011-07-10 14:08:32)
Offline
try to enable the S.M.A.R.T option in the bios
so you can check it before booting.
or try fsck or similar from livecd.
ezik
Online
or try fsck or similar from livecd.
ezik
This worked, but i don't understand why the system didn't do it by itself.....
Offline
arch always check my disk in case of problem
and some times without problem - after specific times of boot.
eik
Online
Why would the system automagically check your disk if it started doing weird stuff? If you haven't set it up it won't. Anyways; you can't run fsck on a mounted filesystem.
Emm... usually, after a bad shutdown, the system checks itself automagically.... well, actually, its a simple system for knowing that the disk was not unmounted properly, not magic.. .... It was strange that this time the magic didn't work.... just that..
Thanks for the help, anyway....
Offline
Pages: 1