Public bug reported:
Upgraded server from 6.06 LTS to 8.04 LTS using the instructions at
https://help.ubuntu.com/community/HardyUpgrades
Power the machine down, power back up and some timed the machine fails
to mount its root fs and drops me to a BusyBox shell, terminal output
looks like (based on attached photo);
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.24-19-server root=UUID=159c98b4-db88-438e-8384-fb37d94b20b3
ro quiet
[Linux-bzImage, setup=0x2a00, size=0x1e25b8]
initrd /initrd.img-2.6.24-19-server
[Linux-initrd @ 0x1f84f000, 0x7a0522 bytes]
Loading, please wait...
[ 22.411768] 8139cp 0000:00:13.0: This (id 10ec:8139 rev 10) is not an 8139C+
compatible chip
[ 22.411828] 8139cp 0000:00:13.0: Try the "8139too" driver instead.
mount: Mounting /dev/disk/by-uuid/159c98b4-db88-438e-8384-fb37d94b20b3 on
/root failed: Device or resource busy
mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory
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.1.3 (Debian 1:1.1.3-5ubuntu12) Built-in shell (ash)
However sometimes the machine starts up fine, in which case the terminal
output looks like (additional photo to follow)
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.24-19-server root=UUID=159c98b4-db88-438e-8384-fb37d94b20b3
ro quiet
[Linux-bzImage, setup=0x2a00, size=0x1e25b8]
initrd /initrd.img-2.6.24-19-server
[Linux-initrd @ 0x1f84f000, 0x7a0522 bytes]
Loading, please wait...
[ 22.411768] 8139cp 0000:00:13.0: This (id 10ec:8139 rev 10) is not an 8139C+
compatible chip
[ 22.411828] 8139cp 0000:00:13.0: Try the "8139too" driver instead.
* Setting the system clock
[EMAIL PROTECTED]:~$ ls -lah
/dev/disk/by-uuid/159c98b4-db88-438e-8384-fb37d94b20b3
lrwxrwxrwx 1 root root 10 2008-07-01 16:04
/dev/disk/by-uuid/159c98b4-db88-438e-8384-fb37d94b20b3 -> ../../sda6
I have examined the jumper settings of my HDDs as a bug suggested that libata
is much more strict on timings for reply, even with Primary Master, Primary
Slave and Secondary Master all jumpered correctly (no cable select) and in the
correct positions on the IDE ribbon cables I still get this problem.
Any suggestions?
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
hardy mounting on root file system failed device or resource busy
https://bugs.launchpad.net/bugs/244421
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
