On Mon, Mar 29, 2004 at 10:43:11AM +0200, Nacho de los RÃos Tormo wrote:
| I have installed kernel 2.6.4-1-686-smp using apt-get install, but I
| have not managed to get it to boot. It gets stuck with these messages
| (quoted below from the moment thing start to go wrong): 
| 
|      mount: /dev2/root2 is not a valid block device
|      mount: /dev2/root2 is not a valid block device
|      NTFS driver 2.16 [Flags R/O MODE]
|      mount: /dev2/root2 is not a valid block device
|      mount: /dev2/root2 is not a valid block device
|      mount: /dev2/root2 is not a valid block device
|      EFS: 1.0a - http://aeschi.ch.eu.org/efs
|      mount: /dev2/root2 is not a valid block device
|      mount: /dev2/root2 is not a valid block device
|      mount: /dev2/root2 is not a valid block device
|      mount: /dev2/root2 is not a valid block device
|      pivot-root: no such file or directory
|      /sbin/init: 347
|      cannot open /dev/console: No such file
|      Kernel panic: Attempted to kill init!
| 
| There is indeed no such thing as /dev2 directory in my system. In case
| this had something to do with devfs (though I really don't know much
| about devfs), I added the option "devfs=mount", but it did nothing.
| 
| For what it is worth, upon executing lilo I get: 
| > Warning: '/proc/partitions' does not match '/dev' directory structure.
| >     Name change: '/dev/ide/host2/bus0/target0/lun0/disc' -> '/dev/hde'
| > Added Linux_2.6
| > Added Linux_2.4 *
| > Added Win2000
| 
| The hard disk is a SATA device which works fine under 2.4.24 (as
| /dev/hde) and under W2K.
| 
| Any idea about what's going on?

I know exactly what's going on!  I saw the same messages yesterday
when I moved a machine from plain old IDE to using a 3Ware RAID
controller.  Boot an installer system or knoppix or something, load
the driver for your SATA controller, mount the disk, edit /etc/modules
and list the driver for your disk controller there.  Then chroot to
the disk that's supposed to be your system and run 'dpkg-reconfigure
kernel-image-2.6.4-1-686-smp'.  Running dpkg-reconfigure will rebuild
the initrd image and since /etc/modules now lists the driver needed
for your disk controller that driver will be included in the initrd
and then the kernel will be able to actually see the disk while it
tries to boot.  (at least, that was the situation yesterday with the
RAID card)

-D

-- 
An anxious heart weighs a man down,
but a kind word cheers him up.
        Proverbs 12:25
 
www: http://dman13.dyndns.org/~dman/            jabber: [EMAIL PROTECTED]

Attachment: signature.asc
Description: Digital signature

Reply via email to