sn8kman Posted May 4, 2006 Report Share Posted May 4, 2006 I need some help please. I recently applied some patches and I don't know if any apply to this problem or not. After applying patches to hal, kdelibs, dbus and some others, my mouse locked-up. Restart X and same - no mouse. Reboot and now I don't even get shell login. What I get is something like: /dev/fb0 umount /initrd/sys failed: 16 mounting systs on /sys FATAL: module not found. Then goes on to say: no superblock found on /dev/sda1 e2fsck..... login to repair login and run e2fsck -b 8193 /dev/sda1 and same thing. boot from Knoppix live DVD and run e2fsck /dev/sda1 and says clean. I've checked my fstab and my lilo.conf. Both seem fine. This happens with every kernel version I select in Lilo menu as well as failsafe. Any help is appreciated. [moved from Installing Mandriva by spinynorman] Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted May 4, 2006 Report Share Posted May 4, 2006 What did it say after you ran: e2fsck -b 8193 /dev/sda1 I'm curious, as you said "and same thing", so not sure if you meant you rebooted after and still got the error? How did you do the updates? Did you just select specifics? Or everything that was listed? Quote Link to comment Share on other sites More sharing options...
sn8kman Posted May 4, 2006 Author Report Share Posted May 4, 2006 It said no superblock was found on /dev/sda1 try using e2fsck -b 8193 etc, etc... I updated through mandriva update and from what I can remember, there were some MDE files such as kdelibs-3.5.2-? and libkde's; Non-MDE files: hal-v.v.v, dbus-v.v.v, and clamav, clamd updates. Selected them all except hylafax. Completed normally. While refreshing the selection, mouse locked up. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted May 4, 2006 Report Share Posted May 4, 2006 Sounds like a disk problem to me. ext3 has a way of recovering itself if it gets corrupted as it has two superblocks to read from. If the first one gets trashed, it can use the second superblock to recover. If both superblocks have gone, then you've got problems. Try booting from the livecd and then typing this: dumpe2fs /dev/sda1 and see what it reports back. Using: dumpe2fs -h /dev/sda1 will filter and only display superblock information. Quote Link to comment Share on other sites More sharing options...
sn8kman Posted May 4, 2006 Author Report Share Posted May 4, 2006 (edited) Result: sudo dumpe2fs -h /dev/sda1 dumpe2fs 1.38 (30-Jun-2005) Filesystem volume name: root Last mounted on: <not available> Filesystem UUID: 4c3b741d-0858-4998-9b78-34b3e804b99e Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal filetype sparse_super Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 1311552 Block count: 2622603 Reserved block count: 131130 Free blocks: 2242277 Free inodes: 1270981 First block: 0 Block size: 4096 Fragment size: 4096 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 16192 Inode blocks per group: 506 Filesystem created: Sat Apr 22 05:01:43 2006 Last mount time: Thu May 4 02:04:49 2006 Last write time: Thu May 4 02:39:11 2006 Mount count: 41 Maximum mount count: -1 Last checked: Sat Apr 22 05:01:43 2006 Check interval: 0 (<none>) Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal inode: 8 Default directory hash: tea Directory Hash Seed: 50a955ed-a98c-42eb-9863-a3a747d538da Journal backup: inode blocks so you know, here's my lilo.conf and fstab files: lilo.conf # File generated by DrakX/drakboot # WARNING: do not forget to run lilo after modifying this file default="multimedia_4GB_2.6.14.7" boot=/dev/sda map=/boot/map keytable=/boot/us.klt menu-scheme=wb:bw:wb:bw prompt nowarn timeout=60 message=/boot/message disk=/dev/sda bios=0x80 image=/boot/vmlinuz label="linux" root=/dev/sda1 initrd=/boot/initrd.img append="resume=/dev/sda5 splash=silent" vga=788 image=/boot/vmlinuz label="linux-nonfb" root=/dev/sda1 initrd=/boot/initrd.img append="resume=/dev/sda5 splash=silent" image=/boot/vmlinuz label="failsafe" root=/dev/sda1 initrd=/boot/initrd.img append="failsafe resume=/dev/sda5" image=/boot/vmlinuz-i586-up-1GB label="linux-i586-up-1GB" root=/dev/sda1 initrd=/boot/initrd-i586-up-1GB.img append="resume=/dev/sda5 splash=silent" vga=788 image=/boot/vmlinuz-2.6.12-18mdk-i586-up-1GB label="2612i586up1GB-18" root=/dev/sda1 initrd=/boot/initrd-2.6.12-18mdk-i586-up-1GB.img append="resume=/dev/sda5 splash=silent" vga=788 image=/boot/vmlinuz-i686-up-4GB label="linux-i686-up-4GB" root=/dev/sda1 initrd=/boot/initrd-i686-up-4GB.img append="resume=/dev/sda5 splash=silent" vga=788 image=/boot/vmlinuz-2.6.12-18mdk-i686-up-4GB label="2612i686up4G-18" root=/dev/sda1 initrd=/boot/initrd-2.6.12-18mdk-i686-up-4GB.img append="resume=/dev/sda5 splash=silent" vga=788 image=/boot/vmlinuz-2.6.14-2mdk-i686-up-4GB label="4GB_2.6.14-2" root=/dev/sda1 initrd=/boot/initrd-2.6.14-2mdk-i686-up-4GB.img append="resume=/dev/sda5 splash=silent" vga=788 image=/boot/vmlinuz-2.6.12-18mdk label="2.6.12-18" root=/dev/sda1 initrd=/boot/initrd-2.6.12-18mdk.img append="resume=/dev/sda5 splash=silent" vga=788 image=/boot/vmlinuz-2.6.14-2mdk label="2.6.14-2" root=/dev/sda1 initrd=/boot/initrd-2.6.14-2mdk.img append="resume=/dev/sda5 splash=silent" vga=788 image=/boot/vmlinuz-2.6.14-2mdk-i586-up-1GB label="i586_2.6.14-2" root=/dev/sda1 initrd=/boot/initrd-2.6.14-2mdk-i586-up-1GB.img append="resume=/dev/sda5 splash=silent" vga=788 image=/boot/vmlinuz-2.6.14-0.mm.7mdk-i686-up-4GB label="multimedia_4GB_2.6.14.7" root=/dev/sda1 initrd=/boot/initrd-2.6.14-0.mm.7mdk-i686-up-4GB.img append="resume=/dev/sda5 splash=silent" vga=788 image=/boot/vmlinuz-2.6.14-0.mm.7mdk label="multimedia_2.6.14.7" root=/dev/sda1 initrd=/boot/initrd-2.6.14-0.mm.7mdk.img append="resume=/dev/sda5 splash=silent" vga=788 fstab: # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/sda1 / ext3 defaults 1 1 none /dev/shm tmpfs defaults 0 0 /dev/sda8 /home ext3 defaults 1 2 /dev/sdb2 /home/elavoie/Documents_Backup ext3 defaults 1 2 /dev/sdb3 /home/elavoie/Downloaded_Software ext3 defaults 1 2 /dev/sdb1 /home/elavoie/Ripped_CDs ext3 defaults 1 2 /dev/hdc /mnt/cdrom auto umask=0022,user,iocharset=iso8859-1,codepage=850,noauto,ro,exec,users 0 0 /dev/hdd /mnt/cdrom2 auto umask=0022,user,iocharset=iso8859-1,codepage=850,noauto,ro,exec,users 0 0 none /proc proc defaults 0 0 /dev/sda6 /usr ext3 defaults 1 2 /dev/sda7 /var ext3 defaults 1 2 /dev/sda5 swap swap defaults 0 0 Edited May 4, 2006 by sn8kman Quote Link to comment Share on other sites More sharing options...
sn8kman Posted May 4, 2006 Author Report Share Posted May 4, 2006 if it means anything, here's my /mnt/sda1/etc/rc.d/init.d/udev file: #! /bin/bash # # udev init script to setup /udev # # description: manage user-space device nodes in /udev . /etc/rc.d/init.d/functions . /etc/udev/udev.conf # strip trailling slash: udev_root=/dev udev_root2=${udev_root}.old UDEVSTART=/sbin/udevstart HELPERS_PATH=/lib/udev sysfs_dir=/sys # default maximum size of the /dev tmpfs tmpfs_size="10M" case "$(uname -r)" in 2.[012345].*) gprintf "udev requires a 2.6.x kernel, not started.\n" exit 1 ;; esac # don't use udev if devfs is in use. if [ -e $udev_root/.devfsd ]; then gprintf "devfsd used instead of udev!!!\n" exit 1 fi # we need to unmount /dev/pts/ and remount it later over the tmpfs unmount_devpts() { if grep -q $1/pts /proc/mounts; then umount -l $1/pts/ fi if grep -q $1/shm /proc/mounts; then umount -l $1/shm/ fi } # mount a tmpfs over /dev, if somebody did not already do it mount_tmpfs() { if ! grep -E -q "^[^[:space:]]+ $udev_root tmpfs" /proc/mounts; then unmount_devpts $udev_root mount -n -o size=$tmpfs_size,mode=0755 -t tmpfs none $udev_root fi make_extra_nodes if ! grep -q $udev_root/pts /proc/mounts; then mount -n -t devpts -o mode=620 none $udev_root/pts fi if ! grep -q $udev_root/shm /proc/mounts; then mount -n -t tmpfs none $udev_root/shm fi } make_node () { dev="$1" type="$2" major="$3" minor="$4" if [ "$type" = c -a ! -c "$dev" -o "$type" = b -a ! -b "$dev" ]; then rm -f "$dev" mknod "$dev" "$type" "$major" "$minor" fi } make_extra_nodes () { # there are a few things that sysfs does not export for us. # these things are listed in /etc/udev/links.conf grep '^[^#]' /etc/udev/links.conf | \ while read type name arg1; do [ "$type" -a "$name" -a ! -e "$udev_root/$name" -a ! -L "/dev/$name" ] ||continue case "$type" in L) ln -s $arg1 $udev_root/$name;; D) mkdir -p $udev_root/$name;; M) mknod --mode=600 $udev_root/$name $arg1;; *) gprintf "links.conf: unparseable line (%s %s %s)\n" "$type" "$name" "$arg1";; esac done } # When modifying this script, do not forget that between the time that # the new /dev has been mounted and udevstart has been run there will be # no /dev/null. This also means that you cannot use the "&" shell command. ############################################################################## case "$1" in start) [ "`runlevel`" != "unknown" -a -f /var/lock/subsys/udev ] && exit 0 [[ -d /var/lock/subsys/ ]] && touch /var/lock/subsys/udev 2> /dev/null fgrep -q '/dev ' /proc/mounts && [[ -e /$udev_root/.started ]] && exit 0 # don't use udev if sysfs is not mounted. if [ ! -d $sysfs_dir/block ]; then echo not starting because /sys is not mounted exit 1 fi if [ ! -d $udev_root ]; then mkdir $udev_root fi # we'd better handle this in an udev event: [[ -e /sys/class/firmware/timeout ]] && echo 50 > /sys/class/firmware/timeout # Creating initial udev device nodes: mount_tmpfs touch $udev_root/.started # udev uses a netlink, kernel.hotplug isn't needed echo "" > /proc/sys/kernel/hotplug udevd -d # propagate /udev from /sys - we only need this while we do not # have initramfs and an early user-space with which to do early # device bring up (aka coldplug) PKLVL=$(cut -f1 /proc/sys/kernel/printk) sysctl -n -w kernel.printk=0 $UDEVSTART $HELPERS_PATH/udev_input_coldplug start sysctl -n -w kernel.printk=$PKLVL action "Start %s\n" udev /bin/true for i in /etc/udev/conf.d/*; do [[ "$i" = ${i%\~} ]] && [[ -x $i ]] && $i; done pam_console_apply ;; stop) rm -f /var/lock/subsys/udev $udev_root/.started exit 0 ;; force-stop) killall udevd [[ ! -d $udev_root2 ]] && mkdir $udev_root2 mount --move $udev_root $udev_root2 unmount_devpts $udev_root2 # unmounting with -l should never fail action "Stopping %s" udev umount -l $udev_root2 2>/dev/null sysctl -n -w kernel.hotplug="/sbin/hotplug" >/dev/null 2>&1 rmdir $udev_root2 rm -f /var/lock/subsys/udev ;; status) if [ -f /var/lock/subsys/udev ]; then action "%s is running\n" udev /bin/true exit 0 fi action "%s is stopped\n" udev /bin/true exit 3 ;; restart) [[ -f /var/lock/subsys/udev ]] || exit 0 $UDEVSTART pam_console_apply ;; force-reload) $0 force-stop $0 start service syslog restart ;; reload) $0 restart ;; *) gprintf "Usage: %s {start|stop|status|restart|force-reload|force-stop}\n" "$0" exit 1 esac exit 0 Quote Link to comment Share on other sites More sharing options...
sn8kman Posted May 4, 2006 Author Report Share Posted May 4, 2006 Also, I've checked and my udevstart and all the udev files in /sbin have been updated as of yesterday - the day I got this issue. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted May 4, 2006 Report Share Posted May 4, 2006 I honestly think it's nothing to do with lilo, fstab or anything like that. I think your filesystem is screwed and I think you should copy the data off, before it's too late. Then, do a clean install, recreating your partition from scratch, maybe use reiserfs instead of ext3. If it's failing to find superblocks, I'm unsure how you can recover this without recreating the filesystem and this will probably be your quickest way. Quote Link to comment Share on other sites More sharing options...
sn8kman Posted May 4, 2006 Author Report Share Posted May 4, 2006 I don't understand. Is it still failing to find superblocks in Knoppix? sudo dumpe2fs -h /dev/sda1 dumpe2fs 1.38 (30-Jun-2005) Filesystem volume name: root Last mounted on: <not available> Filesystem UUID: 4c3b741d-0858-4998-9b78-34b3e804b99e Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal filetype sparse_super Default mount options: (none) Filesystem state: clean Seems like the drive integrity is fine. Are you saying that the linux kernel or something is corrupted and that's why I should reinstall? Forgive me if I seem stubborn, but I'd hate to revert to a windows-like solution of format and reinstall. Quote Link to comment Share on other sites More sharing options...
sn8kman Posted May 5, 2006 Author Report Share Posted May 5, 2006 Ok, here's what I'm currently doing - if this doesn't work then I'll clean install mandriva; sudo dd if=/dev/sda1 of=/dev/sdb3/sda1 sudo umount /dev/sda1 <run Qtparted and format sda1> sudo mount -rw /dev/sda1 /mnt/sda1 sudo dd if=/mnt/sdb3/sda1 of=/dev/sda1 <reboot mandriva and see if anything changed> Anyway, it may not change a darn thing, but at least I'll know. Now to just wait for dd to finish Quote Link to comment Share on other sites More sharing options...
sn8kman Posted May 5, 2006 Author Report Share Posted May 5, 2006 Hmm, nope - didn't work. I've installed Kubuntu for the moment just to see if I'm going to take the easy way out with a clean-install with 3.5.2 already included, but so far I'm hating it. Out of curiosity, has anyone made a full distro image with Mandriva 2006 and MDE/KDE 3.5.2 yet? That would be awesome! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.