hello, please do not drop the list out of the cc.
On Wed, 01 Mar 2006, giorgio wrote: <snip> > >upgrade to latest udev. your box is not up2date. > > Ok. Done. cool. > >>and then stops on a shell prompt, because it cannot mount the root disk > >>(/dev/sdc2) a serial-ata device. > > > > > >did you check if the device is there ls -l /dev/sdc2 > > > > /dev/sdc2 is not present. what does the following command show: cat /proc/cmdline cat /proc/modules > Well I shoot the commands as root and that's the output: > > neo64:/home/giorgio# dpkg-reconfigure linux-image-2.6.15-1-686 > Running depmod. > Finding valid ramdisk creators. > Using mkinitramfs to build the ramdisk. > cpio: ./sbin/vgchange: No such file or directory > Not updating initrd symbolic links since we are being updated/reinstalled > (2.6.15-7 was configured last, according to dpkg) > Not updating image symbolic links since we are being updated/reinstalled > (2.6.15-7 was configured last, according to dpkg) > Running postinst hook /sbin/update-grub. > Searching for GRUB installation directory ... found: /boot/grub > Testing for an existing GRUB menu.list file ... found: /boot/grub/menu.lst > Searching for splash image ... none found, skipping ... > Found kernel: /boot/vmlinuz-2.6.15-1-686 > Found kernel: /boot/vmlinuz-2.6.12-1-686 > Found kernel: /boot/vmlinuz-2.6.8-2-386 > Updating /boot/grub/menu.lst ... done > > > neo64:/home/giorgio# update-initramfs -t -u > cpio: ./sbin/vgchange: No such file or directory > neo64:/home/giorgio# you are still using lvm10, please upgrade to lvm2. although that warning is harmless. > Now if I try to boot with 2.6.15 udev doesn't give me errors, but the > system still drop to a shell prompt. > This is the message: > > ALERT! /dev/sdc2 does not exist. dropping to a shell! > > BusyBox v1.01 (Debian 1:1.01-4)Built in shell (ash) > > Enter 'help' for a list of built-in commands > > /bin/sh:can't access tty; job control turned off > > > Any idea? maybe if you would post what's happening above that, the last lines of "dmesg" might be intersting or with the questions i asked above the picture could get clearer. regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
