Originally Posted by desouzaalex
Hey, I forgot telling that it shows:
I/O Error Dev SDB Sector 19777536
AND it started happening a couple of days ago, then the lights went off over here.
I'm new to Linux, I'm still stuying and learning, so I don't know many things yet. Could you go any further on the "rhgb" and "quiet" boot options?
And concerning that manual intervention (fsck), I guess I should just shoot "fsck" in the terminal while in maintenance mode, right? (Yes, I tried to do it right now, while using the system and it warned me that it could cause SEVERE filesystem damage
) It'll do things automatically or I'm supposed to do anything?
The I/O error is bad news. The disk may be failing.
If you are new to Linux at least I guess you are not so new with Windows.
Grab Hard Disk Sentinel (www.hdsentinel.com
) and check your drive (Windows program, easiest option for now).
If you have important data, the time for a backup was yesterday
rhgb & quiet: At boot menu stop the automatic boot (play with cursor keys) and edit the kernel line parameters: delete 'rhgb' and 'quiet' and you may add 'single' to boot in single mode (where you can run fsck directly). These changes made on-the-fly are volatile, they are only for the current boot. With fsck you have no options basically but to say 'y' (yes).
With fsck you have to specify the partitlion. e.g.
'fsck /dev/sdb3' is the third partition ('3') on the second disk ('b') in the order detected at boot time
Use 'mount' to find the device, you should see something like:
/dev/sda2 on / type ext3 ...
which means the root fs is on first disk, partition 2, and is of type ext3
WARNING: YOU DO _NOT
_ RUN fsck ON A MOUNTED FILESYSTEM !
This is probably why you got the warning and this is why you need to go in single mode with the root fs check.