Filesystem check failed while booting [SOLVED]

I tried to get some help from my previous post but got no answers, so I'll summarize in hope of getting an answer:
I've installed linux before windows because I had this operating system before. But, when I've partitioned I've made a NTFS type 83 for windows, cause I know I'd install it later on.
Now, I've restored my bootloader (grub) but when I try to boot my arch linux copy, a message tells me that my partition sda2 which is my Windows one, isn't clean or corrupt.
all my linux partition are clean, but my NTFS windows partition make me unable to boot on my linux OS with this error msg:
fsck.ext4: Bad magic number in super-block while trying to open /dev/sda2
/dev/sda2:
The superblock could not be read or does not describe a correct ext filesystem. If the devine is valid and it really contains an ext2 filesystem (and not swao or ufs or simething else), then the superblock is corrupt, and you might try running e2fsck with an alternate superbloc:
e2fsck -b 8193 <device>
Next I can do is entering the root psw and use the command line, I really need help to restore my linux partition without formating anything, please.
My guess is that linux doesn't reorganize the partition as it is NTFS and doesn't boot for this reason, but didn't find how to fix it over internet yet, some help would be really appreciated.
Last edited by Mazh (2011-06-10 20:30:39)

My partition layout is:
fdisk -l output:
/dev/sda1 ID (5) extended (don't know what's that didn't think I've made that myself, maybe coming from windows when I installed the NTFS partition)
/dev/sda2 * HPFS/NTFS/exFAT ID (7) (strange cause I had set 87 but well, windows is working correctly it seems)
/dev/sda3 ID (83) linux
/dev/sda5 ID (83) linux
/dev/sda6 ID (83) linux
/dev/sda7 ID (83) linux
/dev/sda8 * ID (83) linux
yep, it's actually strange that my fsck.ext4 check my sda2 partition NTFS...
cat /etc/fstab:
/dev/sda2 /home ext4 defaults 0 1
/dev/sda5 swap defaults 0 0
/dev/sda6 /var ext4 defaults 0 1
/dev/sda7 /usr ext4 defaults 0 1
/dev/sda8 / ext4 defaults 0 1
menu.lst
linux grub
/dev/sd0 (fd0)
/dev/sda (hd0)
/dev/sdb2 (hd1,1)
/dev/sda3 (hd0,2)
title arch linux
root (hd0,7)
kernel /bootvmlinuz26 root=/dev/sda8 ro
initrd /boot/kernel26.img
the arch fallback (same)
title Windows xp lite sp3
rootnoverify (hd0,1)
makeactive
chainloader +1
I really have to write by hands, so if you wants more info tell me and I'll write more.
it's strange, could you explain me what does mean hd1 or hd0? isn't the 1st and second hard drive? and the second array the partition? cause if so, i've only 1 drive. But I'm probably not correct. Hope you get enough info to get me out of this problem!
And no, I'm not using UUIDs, thx for your suggestion!

Similar Messages

"Filesystem check failed" on boot [Solved]

It seems to not like /home or /. Tried reinstalling Arch using ext3 instead of ext4 but I still get the same error. I tried searching for a fix on the forums already but couldn't find one that worked for me.
Misc Info:
- Using VirtualBox 3.1.2
- Using 2009.08 netinstall iso
Last edited by NightKev (2010-02-17 05:15:11)

I don't know how you would do so in VB, but on my desktop I used an Arch LiveCD to reinstall GRUB in order to get /root and the kernel image working from the /boot directory. I entered the command "grub" as root in a terminal to open the grub prompt "grub>" then I entered "find /boot/grub/stage1" and received back" (hd1,1)" which is where my root partition was located. I then entered "root (hd1,1)" and then "setup (hd0)" and then "quit". It installed GRUB to the MBR. I don't know if that's helpful in your case though, but if GRUB is installed it could be.

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

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

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

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

Filesystem check failed - Linux won't boot

I did a search on this forum, and this error ("Filesystem check failed") comes up a few times, but always after its user resized his partitions or did something to his fstab. Which is not my case.
For two days, I've been getting this error at boot. Just before getting the error, I can see that both my / and /home partitions are checked and raise no errors. However, when it gets to my /boot partition, I get the following message.
Filesystem mounted or used by another program ?
I have no clue as to what's happening. My current partitions, for the record, are
/boot /dev/sdb1 ext2
/ /dev/sdb2 ext3
/home /dev/sdb3 ext3
If you need any other info to help my solve my problem, just ask. Thanks !

4th attempt to restore successful!
Will attempt to verify disk and make second attempt to install Mavs.

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

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

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. with UUID, SATA, fsck -f doesn't res [SOLVED]

It appeared right on the first boot.
Things I tried:
reinstalled Arch
fsck -f
checked fstab - all mountpoints in UUID
system was installed with AHCPI enabled and running
system boots like this:
Bringing up loopback interface [done]
Mounting Root Read-only [done]
Checking Filesystems [busy] linuxroot: clean, 110927/327680 files, 744572/1310384 blocks
[fail]
Filesystem check failed.
Please repair manually and reboot. Note that the root file system is currently mounted readonly. To remount it read-write type: mount -n -o remount ,rw /
When you exit the maintenance shell the system will reboot automatically.
Its a Sata-HD
It has 4 partitions and had Vista preinstalled using the first 3. on the last patitions (sda4) i put /. home and swap are on a USB-HD
EDIT
fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
#/dev/cdrom /media/cd 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
UUID=3f247afa-7966-4472-aea3-d65199b769b3 swap swap defaults 0 0
UUID=735b5356-141f-4ee5-a5cf-4ca82dd6809b /home ext3 defaults,noatime 0 1
UUID=cc6b9a82-b403-4fce-94b7-a939e85fbd17 / ext3 defaults,noatime 0 1
Last edited by capoeira (2010-05-27 21:03:23)

Factory wrote:Are you positive those are the correlating uuids for the appropriate drives? On my desktop my sd*#s like to switch themselves after an install.
yes, the UUIDs were generated by the installer, and I can manualy mount them with "mount /dev/sda4", "mount /dev/sdb2"
EDIT: I duble checked that, UUIDs OK
Inxsible wrote:
capoeira wrote:It has 4 partitions and had Vista preinstalled using the first 3. on the last patitions (sda4) i put /. home and swap are on a USB-HD
Probably a dumb question, but you do have your USB HD plugged in when you boot up, right?
sure I do
Last edited by capoeira (2010-05-27 18:39:28)

Filesystem check failed after running upgrades [Solved]

I have a new arch installation with /home, /tmp, /var, and /usr mounted on an LVM partition. After running the updates I get a "Filesystem Check Failed" error message. It then dumps me into the terminal in read-only mode, giving me the option for read/write... which doesn't matter, because without access to vi (which is on /usr o the LVM partition) I can't access anything anyway. / and /boot test clean, but it's not recognizing the LVM. Any help would be appreciated.
Last edited by 2handband (2011-01-22 19:21:17)

Figured it out... the miserable thing couldn't make up it's mind which drive to label sda.

Filesystem check failed while booting [SOLVED]

Similar Messages

Maybe you are looking for