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?

Similar Messages

[PPC] new install fails to boot: root partition not found

Hi,
new ArchPPC installation on a iMac G3. It does not boot further than initramfs because root partition is not found. I get something like:
Root device /dev/sda4 doesn't exist
Attempting to created it
ERROR: unable to determine major/minor number of root device /dev/sda4
then I get a dropbox recovery console but keyboard doesn't work.
I chroot in the installed system to change mkinicpio pata hook to ide, regenerated initramfs but that didn't help.
Any guidance to diagnose and solve this issue would be greatly appreciated.

Hi, sorry I just realized you replied to my thread.
I don't have my mac at the moment, but I must have done something like :
- boot the live CD
- get the output of lsmod
- copy this output to mkinitcpio.conf (the one that's on your HD), remove the autodetect hook
- chroot into your HD setup
- regenerate initramfs
- update yaboot (is this really mandatory?)
- exit chroot and reboot.

[SOLVED]kexec into arch fails : root device not found

Hello,
I have a fresh arch install with only base, base-devel and openssh.
I boot on penbuntu, at this point I can see my devices in /dev.
Then I mount my root arch partition on /mnt/rootfs and do :
kexec --load /mnt/rootfs/boot/vmlinuz-linux --initrd=/mnt/rootfs/boot/initramfs-linux.img --command-line="root=/dev/sda3 ro vesa video=vesafb"
which returns :
setup_linux_vesafb: 1280x720x32 @ 10028000 +708000
I then do kexec -e, It seems to start loading the kernel since the screen is cleared and each time it does
[0.845500] i8042: No controller found
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
Waiting 10 seconds for device /dev/sda3 ...
ERROR: device '/dev/sda3' not found. Skipping fsck.
ERROR: Unable to find root device '/dev/sda3' /
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[rootfs /]#
I tried everything as root in the kexec --command-line, root=LABEL, root=UUID but it always do exactly the same thing, waits for 10s for device and then ERROR and drops to the recovery shell.
Any idea of what's going on ? Why can't it see devices ?
EDIT : If that can help, the kernel from which I am kexecing is 2.6.24.3 and If I try to just chroot I notice :
mount -t proc proc proc/
mount -t sysfs sys sys/
Works but when I :
mount -o bind /dev dev/
It returns :
mount: mounting /dev on dev/ failed: Invalid argument
So somehow I think when the kernel loads it has trouble passing the /dev along and therefore sees no devices. But I still can't figure out what to do.
Thanks in advance
Last edited by Nolhian (2012-07-28 17:47:30)

I can't because I'm booting on penbuntu and not arch linux. Anyways the command used in the wiki is similar to the one I'm using.

"FILESYSTEM CHECK FAILED" - fresh install, clean partition

Hi,
I just installed Arch on my Asus EEE 701SD. Since GRUB is extremely slow (takes about 30-45 seconds from "loading..." to menu) I've set up my /boot on a separate flash drive. However, booting the new installation gives me the "FILESYSTEM CHECK FAILED" + maintenance shell. I've tried running fsck with various options but none of it has helped. Apparently, the partition is clean so I'm not quite sure what's going on. Any suggestions?
Cheers:)

The hook "usb" should work too, so I don't think we're on the right track here. But since it doesn't hurt you can add the actual kernel modules to the modules= line:
usbcore ehci-hcd (and/or uhci-hcd) usb-storage and maybe the filesystem used (and it's dependencies like ciphers).
Greets,
demian
// I guess I'm a slow typer. Why don't you show us your /etc/fstab?
From what you've written the system shouldn't be able to boot since there's no fstab entry for /boot. Maybe I misunderstood you.
Last edited by demian (2010-06-07 23:00:48)

[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.

Filesystem check failed, but filesystems are clean

Im running custom kernel and this might be related to it, but Im on my wits' end here and looking for pointers.
The problem is, Im getting filesystem check failed every time I boot my system. And it gives no apparent reason
for it to happen. I have fsck'd my partitions many times and they are clean. My hwclock is in time and rc.conf is set
to 'localtime'. The problem didn't occurs on the previous kernel (2.6.18) I had, so I've been using its running config to
compile the new one (2.6.23). The thing is, the previous kernel works fine, no filesystem check failed in boot. Only
difference between those two is I had to enable HOTPLUG in the newer kernel to get udev working, otherwise it would
complain about failing netlink socket in initscript.
As a temporary solution, I commented out the filesystem check from the rc.sysinit and it boots further. This time
it fails to mount my /boot/ and /home/ directory and fails to activate my swap. Effectively only root is mounted, but
after logging in, "mount -a" works without any problems and I can use my system normally.
I have compiled all(?) the needed modules to the kernel, so initramfs shouldn't be needed, but I've tried it anyway, no
luck there. The system is build with 2009.08 core install disc, no packages updated as far as I recall.
fstab:
#none /dev/pts devpts defaults 0 0
#none /dev/shm tmpfs defaults 0 0
/dev/hdb /media/cdrom auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
/dev/disk/by-uuid/728c65f2-a84f-401f-9899-17020758b829 /boot ext3 defaults 0 1
/dev/disk/by-uuid/2767f772-203a-4fe9-ac4d-7c8754abc4c8 swap swap defaults 0 0
/dev/disk/by-uuid/b0b958c4-5f24-414a-8826-6df956f0815b / reiserfs defaults 0 1
/dev/disk/by-uuid/e83b7114-86fe-4e8f-9e95-0d92b8e50d1a /home reiserfs defaults 0 1
dmesg:
Linux version 2.6.23-xbox (root@xbox) (gcc version 4.1.2) #3 Sat Oct 2 14:20:54 EEST 2010
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
BIOS-e820: 000000000009f000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000003c00000 (usable)
BIOS-e820: 0000000003c00000 - 0000000004000000 (reserved)
60MB LOWMEM available.
Entering add_active_range(0, 0, 15360) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 15360
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0 -> 15360
On node 0 totalpages: 15360
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 4064 pages, LIFO batch:0
Normal zone: 88 pages used for memmap
Normal zone: 11176 pages, LIFO batch:1
Movable zone: 0 pages used for memmap
DMI not present or invalid.
Allocating PCI resources starting at 10000000 (gap: 04000000:fc000000)
Built 1 zonelists in Zone order. Total pages: 15240
Kernel command line: root=/dev/hda3 devfs=mount kbd-reset xbox=hdd
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 256 (order: 8, 1024 bytes)
Detected 733.370 MHz processor.
Console: colour dummy device 80x25
console [tty0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 57652k/61440k available (1764k kernel code, 3380k reserved, 470k data, 136k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xffffb000 - 0xfffff000 ( 16 kB)
vmalloc : 0xc4800000 - 0xffff9000 ( 951 MB)
lowmem : 0xc0000000 - 0xc3c00000 ( 60 MB)
.init : 0xc0332000 - 0xc0354000 ( 136 kB)
.data : 0xc02b90ae - 0xc032ea60 ( 470 kB)
.text : 0xc0100000 - 0xc02b90ae (1764 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 1467.98 BogoMIPS (lpj=2935965)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040 00000000 00000000 00000000 00000000
Compat vDSO mapped to ffffe000.
CPU: Intel Celeron (Coppermine) stepping 0a
Checking 'hlt' instruction... OK.
NET: Registered protocol family 16
PCI: Using configuration type 1
Setting up standard PCI resources
SCSI subsystem initialized
libata version 2.21 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Cannot allocate resource region 7 of bridge 0000:00:08.0
PCI: Cannot allocate resource region 8 of bridge 0000:00:08.0
PCI: Cannot allocate resource region 9 of bridge 0000:00:08.0
PCI: Bridge: 0000:00:08.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Failed to allocate mem resource #2:80000@f8000000 for 0000:01:00.0
PCI: Failed to allocate mem resource #6:10000@f8000000 for 0000:01:00.0
PCI: Bridge: 0000:00:1e.0
IO window: disabled.
MEM window: fd000000-fdffffff
PREFETCH window: f0000000-f7ffffff
PCI: Setting latency timer of device 0000:00:08.0 to 64
NET: Registered protocol family 2
Time: tsc clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 325k freed
Enabling Xbox eject problem workaround.
fuse init (API version 7.8)
io scheduler noop registered
io scheduler deadline registered (default)
io scheduler cfq registered
xboxfb: nVidia device/chipset 10DE02A0
xboxfb: Detected 64MB of system RAM
xboxfb: Using 4M framebuffer memory
i2c-xbox.o version 0.0.1
i2c-xbox.o: Found nVidia XBOX nForce SMBus controller.
i2c-xbox.o: SMBus bus detected and initialized
xbox-tv-i2c: Using 'SMBus adapter at c000'!
xboxfb: Setting TV mode from EEPROM (NTSC)
xboxfb: detected conexant encoder
xboxfb: Setting cable type from AVIP ID: HDTV (Component video)
xboxfb: RIVA MTRR set to ON
Console: switching to colour frame buffer device 80x30
xboxfb: PCI nVidia NV20 framebuffer ver 0.9.5b-xbox (XboxGeForce3, 4MB @ 0xF3C00000)
Real Time Clock Driver v1.12ac
Linux agpgart interface v0.102
[drm] Initialized drm 1.1.0 20060810
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: module loaded
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.
PCI: Setting latency timer of device 0000:00:04.0 to 64
eth0: forcedeth.c: subsystem: 00000:0000 bound to 0000:00:04.0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE: IDE controller at PCI slot 0000:00:09.0
NFORCE: chipset revision 212
NFORCE: not 100% native mode: will probe irqs later
NFORCE: 0000:00:09.0 (rev d4) UDMA100 controller
ide0: BM-DMA at 0xff60-0xff67, BIOS settings: hda:DMA, hdb:DMA
Probing IDE interface ide0...
hda: WDC WD2500JB-00FUA0, ATA DISK drive
hdb: PHILIPS XBOX DVD DRIVE, ATAPI CD/DVD-ROM drive
hda: host side 80-wire cable detection failed, limiting max speed to UDMA33
hda: selected mode 0x42
hdb: selected mode 0x42
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hda: max request size: 512KiB
hda: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(33)
hda: cache flushes supported
hda: hda1 hda2 hda3 hda4
hdb: ATAPI DVD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: OHCI Host Controller
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1
ohci_hcd 0000:00:02.0: irq 1, io mem 0xfed00000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
PCI: Setting latency timer of device 0000:00:03.0 to 64
ohci_hcd 0000:00:03.0: OHCI Host Controller
ohci_hcd 0000:00:03.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:03.0: irq 9, io mem 0xfed08000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
USB Universal Host Controller Interface driver v3.0
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
usb 1-3: new low speed USB device using ohci_hcd and address 2
usb 1-3: configuration #1 chosen from 1 choice
input: DELL DELL USB Keyboard as /devices/pci0000:00/0000:00:02.0/usb1/1-3/1-3:1.0/input/input0
usbcore: registered new interface driver usbkbd
drivers/hid/usbhid/usbkbd.c: :USB HID Boot Protocol keyboard driver
usbcore: registered new interface driver usbmouse
drivers/hid/usbhid/usbmouse.c: v1.6:USB HID Boot Protocol mouse driver
TCP cubic registered
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Freeing unused kernel memory: 136k freed
ReiserFS: hda3: found reiserfs format "3.6" with standard journal
ReiserFS: hda3: using ordered data mode
ReiserFS: hda3: journal params: device hda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda3: checking transaction log (hda3)
ReiserFS: hda3: Using r5 hash to sort names
NET: Registered protocol family 1
spurious 8259A interrupt: IRQ7.
udev: starting version 141
df -h after "mount -a":
Filesystem Size Used Avail Use% Mounted on
/dev/disk/by-uuid/b0b958c4-5f24-414a-8826-6df956f0815b
7.4G 2.1G 5.3G 29% /
/dev/hda1 99M 11M 83M 12% /boot
/dev/hda4 226G 39M 226G 1% /home
Ok, something is definately wrong there, only root is by-uuid
blkid:
/dev/hda3: UUID="b0b958c4-5f24-414a-8826-6df956f0815b" TYPE="reiserfs"
/dev/hda2: TYPE="swap" UUID="2767f772-203a-4fe9-ac4d-7c8754abc4c8"
/dev/hda4: UUID="e83b7114-86fe-4e8f-9e95-0d92b8e50d1a" TYPE="reiserfs"
/dev/hda1: UUID="728c65f2-a84f-401f-9899-17020758b829" SEC_TYPE="ext2" TYPE="ext3"
Should I try newer udev? Can I even use the latest with 2.6.23?

Mounting Local Filesystems fails
Mount: Special device /dev/disk/by-uuid/728c65f2-a84f-401f-9899-17020758b829 does not exist
Mount: Special device /dev/disk/by-uuid/e83b7114-86fe-4e8f-9e95-0d92b8e50d1a does not exist
so does Activating swap.
still, ls -la /dev/disk/by-uuid/ gives me:
lrwxrwxrwx 1 root root 10 2010-10-02 22:45 2767f772-203a-4fe9-ac4d-7c8754abc4c8 -> ../../hda2
lrwxrwxrwx 1 root root 10 2010-10-02 22:45 728c65f2-a84f-401f-9899-17020758b829 -> ../../hda1
lrwxrwxrwx 1 root root 10 2010-10-02 22:45 b0b958c4-5f24-414a-8826-6df956f0815b -> ../../hda3
lrwxrwxrwx 1 root root 10 2010-10-02 22:45 e83b7114-86fe-4e8f-9e95-0d92b8e50d1a -> ../../hda4
should I have /boot and /home in /dev?
Full system upgrade gave me the same issue. Even after udev downgrade (udev-142 is the latest I can use with 2.6.23).
Edit:
Changed my fstab back from by-uuid to hdaX, didn't help. Strangely all hdaX are in /dev/ after boot, but the symlinks are missing.
Last edited by TelaKeppi (2010-10-02 21:22:53)

"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)

Filesystem Check Failed - Mounted

After having a little trouble getting XFCE to start automatically like KDE did, I played around with some settings using a SLAX LiveCD. Since then, I'm unable to boot for a different reason: Filesystem Check Failed.
The only thing that seems to be the problem is that /dev/sdb1 is, as it says, "mounted". When I am prompted to fix it myself, I find that the system is confused as to whether it is mounted.
Typing "mount" produces
/dev/sdb1 on /mnt/sto type ext3 (rw,noexec,nosuid,nodev)
Yet typing "umount /dev/sdb1" produces
umount: dev/sdb1: not found
umount /mnt/sto: not found
umount: dev/sdb1: not found
umount /mnt/sto: not found
cd to /mnt/sto and using dir or ls -a also shows me nothing.
The following is displayed upon "reboot"
shutdown: /dev/initctl: No such file or directory
init: /dev/initctl: No such file or directory
Finally, the files I remember having edited in SLAX and partially ARCH. I'm not sure how correct these are, but I didn't think trying to fix up XFCE was going to create such a problem:
/etc/X11/xinit/xinit.rc
#!/bin/sh
# $Xorg: xinitrc.cpp,v 1.3 2000/08/17 19:54:30 cpqbld Exp $
userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap
# merge in defaults and keymaps
if [ -f $sysresources ]; then
xrdb -merge $sysresources
fi
if [ -f $sysmodmap ]; then
xmodmap $sysmodmap
fi
if [ -f $userresources ]; then
xrdb -merge $userresources
fi
if [ -f $usermodmap ]; then
xmodmap $usermodmap
fi
# start some nice programs
#twm &
#xclock -geometry 50x50-1+1 &
#xterm -geometry 80x50+494+51 &
#xterm -geometry 80x20+494-0 &
#exec xterm -geometry 80x66+0+0 -name login
exec startxfce4
/etc/inittab
# /etc/inittab
# Runlevels:
# 0 Halt
# 1(S) Single-user
# 2 Not used
# 3 Multi-user
# 4 Not used
# 5 X11
# 6 Reboot
id:5:initdefault:xdm
rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p
c1:2345:respawn:/sbin/agetty 38400 vc/1 linux
c2:2345:respawn:/sbin/agetty 38400 vc/2 linux
c3:2345:respawn:/sbin/agetty 38400 vc/3 linux
c4:2345:respawn:/sbin/agetty 38400 vc/4 linux
c5:2345:respawn:/sbin/agetty 38400 vc/5 linux
c6:2345:respawn:/sbin/agetty 38400 vc/6 linux
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
x:5:respawn:/opt/xfce4/bin/startxfce4
# End of file
Please let me know if I'm missing any information. I'm currently running Windows, but luckily have full access to my root partition.
Thanks in advance.
P.S. /dev/sdb1 is no longer being shown in Windows OR SLAX. I predicted Windows, but can't think why it won't show up in SLAX.
Last edited by Newnux (2007-06-30 20:54:08)

Never mind, the fsck seemed to complete just fine .
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
Storage has been mounted 29 times without being checked, 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
Storage: 23560/24903680 files (22.3% non-contiguous), 41462978/49785427 blocks
It didn't take that long, I just expected a progress bar, like with other drives.
Thanks anyway! Time to see if Arch boots without problems.

[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.

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.

[Solved (initscripts-splash plroblem)] Filesystem check failed

Hello, my arch i686 sudently doesn't boot.
At system start, after loading kernel, the boot process stops and says "FILESYSTEM CHECK FAILED" give root password for maintenance or control+D for restart.
My root partition (dev/sda2) is reiserfs formated, and arch updated this week.
After reading a while I booted with Arch install CD and tried the follwing:
fsck.reiserfs --check /dev/sda2
fsck.reiserfs --fix-fixable /dev/sda2
fsck.reiserfs --rebuild-sb /dev/sda2
fsck.reiserfs --clean-attributes /dev/sda2
But no errors were found or fixed, so I can't boot arch yet.
Are there any other way to fix the filesystem?
can filesystem check be skipped?
please help
Last edited by juan_sck (2008-10-13 11:09:17)

Mektub wrote:
Could it be that it is anoter partition that is giving trouble ? Ot do you only have /dev/sda2 ?
Or start in sinle-user. At the grub boot menu, select the option that lets you edit the kernel parameters.
Add either a '1' or 'single' to the end of the kernel parameters, then continue booting up.
Mektub
of course I know where I installled Arch.
pointone wrote:There should be a more descriptive error message above where it says "filesystem check failed" describing WHY the fsck failed.
No, just system check failed. Even more, my filesystem was perfectly, it was a problem with initscripts-splash
iDeJ wrote:
i had a similar problem after the last pacman -Syu, basicly the bootsplash-initscripts are not compatible with latest udev
maybe it helps
http://bbs.archlinux.org/viewtopic.php?id=56604
I don't think installing a year old initscripts package would solve it, but you were very helpful.
Finally I could solve it with the recovery console:
After the error message I typed root password to log in, then remounted root partition for r/w:
mount -n -o remount,rw /
Finally I had to remove the package initscripts-splash and install initscripts form core.
ifconfig eth0 up
dhcpcd eth0
pacman -Syu
pacman -Rs initscripts-splash
pacman -S initscripts
exit
**You should make a backup of rc.conf before installing initscripts, because installing initscrips will overwrite it (and a few other files i hadn't modified), and pacman was supoussed to back it up, but it didn't
thanks for your help.

"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

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

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 + accidental /boot deletion

Yesterday I rebooted my PC and suddenly Arch started complaining about "Filesystem check failed", just like stated by the OP in this thread https://bbs.archlinux.org/viewtopic.php … 00#p941200
The problem was with two partitions: /boot and /home. I tried to no avail to manually fsck them using the maintenance console and e2fsck as well as the forcefsck command but it didn't work.
I didn't try any LiveCD back then but since I saw that in that thread the OP solved his problem by deleting some folders located at /media:
Fixed the problem.
The /dev/sda2 and /dev/sda5 were being mounted in the wrong place.
Instead of being mounted in /home and /boot as per /etc/fstab, they were being mounted in new directories in /media called /media/usbhd-sda2 and /media/usbhd-sda5. Upon deleting those folders, everything has gone back to normal.
I have no idea how those new folders got created...but problem solved now.
Thanks for the help, guys
Samsom
Problem is I didn't think at all when I read this post and went right away to delete the problematic folders (the post itself didn't exactly explain how the OP managed to unmount the partitions and then proceed to delete the folders, my umount commands didn't work so it wasn't crystal clear to me how he managed it, my bad tho for not checking what I was deleting).
Luckily, I think I only managed to delete partially my /boot folder (thus GRUB now complains and doesn't boot any system). So now my question is, is there a way to restore my /boot folder without a full system re-install?
Thanks in advance.

But what is the command? mkinitcpio -p kernel26 ? Also how do I fix this grub issue? I'm assuming grub created a default menu.lst after I copied the config files and setup the hd0 but I actually don't recall checking that.
Just re-did all steps including rebuilding the kernel, I still can't get the boot menu when I reboot. It goes directly to grub console.
I checked the generated menu.lst, it lists my root as the device where /boot partition is and the kernel line root enrty is defined for the arch system I want to boot :\
Last edited by Grimn (2011-05-31 17:50:02)

Filesystem check failed, root partition not found

Similar Messages

Maybe you are looking for