Re: Another sata failure report
Morten Bo Johansen <firstname.lastname@example.org> writes:
> With this iso image
> sid-amd64-netinst.iso 11-Feb-2005 09:01 193M
> I was actually able to perform an installation of the base system. With
> previous images, either my sata disk was not detected or I got a kernel
> panic during the first boot of the installer. So this was a step in the
> right direction. However my happiness did not last for long: After
> having finished the installation by answering yes to installing grub in
> the master boot record, I booted the system only to find that grub was
> not installed correctly. I had to use a grub boot diskette to reinstall
Thats bad, very bad. Does the latest i386 installer work?
> grub to make my old system bootable. I loaded my old system and updated
> menu.lst to include the newly installed system and rebooted. Booting the
> system I just installed from the iso image above, I got:
> ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xEA00 irq 11
> ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xEA08 irq 11
> ata1 is slow to respond, please be patient
> ata1 failed to respond (30 sec)
> scsi0 : sata_nv
> pivot_root: no such file or directory
> /sbin/init: 431: Cannot open dev/console: No such file or directory
> Kernel panic: Attempted to kill init!
Did you use the same kernel as D-I uses? Try sticking with the generic
one and the same version number. Is the root device detected as the
same device as under D-i?
Anyway, this problem is a mkinitrd bug and needs to be fixed there.