shitshitshit /dev/sda4 has errors?

nilsHaus · 2007-07-26 14:04:59

First thing it does, Arch checks my filesystem (/dev/sda4) and it has errors...Filesystem check fails, and it tells put password to log in as root or Ctrl+D to continue...I really need this HD because it has tons of family pictures, etc. no backup (THIS WAS MY BAKCUP WHAT THE H)
Worrisome is that when I drop into root /home/*username* doesn't exist. And mounting the samba server also fails...Do I have to take out the HD and make it an external now? Is it really dead? Or could this be a mistake. This was a default Arch installation, I dunno what /dev/sda4 is...

ataraxia · 2007-07-26 15:00:25

Did you try to fsck it like it told you to? I'd tell you how but you didn't say what kind of fs it has.

nilsHaus · 2007-07-26 19:08:46

ext2, I think. The default?

ataraxia · 2007-07-27 02:16:01

So, when you drop into root as you did, run "e2fsck -y /dev/sda4". Repeat until it tells you everything is ok, then reboot again.

hades646 · 2007-07-27 03:36:54

I am not shure, but I think I once had the same problem. When the filesystem-checking daemon finds an error it stops and tells you that you have to fix it first. This could be happening because the filesystem was not properly unmounted before rebooting.

What you have to do is what ataraxia said before, but as I remember, when you enter the root password, if that drive is already mounted (which is the case of the root partition), you have to remount it read-only first. You can achieve this by typing:

mount -o remount,ro /dev/sda4

Then you can check the filesystem again with e2fsck as ataraxia said above. In the case you don't need to reboot Linux, you can remount the filesystem as read-write by typing:

mount -o remount,rw /dev/sda4

If it has errors, you probably will have to reboot, but maybe in the future, if you just want to check the filesystem for errors, this last command will be helpful.

Regards.

ataraxia · 2007-07-27 15:09:56

It comes up read-only by default at this point in the boot process, it's safe to fsck here.

nilsHaus · 2007-07-29 03:14:29

first of all, its /dev/sda3.
I ran e2fsck fine, but then when I hit reboot, it didn't work. So I did init 6. THE PROBLEM, is that there was a ubuntu liveCD in the drive, so when it started up again, it took real long load, never actually did (I've had terrible experience with LiveCDs, every single one except puppy linux). Anyways, I had to hard reboot it. I know, stupid.

Now its telling me superblock could not be read or does not correctly describe ext2 filesystem. I'm not even sure /dev/sda3 is a real filesystem (it could be swap). In any case, grub still works so maybe I should use the fallback arch linux image?

nilsHaus · 2007-07-29 03:16:14

And now I can't even init 6 anymore

Arch Linux

#1 2007-07-26 14:04:59

shitshitshit /dev/sda4 has errors?

#2 2007-07-26 15:00:25

Re: shitshitshit /dev/sda4 has errors?

#3 2007-07-26 19:08:46

Re: shitshitshit /dev/sda4 has errors?

#4 2007-07-27 02:16:01

Re: shitshitshit /dev/sda4 has errors?

#5 2007-07-27 03:36:54

Re: shitshitshit /dev/sda4 has errors?

#6 2007-07-27 15:09:56

Re: shitshitshit /dev/sda4 has errors?

#7 2007-07-29 03:14:29

Re: shitshitshit /dev/sda4 has errors?

#8 2007-07-29 03:16:14

Re: shitshitshit /dev/sda4 has errors?

Board footer