You are not logged in.

#1 2008-10-07 06:06:08

Rulatir
Banned
Registered: 2007-02-05
Posts: 94

[SOLVED (sort of)] Boot failure after klibc upgrade!

I am aware that "after" doesn't necessarily mean "because of", but anyway here is, painstakingly written down and retyped, what I get immediately after updating klibc and trying to reboot:

/dev/sda6 contains a file system with errors, check forced
Fast symlink 523313 has EXTENT_FL set

***************** 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                                    *
*                                                          *
************************************************************

followed by the usual password-or-Ctrl+D prompt.

I have no idea what this "fast symlink" "EXTENT_FL" message means or how to fix it manually. Google suggests that:

- this kind of curruption seems to be related to deleting a symlink (which was necessary to install new klibc)
- normally when it happens fsck can deal with it; it just asks "Clear?" and proceeds if given "y".

What to do? Help!

Last edited by Rulatir (2008-10-07 07:06:39)

Offline

#2 2008-10-07 06:39:22

AD28
Member
Registered: 2008-09-16
Posts: 161

Re: [SOLVED (sort of)] Boot failure after klibc upgrade!

Offline

#3 2008-10-07 07:06:10

Rulatir
Banned
Registered: 2007-02-05
Posts: 94

Re: [SOLVED (sort of)] Boot failure after klibc upgrade!

Rulatir wrote:

- normally when it happens fsck can deal with it; it just asks "Clear?" and proceeds if given "y".

Hint, hint! When run on bootup, fsck is run with a flag that makes it fail when it would otherwise require input from user.

Booted up from ArchLive. Tried fsck.ext4dev /dev/sda6, no joy, fsck.ext4dev not on ArchLive, must "steal" from the installed system. The trick is, /dev/sda6 is the root. Luckily it mounted read-only so I could steal the utility. I also had to "upgrade" e2fs libs because fsck.ext4dev needed newer version.

Ran fsck.ex4dev, said "y" to about a hundred errors of the same type. Reboot, fsck runs but completes this time and reboots automatically. Now fsck runs on other partitions, one of which has the same kind of problem. This time I could use the maintenance shell to run fsck.ext4dev.

I still don't know what caused the problem.

Offline

#4 2008-10-08 20:17:13

tetonedge
Member
From: Fort Collins, CO
Registered: 2008-08-22
Posts: 71
Website

Re: [SOLVED (sort of)] Boot failure after klibc upgrade!

I have this exact same problem, I have tried booting into archlive and fsck doesn't find anything wrong. How did you exactly fix it, thanks

dt

Offline

#5 2008-10-08 20:57:10

godane
Member
From: NH, USA
Registered: 2008-02-03
Posts: 241
Website

Re: [SOLVED (sort of)] Boot failure after klibc upgrade!

If your talking about my ArchLive system then its fsck.ext4 not fsck.ext4dev. Thats why its not in my system.


I'm working on a live cds based on Archlinux. http://godane.wordpress.com/

Offline

#6 2008-10-08 21:49:30

MONVMENTVM
Member
Registered: 2007-10-06
Posts: 50

Re: [SOLVED (sort of)] Boot failure after klibc upgrade!

Nah... I have that problem too using ext3.

I played around with fsck and stuff like that from a live cd and I could even mount the partition from there.

Offline

#7 2008-10-13 18:56:14

MONVMENTVM
Member
Registered: 2007-10-06
Posts: 50

Re: [SOLVED (sort of)] Boot failure after klibc upgrade!

push

Is there a fix for it now? I was away and busy in the last days... so is there an update? I still can't boot into my Arch Linux.

thx

Offline

#8 2008-10-14 11:16:41

tj
Member
Registered: 2008-01-11
Posts: 48

Re: [SOLVED (sort of)] Boot failure after klibc upgrade!

@MONVMENTVM: you'll need to chroot into your arch install (from live-cd or other linux partition); next make sure that /etc/hosts, /etc/resolv.conf, /etc/rc.conf are all in order; update the system with pacman and make sure you get the latest initscripts (as mentioned in other posts); exit the chroot and try again

Last edited by tj (2008-10-14 11:19:11)

Offline

Board footer

Powered by FluxBB