| 2006-05-11 19:41:00 |
therunnyman |
bug |
|
|
added bug |
| 2006-05-11 19:43:27 |
therunnyman |
description |
Binary package hint: grub
On installing Dapper from a Beta 2 install disc, then performing the forced reboot, this message appears:
-----
Okay booting the kernel yadda yadda
mount: Mounting /root/dev on /dev/.static/dev failed: No such device
mount: Mounting /sys on /root/sys failed: No such file or directory
mount: Mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have /sbin/init
BusyBox v1.00-pre10 (Debain 20040623-1ubuntu22) Built-in shell (ash)
Enter 'help' for a list of built-in commands
-----
The relevant specs of the machine are one ATA (sda and sdb) hard disks and one SATA hard disk (sdc). Dapper installed on sda [1,5], Breezy installed on sdb [1,5], and two storage partitions on sdc [1,2].
The hack to correct the problem was to edit menu.lst on sda1 from sdb1 (Breezy), changing the line:
/boot/vmlinuz-2.6.15-22-386 root=/dev/sda1 ro quiet splash
to
/boot/vmlinuz-2.6.15-22-386 root=/dev/sdb1 ro quiet splash
This loads Dapper. Now the issue is Dapper doesn't appear to know where it is (sometimes it thinks it's sda1, other times sdb1), and it never knows where it is in relation to the other hard disks (sdb mounts as sda, sdc mounts as sdb, and so on). |
Binary package hint: grub
On installing Dapper from a Beta 2 install disc, then performing the forced reboot, this message appears:
-----
Okay booting the kernel yadda yadda
mount: Mounting /root/dev on /dev/.static/dev failed: No such device
mount: Mounting /sys on /root/sys failed: No such file or directory
mount: Mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have /sbin/init
BusyBox v1.00-pre10 (Debain 20040623-1ubuntu22) Built-in shell (ash)
Enter 'help' for a list of built-in commands
-----
The relevant specs of the machine are two ATA (sda and sdb) hard disks and one SATA hard disk (sdc). Dapper installed on sda [1,5], Breezy installed on sdb [1,5], and two storage partitions on sdc [1,2].
The hack to correct the problem was to edit menu.lst on sda1 from sdb1 (Breezy), changing the line:
/boot/vmlinuz-2.6.15-22-386 root=/dev/sda1 ro quiet splash
to
/boot/vmlinuz-2.6.15-22-386 root=/dev/sdb1 ro quiet splash
This loads Dapper. Now the issue is Dapper doesn't appear to know where it is (sometimes it thinks it's sda1, other times sdb1), and it never knows where it is in relation to the other hard disks (sdb mounts as sda, sdc mounts as sdb, and so on). |
|
| 2006-05-12 17:17:06 |
Simon Law |
grub: status |
Unconfirmed |
Needs Info |
|
| 2006-05-12 17:17:06 |
Simon Law |
grub: statusexplanation |
|
|
|
| 2006-05-12 20:09:57 |
Simon Law |
title |
Dapper Beta 2 install misrecognizes S/ATA drives |
SATA drives initialized in different orders |
|
| 2006-05-12 20:53:31 |
Ben Collins |
linux-source-2.6.15: status |
Needs Info |
Confirmed |
|
| 2006-05-12 20:53:31 |
Ben Collins |
linux-source-2.6.15: statusexplanation |
|
This is basically a bug in the installer, IMO. The only thing that orders the drives is the order that the drivers were loaded (something the kernel has no control over).
The difference is that the installer loads in a different order than udev. This inconsistency has been shown before, so this bug is probably a duplicate. From what I can tell, the installer needs to more closely match what udev does. |
|
| 2009-01-31 15:07:42 |
Martin Mai |
debian-installer: status |
Confirmed |
Incomplete |
|
| 2009-01-31 15:07:42 |
Martin Mai |
debian-installer: statusexplanation |
This is basically a bug in the installer, IMO. The only thing that orders the drives is the order that the drivers were loaded (something the kernel has no control over).
The difference is that the installer loads in a different order than udev. This inconsistency has been shown before, so this bug is probably a duplicate. From what I can tell, the installer needs to more closely match what udev does. |
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance. |
|
| 2009-04-05 12:08:22 |
nglnx |
debian-installer (Ubuntu): status |
Incomplete |
Invalid |
|
| 2012-05-29 15:17:09 |
Curtis Hovey |
removed subscriber Registry Administrators |
|
|
|
