has udev updated fsck'ed (literally) my install?

dtw · 2005-05-31 08:35:08

I just did my first reboot after installing the latest udev - only to get an error at the fsck stage say that my root partition couldn't be found and maybe it was a bad super block - i have not yet fscked with a rescue disk but I can see no reason for a sudden bad superblock!

iphitus · 2005-05-31 10:58:38

the superblock is backed up throughout the filesystem and it is possible to recover it, only problem is i dont have my linux

http://edseek.com/archives/2004/02/25/e … -recovery/

theres some instructions for ext3, but im sure theres an easier way, and im sure its possible for other filesystems.

Moo-Crumpus · 2005-05-31 11:08:14

udev had some issues creating scsi nodes in a devfs comparable manner (/dev/discs/disc1/part3 etc). It was updated to create this nodes using the udev-scsi script. Do you use sata ore scsi, maybe usb devices? Then it might be useful to have a look at your fstab. It should work if you use classic syntax, like /dev/sda1 etc - I still use them, allthough latest udev packages fixed this issue. Devfs syntax might be a problem here.

lanrat · 2005-05-31 12:53:17

... or you have custom rules using udev scripts for creating devfs compatible symlinks. The location (scripts are now in udev/scripts) and syntax has changed too in this udev version.

On the other hand it may have nothing to do with udev upgrade. I did an upgrade yesterday on two boxes and after updating my custom rules they rebooted fine.

Tell me if you need any help with udev - there are many changes in latest versions (rules mixing, rules on unplug events etc. etc.)

dtw · 2005-06-01 01:19:03

...or you could make sure that when you install the new udev pkg - which changes where the scripts are stored - you make sure you replace you old rules with the new rules...

ahem

nggalai · 2005-06-01 06:24:10

lanrat wrote:

... or you have custom rules using udev scripts for creating devfs compatible symlinks. The location (scripts are now in udev/scripts) and syntax has changed too in this udev version.

That sounds like something that ought to be on the frontpage of www.archlinux.org prior to releasing a package which changes such basic things to the base repository. Or, even nicer: make pacman show a huge notice as soon as installation is done. Totem e.g. came up with a nice notice that it was using GStreamer now as default.

dtw · 2005-06-01 10:35:23

i agree that this should have been done - Judd is normally very good at doing that. Something in the post or pre install script would be best

Moo-Crumpus · 2005-06-01 11:35:23

fullack

Arch Linux

#1 2005-05-31 08:35:08

has udev updated fsck'ed (literally) my install?

#2 2005-05-31 10:58:38

Re: has udev updated fsck'ed (literally) my install?

#3 2005-05-31 11:08:14

Re: has udev updated fsck'ed (literally) my install?

#4 2005-05-31 12:53:17

Re: has udev updated fsck'ed (literally) my install?

#5 2005-06-01 01:19:03

Re: has udev updated fsck'ed (literally) my install?

#6 2005-06-01 06:24:10

Re: has udev updated fsck'ed (literally) my install?

#7 2005-06-01 10:35:23

Re: has udev updated fsck'ed (literally) my install?

#8 2005-06-01 11:35:23

Re: has udev updated fsck'ed (literally) my install?

Board footer