[Solved] Filesystem check failed - manual repair too

Good Evening.
Recently my Arch box hang up and I had to reboot forcefully. I expected to get a filesysem scan. The messages on bootup say, that the filesystem check failed and I have to repair it manually. The exact error message is similar to http://bbs.archlinux.org/viewtopic.php?id=89394.
Then I log into the maintenance shell and try to run fsck -pck /dev/sdXX. But that doesn't work because it complains that the filesystem is no ext2-fs or the superblock is corrupt. I should try one of the backup superblocks. To figure out the backup superblocks, I tried mke2fs -n /dev/sdXX but that does not work either. Now it complains that /dev/sdXX does not exist! I looked in /dev and the partitions really don't show up. Where are they? I mean, the maintenance shell works on the / partition, or does it?
To cut a long story short, I can't check my partitions and I don't know any other way how to fix the problem. The next ArchLive CD is 500 km away.
I appreciate any help.
Greetz,
haunted
EDIT:
Ok, I solved the problem as I got my ArchLive CD. If it's to anybody's use, that's the procedure I went through:
I inserted the CD and booted from it. I ran the e2fsck several times. First I did an overall check (e2fsck -v /dev/sdaX) on my Arch partition which I had to do manually i.e. type "y" to every inconsisteny found, then updated the badblock list (e2fsck -vc /dev/sdaX) and checked the partition again.
I rebooted the system without the CD to look if I succeded repairing the hdd. Eventually I deleted the /sys mountpoint in the procedure and had to create it again via ArchLive CD. After the next reboot it complained that the superblock's timestap was written in the future. Rebooting with the CD again, checking again and rebooting without CD again.
It wasn´t of any use and Arch complained again. Then I simply rebooted the system (without CD) again and on start up it stopped complaining and did a normal check on the Arch partition, completed the check and went on loading as normal. System repaired.
Last edited by hauntergeist (2010-02-08 11:11:59)

It went ahead and fixed the filesystem, however some of the files (music files mostly) are corrupted and won't play. I have backups of those so it's no big lose, as long as the file system works now.

Similar Messages

[SOLVED] Filesystem check failed on LVM partition...

My server experienced a power outage last night, and I noticed today that it wasn't booting correctly. Apparently, the storage partition, /dev/mapper/VolGroup00-lvolstorage fails the filesystem check. The first time I booted into it, I ran a manual check and answered (y) to the questions. Now when booting, it quickly displays a bunch of numbers and that scrolls for a little while (goes too fast to understand what they are...). Then it says:
####Filesystem Check Failed####
Please repair manually, blah blah blah
I'm not really sure what to do. Running fsck does the whole numbers scrolling across the screen thing again, finally asking if I want to clone multiply-claimed blocks... =/ I don't want to answer yes anymore until I get someone's input. <_<
EDIT: It said before that there are 81 inodes containing multiply-claimed blocks... Then it said a certain large file (inode #20) has 27818 multiply-claimed blocks shared with 24 other files, and it then lists other files.
Last edited by XtrmGmr99 (2010-05-21 14:14:25)

It went ahead and fixed the filesystem, however some of the files (music files mostly) are corrupted and won't play. I have backups of those so it's no big lose, as long as the file system works now.

[SOLVED] "Filesystem check failed" during boot process

I was using XFCE on my netbook recently and clicked "shutdown". It logged out to the command prompt and nothing happened. Assuming that I'd clicked "logout" by mistake, I typed "pacman -Syu" to run an update... And moments later it suddenly started the shutdown process.
Now, whenever I boot up, I see the message below. I tried booting from a GParted CD to check the filesystems for errors, but none were detected.
Can anyone suggest what I might need to do to fix the problem?
rootfs: clean, 11026/246512 files, 477083/984576 blocks
home: clean, 4386/527280 files, 237183/2105344 blocks
/dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
************* FILESYSTEM CHECK FAILED ************
* Please repair manually and reboot. Note that the root
* file system is currently mounted read-only. To remount
* it read-write type: mount -n -o remount,rw /
* when you exit the maintenance shell the system will
* reboot automatically.
Give root password for maintenance
(or type Control-D to continue):
Last edited by esuhl (2012-03-27 01:20:07)

Thank you all for your replies :-)
hadrons123 wrote:What happens when you do try the suggestion given by it?
I don't exactly know how I should "repair manually"... I thought a filesystem check in GParted would have been enough...
lijpbasin wrote:You can boot the system using a archlinux live cd, and run fsck manually on every linux partition in the old system with options.
DON'T mount any of the filesystems before running fsck, or your data will probably be lost. If you want to check the partition information first, run fdisk -l with root privileges.
Thanks. I tried booting from an ArchBang live CD last night and ran "e2fsck -pcv" on each partition. The check completed, but the problem persists... I just tried again using "fsck" as you suggested and got the following output (but the machine still fails to boot with the same error as before):
fsck from util-linux 2.20.1
e2fsck 1.41.14 (22-Dec-2010)
usr was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
usr: 115811/458752 files (1.7% non-contiguous), 783161/1834496 blocks
Gcool wrote:
/dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
As mentioned already, the reason it's failing is because the /dev/sdb2 partition is mounted before it can be fsck'd. What is this partition exactly (which filesystem, what's on it, mountpoint,...)?
I'm not overly familiar with the Linux boot process, but why would it suddenly be mounting this partition before fsck-ing it? Even if it was mounted when the netbook shutdown, surely the boot process starts with all partitions unmounted...? Anyway, the partition details from /etc/fstab are below.
<file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sda1 / ext2 defaults,noatime 0 1
/dev/sdb1 /home ext2 defaults,noatime,user_xattr 0 1
/dev/sdb2 /usr ext2 defaults,noatime 0 1
I'm (now) aware that mounting /usr as a separate partition is a bad idea and (having read the "Error when booting with the new initscripts" thread), I have told pacman to ignore updates to the initscripts package (until I figure out how best to work round or fix that issue).
Shark wrote:Write umount /dev/sdb2 in konsole or unmount partition in gparted by right click on problematic partition and click unmount. Than proced.
If I type "umount /dev/sdb2" at the prompt, I get the following error:
umount: /usr: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
I tried "umount -l /dev/sdb2" to unmount when the device becomes free... but it never does.
I also booted into GParted, but there is no option to "unmount" /dev/sdb2. There is a "mount" option in the menu, but it is greyed out. If I open a terminal window from the GParted Live environment and type "sudo umount /dev/sdb2" I get the following message:
umount: /dev/sdb2: not mounted
DSpider wrote:Are you mounting the root drive with "ro" (read only) in fstab?
No (as shown above). I don't *think* I've messed anything up with fstab or any other config files -- everything was working perfectly till the netbook shutdown whilst pacman was running.

[SOLVED] Filesystem check failed - All seems normal

Yesterday i turned of my computer after it had been on for a week or so and this morning i can't get it to boot.
While booting, on the filesystem check stage, it reports all filesystems as clean, but then says [FAIL], and gives me access to the maintenance shell.
- I booted the system with a Gparted live cd and did a check on all partitions on all disks. It reported no errors.
- in fstab I commented out the external disk and the internal one which doesn't contain any system partitions, still the same.
- I remounted root rw in the maintainance shell, and did a full system upgrade (last kernel upgrade was applied) ... still no cookies...
- I also tried to mount all the partitions in the maintenance shell. All were mounted without an error, and as far as i can tell all data was there and browsable at least.
- I tried to boot with a /forcefsck file and the checks were all done without any messages, after which it failed as usual.
Also i tried fallback (before the upgrade), which as you can guess by now, also gave the same error. The message about the filesystem check failing is not giving me any useful information. All it does is list the partitions saying every partition is clean, and then says the filesystem check has failed.
As you can probably tell, I did all the steps I could find on the forums that looked it could solve my problems, and I've hit a dead end. If I knew which partition had the problem I could move the data and format it. Could this be a hardware error?
Thanks in advance for any help offered
Last edited by vexxor (2009-07-28 11:04:02)

KimTjik wrote:Maybe a stupid question, but it's not that some partition is totally full?
Nope. I just checked.
Funny thing. In the maintenance console, when i do a "mount -a", I can navigate to the now mounted directories, but I can't see the mounted partitions as an output of either "mount" or "df".
I figured this out when I was checking if the disks were full. Root gets shown, and its on 53%. Just in case i deleted about 20GB of stuff from the media partition, but the problem remains.

[Solved] Filesystem check failed after removing harddrive

I have a harddrive in a arch computer which is not listed in fstab and not used as root, boot or home. I want to remove it from the computer, but when I try this I get the error filesystem check failed. I get the option to repair, and then get logged in as root. Here I can see my ordinary boot, root and home with fdisk -l. How can I tell the computer that there is nothing wrong, that I dont want use that disk? I searched the forum for this error and found a recommendation to use e2fsck, but since the error is because of the removed disk I cant do that.
Last edited by heptapod (2011-04-28 07:51:23)

Always use persistent block device naming to prevent this.
https://wiki.archlinux.org/index.php/Pe … ice_naming

[solved] Filesystem check fail - Cannot access LVM Logical Volumes

I am getting a "File System Check Failed"on startup, I recently did a full system upgrade but I'm not entirely sure that the cause of the issue as I don't reboot very often.
I get the error right before this line is echo'ed out:
/dev/mapper/Arch_LVM-Root:
The super block could not be read or does not describe a correct ext2 filesystem...
this is odd because the only ext2 filesystem I have is on an non-LVM boot partition...
I can log-in and mount / as read/write and I can activate LVM with
modprobe dm-mod
and
vgchange -ay Arch_LVM
and they show up in lvdisplay but their status is "NOT available"
I just need to mount these logical volumes so I can retrieve some personal data in my home directory, I am also hesitant to use LVM again if I can't retrieve my data.
any suggestions?
Last edited by action_owl (2010-08-15 02:15:58)

I just popped in the install disk and was able to mount and access the LVM groups as expected, something must have been wonky with my filesystem

[SOLVED] Filesystem check failed

Hi all,
i've just upgraded the system, but when rebooting it gives me that error on sda5 (the linux partition) and suggests me to repair manually and reboot! what should i repair? can you please give me any suggestion?
Thanks in advance
Last edited by virusso80 (2010-01-15 15:48:04)

guisacouto wrote:
it seems like today is broken filesystem day.. LOL
I had this problem too in my laptop and that fsck solved it very well!
unfortunatly I cannot say the same thing about the external hard drive that is connected to the desktop which has a fat32 filesystem corrupted.. I'm trying to find some courage to format it, because testdisk can only recover the files with some default name.. thats not good enough because 320GB of music, movies and documents isnt very usefull without the real names.. x| I guess this is just not my day
regards!
There's a /sbin/fsck.vfat as well.

Filesystem check failing; can't enter maintenance shell. [SOLVED]

Originally, arch wouldn't let me log in, complaining of an incorrect shell entry. (This is a recently re-setup system of mine, so I only have a root account.)
So I booted into the LiveCD, mounted my root partition, and editted /etc/passwd so that it pointed to the correct zsh path. But I rebooted without thinking, and without unmount. DOH!
Now Im getting the "FILESYSTEM CHECK FAILED: Please repair manually and reboot" error on boot, constantly. I've gone into the Live environemt again, and fsck the partition - didn't help.
Ideas? I've seen a recent topic similar to this one, but couldn't find help in it.
Last edited by pritchard92 (2009-09-28 21:49:34)

Thank you for the reply.
However, after many more reboots, it finally checked the disk, and is now working.
Thanks.

"Filesystem Check Failed" and problems fscking it

I realize that there are other threads about failed filesystem checks, but I think my problem is a bit unique. Sorry for making yet another thread if this question has been answered before and I am too stupid to find it:
I made an 8 hour drive back from school the other day and my box came along with me. I was excited to get it set up for the summer, but upon booting it, I was greeted with a nasty "FILESYSTEM CHECK FAILED, Please repair manually and reboot, etc" message that dumps me into a root shell with limited functionality. I apparently need to run e2fsck on /dev/sda3 to repair the partition, but I get a warning message about running e2fsck on a mounted drive, which can supposedly seriously screw up the files on the partition if it is run. I guess that I have to unmount the partition before running e2fsck on it, but for some odd reason, the umount comand is not found. Neither is mount.
Is this normal, or is something seriously messed up here? How would I go about repairing my partition if I can not unmount it? Should I just ignore the warnings and run e2fsck anyway, or will that ruin all my data? I feel kinda stuck here, and there is a lot of important data on this partition that I'd hate to lose. Please help my clueless self if you can, thanks.

LighthouseKeeper wrote:I have another 500GB HDD in my box formatted to FAT for the sole purpose of extra storage when I need it, so backing stuff up should be easy. I've just been timid about mounting /dev/sda3. I hear that when the filesystem is failing, mounting it can cause damage to all the documents on it. Does this not matter at this point? Should I just go for it?
Mounting it read-only shouldn't hurt it. Try that first, take a look at a few directories, then check your dmesg. If there is nothing funky there about failed reads, you might just be having an issue with finnicky initscripts telling you things that aren't completely true.
I would consider remouting your drive read-write once you are reasonably certain it is ok, and editing the lines in rc.sysinit where /sbin/fsck is run and removing the >/dev/null and 2>&1 redirections so you see every last bit of output from those scripts. Before you try this, you may want to run fsck with the exact options used there and see if anything fishy comes up.
Here is the relevant part of rc.sysinit I speak of:
FORCEFSCK=
[ -f /forcefsck ] && FORCEFSCK="-- -f"
NETFS="nonfs,nonfs4,nosmbfs,nocifs,nocodafs,noncpfs,nosysfs,nousbfs,noshfs,nofuse,nofuseblk"
if [ -x /sbin/fsck ]; then
stat_busy "Checking Filesystems"
if /bin/grep -qw quiet /proc/cmdline; then
/sbin/fsck -A -T -C -a -t $NETFS $FORCEFSCK >/dev/null 2>&1
else
/sbin/fsck -A -T -C -a -t $NETFS $FORCEFSCK 2>/dev/null
fi
fsckret=$?
if [ ${fsckret} -gt 1 ]; then
stat_fail

Filesystem check failed on boot

Hi,
Recently I reinstalled Arch Linux on my laptop (Dell Studio 1737) due to bloating and pacman generally being pretty borked.
For the first few boots it was fine - I installed xorg and xfce, then ran a Pacman -Syu. However, when I reboot, I get the following:
root: clean, XXXX/XXXXXX files, XXXX/XXXXXX blocks
home: clean, XXXX/XXXXXX files, XXXX/XXXXXX blocks
var: clean, XXXX/XXXXXX files, XXXX/XXXXXX blocks
/dev/sda6 is mounted. e2fsck: cannot continue, aborting.
FILESYSTEM CHECK FAILED
Please repair manually and reboot. Note that the root file system is currently mounted read-only. To remount it read-write type: mount -o remount,rw /
When you exit the maintenance shell the system will reboot automatically.
I have tried removing mtab, fsck (despite it saying the filesystem is mounted, even when umount says it is not), among other "fixes"
My current setup is
/dev/sda2: /
/dev/sda3: swap
/dev/sda4: /home
/dev/sda5: /var
/dev/sda6: /usr (this is where the problem occurs)
Can anybody help?
Thanks,
Sam

https://bbs.archlinux.org/viewtopic.php?id=134024

Filesystem check failed

Today I upgrade the kernel to 2.6.19,but when I reboot it,I get such information:
/dev/sda3
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else). then the superblock
is corrupt,and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
[FAIL]
*********************FILESYSTEM CHECK FAILED **************
* Please repair manually and reboot. Note that the root *
* file system is currently mounted read-only.To remount *
* it read write type: mount -n -o remount,rw / *
* When you exit the maintenance shell the system will *
* reboot automatically. *
Press enter for maintenance
(or type Control D to continue)
[root@(none)~]# cd /
[root@(none) /]# mount -n -o remount,rw /
mount:invalid option -n
[root@(none) /]# _
The above information is from my vmware-station,and in my own linux system I got the same,what should I do?
Can I use a livecd to mkinitcpio to rescue the system?

I just realized that now the file system error happens before udev has even started and then it drops me into maintenence mode... I can't do e2fsck or mkfs.ext3 -n /dev/sda7 because the corresponding device node doesn't exist yet... The only nodes were console, null, and a third one but I forget...
My grub and fstab seem to be correct (I just verified and they worked before)... Any help please (having the /dev/sda7 node would be nice as I can't do anything without it)? I'm using an Intel chipset and I've tried various combinations of pata/ide/piix/etc in my mkinitcpio.conf (and generated the images of course)...
I'm still searching through gentoo forums (I've tried everything I could find in arch forums) -- The partition seems also to be intact as it is accessible to me with livecd (I even chrooted and pacman -Syu) and through ext2ifs w/ vi on my Windows 2003 partition...
Thanks

"FILESYSTEM CHECK FAILED" after pacman -Syu

Hi all,
After a sucessfull 'pacman -Syu' (in which i didnt see any 'todo' messages but it did have a kernel upgrade) archlinux cannot start and i just get to a message similar talking about my root partition (ext3):
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
******************* FILESYSTEM CHECK FAILED *************
* Please repair manually and reboot. Note that the root *
* filesystem is currently mounted read-only. To remount *
* it read-write type: mount -n -o remount,rw / *
* When you exit the mantenance shel the system will *
* reboot automatically. *
I restarted with a livecd and 'e2fscked' the partition (which btw found many errors that were corrected by it) but archlinux still gives me the same message. I have checked the partition again and again a thousand times but it always comes up clean, im even able to mount it from the different livecds i have tried and can read and create files on it so im pretty sure it is fine.
And so my question is, does anyone know why this is happening? How comes archlinux keeps seeing a problem in this partition when others dont? What am i doing wrong?
An y answer appreciated.
Last edited by feralert (2009-06-03 20:15:23)

Hi again,
I have done some testing, maybe it will help.
After the failure message i put roots password and i got dropped to a shell, if i try to find the root partition (eg. ls /dev/sda) gives an error cause it sda doesnt exists.
If i edit rc.sysinit with a livecd and remove the fsck part i get a few diferent errors, some about partitions not being found and similar stuff. In my little knowledge of linux it ooks to me like it doesnt load the sata module or somethig...
I copy here the pacman.log file, i remember that the update was a huge one, around 400 Mbytes if i remember correctly:
[2009-05-30 22:20] synchronizing package lists
[2009-05-30 22:21] starting full system upgrade
[2009-05-30 22:23] synchronizing package lists
[2009-05-30 22:23] starting full system upgrade
[2009-05-30 23:29] upgraded alacarte (0.11.10-1 -> 0.12.1-1)
[2009-05-30 23:29] upgraded kernel-headers (2.6.27.6-2 -> 2.6.29.3-1)
[2009-05-30 23:29] upgraded tzdata (2009f-1 -> 2009g-1)
[2009-05-30 23:29] warning: /etc/locale.gen installed as /etc/locale.gen.pacnew
[2009-05-30 23:29] Generating locales...
[2009-05-30 23:29] es_ES.UTF-8... done
[2009-05-30 23:29] es_ES.ISO-8859-1... done
[2009-05-30 23:29] es_ES.ISO-8859-15@euro... done
[2009-05-30 23:29] Generation complete.
[2009-05-30 23:29] upgraded glibc (2.9-4 -> 2.10.1-2)
[2009-05-30 23:29] upgraded alsa-lib (1.0.19-1 -> 1.0.20-1)
[2009-05-30 23:29] upgraded alsa-utils (1.0.19-1 -> 1.0.20-1)
[2009-05-30 23:29] upgraded binutils (2.19.1-1 -> 2.19.1-3)
[2009-05-30 23:29] upgraded geoip (1.4.5-1 -> 1.4.6-1)
[2009-05-30 23:29] upgraded gcc-libs (4.3.3-1 -> 4.4.0-2)
[2009-05-30 23:29] upgraded libdrm (2.4.9-1 -> 2.4.11-2)
[2009-05-30 23:29] upgraded libgl (7.4.1-1 -> 7.4.2-2)
[2009-05-30 23:29] upgraded mesa (7.4.1-1 -> 7.4.2-1)
[2009-05-30 23:29] upgraded wxgtk (2.8.9.2-1 -> 2.8.10-1)
[2009-05-30 23:29] upgraded amule (2.2.4-1 -> 2.2.5-2)
[2009-05-30 23:29] upgraded x264 (20090216-1 -> 20090416-1)
[2009-05-30 23:29] upgraded avidemux (2.4.4-2 -> 2.4.4-3)
[2009-05-30 23:29] upgraded bin86 (0.16.17-3 -> 0.16.17-4)
[2009-05-30 23:29] upgraded gmp (4.2.4-1.1 -> 4.3.1-2)
[2009-05-30 23:29] upgraded coreutils (7.2-1 -> 7.4-1)
[2009-05-30 23:29] upgraded dbus-core (1.2.4.4permissive-1 -> 1.2.14-1)
[2009-05-30 23:29] upgraded glib2 (2.20.1-1 -> 2.20.2-1)
[2009-05-30 23:29] upgraded bluez (4.37-1 -> 4.39-1)
[2009-05-30 23:29] upgraded gstreamer0.10 (0.10.22-1 -> 0.10.23-1)
[2009-05-30 23:29] upgraded gstreamer0.10-base (0.10.22-1 -> 0.10.23-1)
[2009-05-30 23:29] upgraded gstreamer0.10-base-plugins (0.10.22-1 -> 0.10.23-1)
[2009-05-30 23:29] upgraded brasero (2.26.1-2 -> 2.26.2-1)
[2009-05-30 23:29] upgraded policykit (0.9-7 -> 0.9-9)
[2009-05-30 23:29] upgraded consolekit (0.3.0-3 -> 0.3.0-5)
[2009-05-30 23:29] upgraded cpio (2.9-3 -> 2.9-5)
[2009-05-30 23:29] upgraded curl (7.19.4-1 -> 7.19.5-2)
[2009-05-30 23:29] upgraded dbus (1.2.4.4permissive-1 -> 1.2.14-1)
[2009-05-30 23:29] upgraded dcron (3.2-3 -> 3.2-4)
[2009-05-30 23:29] upgraded dhcpcd (4.0.12-1 -> 5.0.4-1)
[2009-05-30 23:29] upgraded dmapi (2.2.9-1 -> 2.2.10-1)
[2009-05-30 23:29] upgraded docbook-xml (4.5-1 -> 4.5-2)
[2009-05-30 23:29] upgraded gconf (2.26.0-3 -> 2.26.2-1)
[2009-05-30 23:29] upgraded gnome-desktop (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:29] upgraded gdbm (1.8.3-5 -> 1.8.3-6)
[2009-05-30 23:29] upgraded sqlite3 (3.6.13-1 -> 3.6.14.1-1)
[2009-05-30 23:29] upgraded python (2.6.1-1 -> 2.6.2-1)
[2009-05-30 23:29] upgraded eog (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded epiphany (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded poppler (0.10.6-1 -> 0.10.7-1)
[2009-05-30 23:30] upgraded poppler-glib (0.10.6-1 -> 0.10.7-1)
[2009-05-30 23:30] upgraded evince (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded libsoup (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded evolution-data-server (2.26.1.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded ffmpeg (20090217-1 -> 0.5-1)
[2009-05-30 23:30] upgraded file (5.00-1 -> 5.03-2)
[2009-05-30 23:30] upgraded file-roller (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded findutils (4.4.0-1 -> 4.4.1-2)
[2009-05-30 23:30] upgraded gcalctool (5.26.1-1 -> 5.26.2-1)
[2009-05-30 23:30] installed ppl (0.10.2-2)
[2009-05-30 23:30] installed cloog-ppl (0.15.3-1)
[2009-05-30 23:30] upgraded gcc (4.3.3-1 -> 4.4.0-2)
[2009-05-30 23:30] upgraded gtksourceview2 (2.6.1-1 -> 2.6.2-1)
[2009-05-30 23:30] upgraded gedit (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded glproto (1.4.9-1 -> 1.4.10-1)
[2009-05-30 23:30] upgraded gnome-games (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded whois (4.7.33-1 -> 4.7.33-2)
[2009-05-30 23:30] upgraded gnome-nettool (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded policykit-gnome (0.9.2-3 -> 0.9.2-4)
[2009-05-30 23:30] upgraded gnome-panel (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:31] upgraded gnome-power-manager (2.26.1-1 -> 2.26.1-2)
[2009-05-30 23:31] upgraded vte (0.20.1-1 -> 0.20.2-1)
[2009-05-30 23:31] upgraded gnome-terminal (2.26.1-1 -> 2.26.2-2)
[2009-05-30 23:31] upgraded gtk-engines (2.18.1-1 -> 2.18.2-1)
[2009-05-30 23:31] upgraded gnome-themes (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:31] upgraded gnome2-user-docs (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:31] upgraded gparted (0.4.4-2 -> 0.4.5-1)
[2009-05-30 23:31] upgraded gstreamer0.10-bad (0.10.11-1 -> 0.10.12-1)
[2009-05-30 23:31] upgraded libraw1394 (1.3.0-2 -> 2.0.2-1)
[2009-05-30 23:31] installed libusb1 (1.0.0-1)
[2009-05-30 23:31] upgraded libdc1394 (2.0.3-1 -> 2.1.0-1)
[2009-05-30 23:31] upgraded libdvdread (0.9.7-2 -> 4.1.3-1)
[2009-05-30 23:31] upgraded libdvdnav (0.1.10-3 -> 4.1.3-1)
[2009-05-30 23:31] upgraded neon (0.28.3-2 -> 0.28.4-1)
[2009-05-30 23:31] installed liblrdf (0.4.0-6)
[2009-05-30 23:31] upgraded gstreamer0.10-bad-plugins (0.10.11-3 -> 0.10.12-1)
[2009-05-30 23:31] upgraded gstreamer0.10-good (0.10.14-1 -> 0.10.15-1)
[2009-05-30 23:31] upgraded libavc1394 (0.5.3-2 -> 0.5.3-3)
[2009-05-30 23:31] upgraded libiec61883 (1.1.0-1 -> 1.2.0-1)
[2009-05-30 23:31] installed libcaca (0.99.beta16-1)
[2009-05-30 23:31] upgraded gstreamer0.10-good-plugins (0.10.14-1 -> 0.10.15-1)
[2009-05-30 23:31] upgraded gstreamer0.10-ugly-plugins (0.10.11-1 -> 0.10.11-2)
[2009-05-30 23:31] upgraded gtkhtml (3.26.1.1-1 -> 3.26.2-1)
[2009-05-30 23:31] upgraded gucharmap (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:31] upgraded libarchive (2.6.2-1 -> 2.7.0-1)
[2009-05-30 23:31] NOTE
[2009-05-30 23:31] ----
[2009-05-30 23:31] Add your user to group 'camera' to use camera devices.
[2009-05-30 23:31] upgraded libgphoto2 (2.4.4-1 -> 2.4.6-1)
[2009-05-30 23:31] upgraded gvfs (1.2.2-1 -> 1.2.3-1)
[2009-05-30 23:31] upgraded gzip (1.3.12-4 -> 1.3.12-6)
[2009-05-30 23:31] upgraded jfsutils (1.1.13-1 -> 1.1.14-1)
[2009-05-30 23:31] upgraded libsndfile (1.0.19-1 -> 1.0.20-1)
[2009-05-30 23:31] upgraded sox (14.2.0-2 -> 14.2.0-3)
[2009-05-30 23:31] installed ilmbase (1.0.1-1)
[2009-05-30 23:31] installed openexr (1.6.1-1)
[2009-05-30 23:31] upgraded libpng (1.2.35-1 -> 1.2.36-1)
[2009-05-30 23:31] upgraded qt (4.5.0-5 -> 4.5.1-3)
[2009-05-30 23:31] installed xine-lib (1.1.16.3-3)
[2009-05-30 23:31] installed phonon (4.3.1-2)
[2009-05-30 23:31] installed clucene (0.9.21b-1)
[2009-05-30 23:31] installed exiv2 (0.18-1)
[2009-05-30 23:31] installed strigi (0.6.4-2)
[2009-05-30 23:31] installed soprano (2.2.3-1)
[2009-05-30 23:31] installed xdg-utils (1.0.2-1)
[2009-05-30 23:31] installed kdelibs (4.2.3-1)
[2009-05-30 23:31] installed kdebase-runtime (4.2.3-1)
[2009-05-30 23:31] installed fftw (3.2.1-1)
[2009-05-30 23:31] installed libofa (0.9.3-2)
[2009-05-30 23:31] installed tunepimp (0.5.3-6)
[2009-05-30 23:31] installed kdemultimedia (4.2.3-1)
[2009-05-30 23:31] installed polkit-qt (0.9.2-1)
[2009-05-30 23:31] upgraded k3b (1.0.5-2 -> 1.66.0alpha2-1)
[2009-05-30 23:32] upgraded qt3 (3.3.8-10 -> 3.3.8-11)
[2009-05-30 23:32] upgraded kdelibs3 (3.5.10-2 -> 3.5.10-3)
[2009-05-30 23:32] >>> Updating module dependencies. Please wait ...
[2009-05-30 23:32] >>> MKINITCPIO SETUP
[2009-05-30 23:32] >>> ----------------
[2009-05-30 23:32] >>> If you use LVM2, Encrypted root or software RAID,
[2009-05-30 23:32] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2009-05-30 23:32] >>> More information about mkinitcpio setup can be found here:
[2009-05-30 23:32] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2009-05-30 23:32]
[2009-05-30 23:32] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2009-05-30 23:32] ==> Building image "default"
[2009-05-30 23:32] ==> Running command: /sbin/mkinitcpio -k 2.6.29-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
[2009-05-30 23:32] :: Begin dry run
[2009-05-30 23:32] :: Parsing hook [base]
[2009-05-30 23:32] :: Parsing hook [udev]
[2009-05-30 23:32] :: Parsing hook [autodetect]
[2009-05-30 23:32] :: Parsing hook [sata]
[2009-05-30 23:32] :: Parsing hook [keymap]
[2009-05-30 23:32] :: Parsing hook [filesystems]
[2009-05-30 23:32] :: Generating module dependencies
[2009-05-30 23:32] :: Generating image '/boot/kernel26.img'...SUCCESS
[2009-05-30 23:32] ==> SUCCESS
[2009-05-30 23:32] ==> Building image "fallback"
[2009-05-30 23:32] ==> Running command: /sbin/mkinitcpio -k 2.6.29-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
[2009-05-30 23:32] :: Begin dry run
[2009-05-30 23:32] :: Parsing hook [base]
[2009-05-30 23:32] :: Parsing hook [udev]
[2009-05-30 23:32] :: Parsing hook [sata]
[2009-05-30 23:32] :: Parsing hook [keymap]
[2009-05-30 23:32] :: Parsing hook [filesystems]
[2009-05-30 23:33] :: Generating module dependencies
[2009-05-30 23:33] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
[2009-05-30 23:33] ==> SUCCESS
[2009-05-30 23:33] upgraded kernel26 (2.6.29.2-1 -> 2.6.29.4-1)
[2009-05-30 23:33] upgraded klibc (1.5.15-1 -> 1.5.15-2)
[2009-05-30 23:33] upgraded klibc-extras (2.5-2 -> 2.5-3)
[2009-05-30 23:33] upgraded klibc-kbd (1.15.20080312-8 -> 1.15.20080312-9)
[2009-05-30 23:33] upgraded klibc-module-init-tools (3.5-1 -> 3.5-2)
[2009-05-30 23:33] upgraded klibc-udev (141-1 -> 141-2)
[2009-05-30 23:33] upgraded libdownload (1.3-1 -> 1.3-3)
[2009-05-30 23:33] upgraded libgsf (1.14.12-1 -> 1.14.13-1)
[2009-05-30 23:33] upgraded libsasl (2.1.22-7 -> 2.1.22-8)
[2009-05-30 23:33] upgraded lsof (4.81-1 -> 4.82-1)
[2009-05-30 23:33] upgraded lzo2 (2.02-3 -> 2.03-1)
[2009-05-30 23:33] upgraded man-pages (3.20-2 -> 3.21-1)
[2009-05-30 23:33] upgraded metacity (2.26.0-1 -> 2.26.0-2)
[2009-05-30 23:33] upgraded mlocate (0.21.1-1 -> 0.22-1)
[2009-05-30 23:33] upgraded mplayer (28347-4 -> 29318-1)
[2009-05-30 23:33] upgraded mtools (4.0.10-1 -> 4.0.10-2)
[2009-05-30 23:33] upgraded nautilus (2.26.2-1 -> 2.26.3-1)
[2009-05-30 23:33] upgraded net-tools (1.60-13 -> 1.60-14)
[2009-05-30 23:33] * relogin or source /etc/profile.d/openoffice.sh
[2009-05-30 23:33] * see http://wiki.archlinux.org/index.php/Openoffice
[2009-05-30 23:33] how to use extensions, e.g. for spell checking
[2009-05-30 23:33] see /opt/openoffice/share/extension/install what
[2009-05-30 23:33] is shipped with this package
[2009-05-30 23:33] upgraded openoffice-base (3.0.1-1 -> 3.1.0-1)
[2009-05-30 23:33] upgraded openoffice-es (3.0.1-1 -> 3.1.0-1)
[2009-05-30 23:33] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2009-05-30 23:33] upgraded pacman-mirrorlist (20090405-1 -> 20090509-1)
[2009-05-30 23:33] upgraded pango (1.24.1-1 -> 1.24.2-1)
[2009-05-30 23:33] upgraded pidgin (2.5.5-2 -> 2.5.6-1)
[2009-05-30 23:33] upgraded tcp_wrappers (7.6-8 -> 7.6-9)
[2009-05-30 23:33] upgraded portmap (6.0-2 -> 6.0-3)
[2009-05-30 23:33] upgraded ppp (2.4.4-7 -> 2.4.4-8)
[2009-05-30 23:33] upgraded procps (3.2.7-5 -> 3.2.8-1)
[2009-05-30 23:33] upgraded psmisc (22.6-2 -> 22.7-1)
[2009-05-30 23:33] upgraded pycairo (1.8.2-1 -> 1.8.4-1)
[2009-05-30 23:33] upgraded pygobject (2.16.1-1 -> 2.18.0-1)
[2009-05-30 23:33] upgraded python-gdata (1.3.0-1 -> 1.3.1-1)
[2009-05-30 23:33] upgraded python-nose (0.10.4-3 -> 0.11.0-1)
[2009-05-30 23:33] upgraded python-numpy (1.3.0-1 -> 1.3.0-2)
[2009-05-30 23:33] upgraded rsync (3.0.5-1 -> 3.0.6-1)
[2009-05-30 23:34] upgraded seahorse (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:34] upgraded seahorse-plugins (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:34] upgraded sysfsutils (2.1.0-4 -> 2.1.0-5)
[2009-05-30 23:34] upgraded syslinux (3.75-4 -> 3.80-1)
[2009-05-30 23:34] upgraded sysvinit (2.86-4 -> 2.86-5)
[2009-05-30 23:34] upgraded tomboy (0.14.1-1 -> 0.14.2-1)
[2009-05-30 23:34] upgraded transmission-gtk (1.42-1 -> 1.60-1)
[2009-05-30 23:34] upgraded unrar (3.9.1-1 -> 3.9.3-1)
[2009-05-30 23:34] upgraded usbutils (0.81-1 -> 0.82-1)
[2009-05-30 23:35] upgraded vlc (0.9.9a-1 -> 0.9.9a-4)
[2009-05-30 23:35] upgraded wireless_tools (29-2 -> 29-3)
[2009-05-30 23:35] upgraded xfsprogs (3.0.0-1 -> 3.0.1-1)
[2009-05-30 23:35] upgraded xkeyboard-config (1.5-1 -> 1.6-1)
[2009-05-30 23:35] upgraded xorg-server-utils (7.4-5 -> 7.4-6)
[2009-05-30 23:35] upgraded xorg-server (1.6.1-1 -> 1.6.1.901-1)

Disk order changes, grub problem, filesystem check failed

I'm having some problems installing Archlinux onto a machine with a lot of SATA drives, some connected by SATA cards. I have tried the 2009-08 netinstaller burned to CD, both -x86_64.iso and -x86_64-isolinux.iso, and I have the same problem with both.
I am installing from a USB-connect optical drive to an Intel X25-M 80GB SSD connected to a motherboard SATA port. I also have 2 HDDs connected to motherboard SATA ports, and 4 more HDDs connected to 4 SIL-based PCIe SATA cards. Additionally, I have a 4GB Patriot USB flash drive connected to a motherboard USB port. None of the HDDs have a bootable MBR, I am planning to create an mdadm RAID with the HDDs, but the USB flash drive is bootable. The motherboard is an Asus Z8PE-D18 with the latest BIOS, in AHCI mode.
First thing to note is that I was able to successfully install Fedora 12 linux to this machine in the exact configuration that I am trying to install Archlinux. I just installed Fedora 12 again last night, and it installed and loaded fine when I rebooted from the SSD.
So, the problems I am having with Archlinux. During install, I found that the SSD is showing up as either /dev/sde or /dev/sdf. This is odd since it was /dev/sda with Fedora. It makes sense for it to be /dev/sda, since it is on the first motherboard SATA port. But I proceeded with the Archlinux install, and grub seemed to detect the stage1 location properly -- root was set to (hda4,0) or (hda5,0) depending on whether the SSD was at sde or sdf. The kernel root was configured by UUID, so that does not depend on the drive order. Okay so far.
The problem shows up on reboot. The bootloader immediately complains that there is no such partition sde1 or sdf1. I drop into a grub command line and do
find /boot/grub/stage1
and it replies with (hd0,0), so I modify the boot line to root (hd0,0) and boot. Now it gets pretty far. Lots of boot messages scroll by. Here are some of the last few before the problem:
Waiting 10 seconds for device /dev/disk/by-uuid/22a35aa2-9799-4575-b1eb-456e819a1a26 ...
kjournald starting. Commit interval 5 seconds
EXT3-fs (sde1): mounted filesystem with writeback data mode
INIT: version 2.86 booting
::Starting UDev DAemon
::Triggering UDev uevents
::Loading Modules
::Waiting for UDev uevents to be processed
::Bringing up loopback interface
::Mounting Root Read-only
::Checking Filesystems
/dev/sdf1:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock
**** FILESYSTEM CHECK FAILED
* Please repair manually and reboot. Note that the root file system
* is currently mounted read-only....
Give root password for maintenance
So I logged in as root and did an fdisk -l. The boot SSD was at /dev/sde. The menu.lst has root as (hd5,0), which would be sdf (which was correct during installation, but the disk order apparently changed). The kernel root= in menu.lst used by-uuid, and it at least points to the correct drive, which I suppose is why I was able to boot as far as I did, but when it tries to mount the root filesystem, it fails as shown above.
So, at initial grub boot, the grub stage1 is found at (hd0,0). During installation, the SSD was sdf, but after booting the kernel, the SSD is sde. What is going on?
One other experiment is that I pulled all the drives (including USB flash drive) except the SSD. The HDDs are in hot-swap slots, so that was easy. The PCIe SATA cards are still plugged into the PCIe slots. Then I was able to successfully install and boot Archlinux. But when I plugged the drives back in and rebooted, I had the same problem as detailed above.
Any suggestions on how to fix this?

I had the same problem.
Last week I installed Arch onto a new SATA HD. I wanted to make sure the installation worked before I attached the other drives. On booting with the other drives attached, similar messages.
My solution:
Login as root.
Follow the instruction to mount / as read-write so you can make changes to the filesystem.
edit /etc/fstab and eliminate the references to /dev/sdxx and replace them with UUIDs or labels (as suggested above) as these won't change.
in /etc/fstab ...
# external data sources
#data /dev/sdb6
UUID=931d7107-1241-4d82-ad28-fcbe7af8ba69 /data ext3 defaults 0 0
#Documents /dev/sda9
/dev/disk/by-label/Documents /data/Documents ext3 defaults 0 0
Reboot and you should be good.
You can find the UUID of the drives by using
$ blkid
or you can set a drive label with e2label, assuming you are using ext2,3 or 4
Good luck.

First boot - filesystem check failed.

I just installed Arch on a clean drive. Newly partitioned with /, /home, and swap partitions. After installation and a reboot, GRUB loads. Then after a while loading the OS, it says filesystem check failed.
/dev/hda1:
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid
and it really contains an ext2 filesystem (and not swap or ufs or comething else), then the suberblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Running that command gives:
No such file or directory while trying to open /dev/hda1
My machine is an IBM ThinkPad, model R40. The copyright year on the bottom is 2003. The hard drive is a 20 gigabyte Fujitsu. I don't know what else people need, but I always get asked for more info right away when enquiring about these things. So, the logo is on the bottom-right and the letters are red, green, and blue. The Intel Centrino sticker on the other side is starting to peel off. What else do you need to know?

Mounting Root Read-only [DONE]
Checking Filesystems [BUSY]
/dev/hda1:
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid
and it really contains an ext2 filesystem (and not swap or ufs or comething else), then the suberblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
***************** FILESYSTEM CHECK FAILED *****************
* Please repair manually and reboot. Note that the root *
* file system is currently mounted read-only. To remount *
* it read-write type: mount -n -o remount,rw / *
* When you exit the maintenance shell the system will *
* reboot automatically. *
That looks better in monospace, but that's an exact copy. Else it'd have better grammar. In /dev, I can see:
sda
sda1
sda3
Yet no sda2. Nor any hda's. Hmm! What's all this, then?
[Edit] Ugh, submitting that thing makes it look even worse. You can read it, though. [End edit]
Last edited by Qoph (2009-12-28 22:03:30)

Filesystem check failed, root partition not found

Hi all,
Since yesterday I receive the following error message when booting into Arch:
:: Mounting root filesystem read-only [ OK ]
:: Checking filesystems [BUSY]
/dev/sda4: no such file or directory
*************** FILESYSTEM CHECK FAILED *******************
* Please repair manually and reboot ...
The device /dev/sda4 is my root partition, which is - after entering the root
password - mounted as /dev/root. Checking the partition with 'reiserfsck
/dev/sda4' does not give any error or warning messages. I can also
successfully remount and access it with 'mount -n -o remount,rw /'.
'ls -l /dev/sda*' gives me the following:
brw-rw---- 1 root disk 8, 0 Apr 28 16:32 /dev/sda
brw-rw---- 1 root disk 8, 1 Apr 28 16:32 /dev/sda1
brw-rw---- 1 root disk 8, 2 Apr 28 16:32 /dev/sda2
brw-rw---- 1 root disk 8, 3 Apr 28 16:32 /dev/sda3
brw-rw---- 1 root disk 8, 4 Apr 28 16:32 /dev/sda4
So the device itself seems to be there. Rebooting doesn't help, neither does
using older, working kernel versions.
I also checked other topics on similar subjects, but I couldn't find any solution.

Hmm, it doesn't work even with the UUID. But the error looks similar:
Failed to open the device UUID=672f076e-131c-4220-81ba-b30639ef9285: No such file or directory
But when I call rc.sysinit manually directly after entering the root password,
everything works fine. It does work with sda as well as uuid notation.
I manually added some code before the output of the '*** FILESYSTEM CHECK FAILED ***' message:
ls -l /dev/sda*
sleep 1
ls -l /dev/sda*
The result was:
ls: cannot access /dev/sda*: No such file or directory
brw-rw---- 1 root disk 8, 0 Apr 30 09:12 /dev/sda
brw-rw---- 1 root disk 8, 1 Apr 30 09:12 /dev/sda1
brw-rw---- 1 root disk 8, 2 Apr 30 09:12 /dev/sda2
brw-rw---- 1 root disk 8, 3 Apr 30 09:12 /dev/sda3
brw-rw---- 1 root disk 8, 4 Apr 30 09:12 /dev/sda4
So it seems that the devices are really not yet created. Is it a udev problem?
I am not aware of changing anything udev specific, maybe an updated version?

[Solved] Filesystem check failed - manual repair too

Similar Messages

Maybe you are looking for