Bug#357654: [Etch beta2] Reboot fails with SATA drive on SATA150 Raid 2 Port PCI Host Adapter
On Sat, Mar 18, 2006 at 02:20:03PM -0600, Hugo Vanwoerkom wrote:
> Package: installation-reports
>
> Boot method: debian-testing-i386-netinst.iso
> Image version: http://cdimage.debian.org/cdimage/etch_di_beta2/i386/iso-cd/
> 14-Mar-2006 18:03 115M
>
> Partitions:
>
> Disk /dev/hda: 81.9 GB, 81964302336 bytes
> 16 heads, 63 sectors/track, 158816 cylinders
> Units = cylinders of 1008 * 512 = 516096 bytes
>
> Device Boot Start End Blocks Id System
> /dev/hda1 * 1 12013 6054520+ 83 Linux
> /dev/hda2 12014 158816 73988681 f W95 Ext'd (LBA)
> /dev/hda5 * 12014 23833 5957248+ 83 Linux
> /dev/hda6 * 23834 35653 5957248+ 83 Linux
> /dev/hda7 35654 47473 5957248+ 83 Linux
> /dev/hda8 * 47474 59293 5957248+ 83 Linux
> /dev/hda9 * 59294 67613 4193248+ 83 Linux
> /dev/hda10 * 67614 77925 5197216+ 83 Linux
> /dev/hda11 77926 89369 5767744+ 83 Linux
> /dev/hda12 89370 97689 4193248+ c W95 FAT32 (LBA)
> /dev/hda13 97690 99627 976720+ 82 Linux swap / Solaris
> /dev/hda14 99628 158816 29831224+ 83 Linux
Mmm, six bootable partitions, one will do.
> Disk /dev/hdc: 80.0 GB, 80026361856 bytes
> 255 heads, 63 sectors/track, 9729 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
<snip/>
> /dev/hdc5 2920 3892 7815591 83 Linux
> /dev/hdc6 * 3893 4865 7815591 83 Linux
> /dev/hdc7 4866 9729 39070048+ 83 Linux
seven
> Disk /dev/sda: 80.0 GB, 80026361856 bytes
> 255 heads, 63 sectors/track, 9729 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sda1 * 1 973 7815591 83 Linux
> /dev/sda2 974 1946 7815622+ 83 Linux
<snip/>
> /dev/sda7 4866 9729 39070048+ 83 Linux
eigth
<snip/>
> Install base system: [O]
> Install boot loader: [O]
> Reboot: [E] 999999's all over the screen + hang
>
> Comments/Problems:
>
> Reboot fails with 9's all over the screen. Both with Grub and with Lilo.
Mmm, I think you have to restore the backup of your computer.
Especially the Master Boot Record (MBR) of the disk that computer is
really booting from.
Then try again and make sure that you are over-write the right MBR.
The very least progress you should be making, is that Lilo and Grub
behave different. ( in other words: different boot loaders will
emmit different messages ( none "9999" ))
When you have written the MBR that is actually used,
then I hope you have chosen a bootloader that can read the next part
from the chosen disk(controller)
Cheers
Geert Stappers
Reply to: