As soon as I upgrade udev from 141 to 146 (current) the system stops booting. Tried with kernel 2.6.25-r9 and with 2.6.31-r6 Error: ##########################################33 * Checking root filesystem... fsck.ext3: No such file or directory while trying to open /dev/sda3 /dev/sda3: The superblock could not be read or does not describe a correct ext 2 filessytem. 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 coudn't be fixed :( ##################################### My fstab ##################################### # /etc/fstab: static file system information. # # noatime turns off atimes for increased performance (atimes normally aren't # needed; notail increases performance of ReiserFS (at the expense of storage # efficiency). It's safe to drop the noatime options if you want and to # switch between notail / tail freely. # # The root filesystem should have a pass number of either 0 or 1. # All other filesystems should have a pass number of 0 or greater than 1. # # See the manpage fstab(5) for more information. # # <fs> <mountpoint> <type> <opts> <dump/pass> # NOTE: If your BOOT partition is ReiserFS, add the notail option to opts. ##/dev/BOOT /boot ext2 noauto,noatime 1 2 ##/dev/ROOT / ext3 noatime 0 1 ##/dev/SWAP none swap sw 0 0 ##/dev/cdrom /mnt/cdrom auto noauto,ro 0 0 #/dev/fd0 /mnt/floppy auto noauto 0 0 ### created byME start ************************************************** /dev/sda1 /boot ext2 defaults 1 2 /dev/sda2 none swap sw 0 0 /dev/sda3 / ext3 noatime 0 1 /dev/cdrom /mnt/cdrom auto auto,user 0 0 ###created by ME end *************************************************** # glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for # POSIX shared memory (shm_open, shm_unlink). # (tmpfs is a dynamically expandable/shrinkable ramdisk, and will # use almost no memory if not populated with files) shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 ##################################### I've tried clearing /proc/* and /sys/* as suggested in similar bug report, but that doesn't help. Using gentoo kernel compiled manually each time. System runs on a Vmware ESXi 3.5.0 on AMD Opteron HP ProLiant DL385 G1 in 32bit mode Reproducible: Always Steps to Reproduce: 1.upgrade udev via emerge 2.reboot 3.enjoy unbootable system Actual Results: System is unbootable and complains about nonexistant disk device Expected Results: System should boot after upgrade or stop upgrade if incompatible
Your conclusion in the thread is incorrect, it should be: - "I'll update more often to avoid problem piling up". Did you try to see during that failed boot if device names didn't change (get reordered or something) ? And what do you mean by "I've tried clearing /proc/* and /sys/*" ? That's bit more tricky than it sounds, you need to '-o bind' it and make sure that a few devices are left (IIRC, among other /dev/zero) - search the board and docs for more details.
Hi Rafal, I've tried to update earlier but ran into the same issue. So i rolled back the backup until a later point in time hoping these kinks would be worked out. Still, several udev and gentoo sources releases later - same issue. From what I could tell - drives didn't get renumbered, but do I have a screenshot or log of this? - No. I've seen a bug report on a similar udev issue (which I believe started with baselayout upgrade) that ran into a udev boot crash and the resolution was to issue "rm -rf /sys/* /proc/*" before a reboot. After which users reported their systems back to normal. I think this is the one http://bugs.gentoo.org/show_bug.cgi?id=291916 Others have reported an issue with a kernel feature CONFIG_INOTIFY_USER I've looked for it in kernel and didn't find anything named like that, but found other features referring to it. http://forums.gentoo.org/viewtopic-t-802861-highlight-udev+e2fsck.html I've tried about 3-4 different suggestions and kernel reconfigs with no success.
(In reply to comment #2) > Hi Rafal, > I've tried to update earlier but ran into the same issue. So i rolled back the > backup until a later point in time hoping these kinks would be worked out. > Still, several udev and gentoo sources releases later - same issue. > > From what I could tell - drives didn't get renumbered, but do I have a > screenshot or log of this? - No. > > I've seen a bug report on a similar udev issue (which I believe started with > baselayout upgrade) that ran into a udev boot crash and the resolution was to > issue "rm -rf /sys/* /proc/*" before a reboot. > After which users reported their systems back to normal. > I think this is the one > http://bugs.gentoo.org/show_bug.cgi?id=291916 > > Others have reported an issue with a kernel feature CONFIG_INOTIFY_USER > I've looked for it in kernel and didn't find anything named like that, but > found other features referring to it. > http://forums.gentoo.org/viewtopic-t-802861-highlight-udev+e2fsck.html > > I've tried about 3-4 different suggestions and kernel reconfigs with no > success. > _________________________________________________________________ UPDATE: Alright, not so sure if this is a proper bug or a case of a not so proper kernel configuration. After turning on some options (can't tell you which, changed too many while solving this), i was able to boot my system into 2.6.31-r6.
