[SOLVED] Cannot boot OS installed from mylivecd

[ternor]

I have installed PCLinuxOS from a remaster created by mylivecd.  Everything went well until I tried to boot the new installation.

On the first occasion, I waited until I was certain the system was not booting.  I pressed the ESC key and saw a message to the effect that the address was already in use.

On the second occasion I pressed ESC immediately after selecting the boot option and got a message to the following effect:

Cannot open file delete
Press I for interactive
starting udev_

I pressed 'i' and 'I'; nothing happened.  I pressed 'Enter' and nothing happened.

What to do?  Thanks.

[AS]

Hi ternor,

if you have burned a CD/DVD compare the md5sums against the ISO image
md5sum <mylivecdfilename.iso>
put your CD/DVD into the drive and type:
md5sum /dev/sr0
(eventually use /dev/sr1 for the second CD/DVD unit)

if the results of the md5sums match, proceed as follow:

at grub screen, press F3 (options) and change the following parameter splash=silent to splash=verbose and retry to boot, hopefully you should see the whole boot process.

Additionally, from the already installed system post the output from the following commands:
open a Konsole, type su, type in your root password:

uname -r
lspci
cat /boot/grub/menu.lst

AS

[ternor]

Thanks.  I should have mentioned that the md5sum is correct.

This is what I get using those commands:

Code:

# uname -r
2.6.38.8-pclos1.bfs
# lspci
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:05.0 VGA compatible controller: nVidia Corporation C51G [GeForce 6100] (rev a2)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a2)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a2)
00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a2)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.2 Multimedia audio controller: nVidia Corporation MCP51 AC97 Audio Controller (rev a2)
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
04:08.0 Communication controller: Conexant Systems, Inc. HSF 56k HSFi Modem (rev 01)
# cat /boot/grub/menu.lst
timeout 10
color black/cyan yellow/cyan                                                                                 
gfxmenu (hd0,1)/boot/gfxmenu
default 0

title linux
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=1771da4a-dc0d-4a10-b388-30eae8e39691 quiet nokmsboot vmalloc=256M acpi=on resume=UUID=a3ebe1ab-ca95-4d8e-a144-9a78deeceeff splash=silent vga=788
initrd (hd0,1)/boot/initrd.img

title linux_nonfb
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux_nonfb root=UUID=1771da4a-dc0d-4a10-b388-30eae8e39691 quiet nokmsboot vmalloc=256M acpi=on resume=UUID=a3ebe1ab-ca95-4d8e-a144-9a78deeceeff
initrd (hd0,1)/boot/initrd.img

title failsafe
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=1771da4a-dc0d-4a10-b388-30eae8e39691 quiet nokmsboot failsafe vmalloc=256M acpi=on
initrd (hd0,1)/boot/initrd.img

title PCLinuxOS (sda9)
root (hd0,8)
configfile /boot/grub/menu.lst

title PCLinuxOS (sda3)
root (hd0,2)
configfile /boot/grub/menu.lst

title 2.6.38.8-pclos1.bfs
kernel (hd0,1)/boot/vmlinuz-2.6.38.8-pclos1.bfs BOOT_IMAGE=2.6.38.8-pclos1.bfs root=UUID=1771da4a-dc0d-4a10-b388-30eae8e39691 quiet nokmsboot vmalloc=256M acpi=on resume=UUID=a3ebe1ab-ca95-4d8e-a144-9a78deeceeff splash=silent vga=788
initrd (hd0,1)/boot/initrd-2.6.38.8-pclos1.bfs.img

title memtest-4.20
kernel (hd0,1)/boot/memtest-4.20 BOOT_IMAGE=memtest-4.20

[AS]

Don't see relevant things ... restart from here:

On the first occasion, I waited until I was certain the system was not booting.  I pressed the ESC key and saw a message to the effect that the address was already in use.

On the second occasion I pressed ESC immediately after selecting the boot option and got a message to the following effect:

Cannot open file delete
Press I for interactive
starting udev_

use the splash=verbose option, additionally delete the quiet option and try to report the exact error ...

[ternor]

OK.  Will report after trying to boot that installation again using F3, deleting 'quiet' and changing to 'splash=verbose'.

[ternor]

I have done as suggested.  The last 4 messages on the screen after attempting to boot were to the following effect:

Code:

usb core registered new interface driver usbfs
usb core registered new interface driver hub
usb core registered new interface driver usb
_

The boot sequence stopped at that point.  What now, please?

[djohnston]

What devices are plugged into the USB ports while you are trying to boot? Are you booting from an internal DVD drive or an external USB connected DVD drive? If it's external, is the drive plugged directly into a computer port, or is it plugged into a USB hub?

[ternor]

I am booting from the hard drive.  No removable media are inserted.  No device is plugged into a usb port.

[AS]

I am booting from the hard drive.  No removable media are inserted.  No device is plugged into a usb port.

It appear you have 3 installation of PCLinuxOS, sda2, sda3, sda9. Which one is the problematic one ?
Also, did you have a separate /boot partition ?
Can you post the output of the command
fdisk -l
(where "-l" is -L but lowercase)

[ternor]

Thanks.  The problematic one is sda9.  There is no separate boot partition.

Code:

# fdisk -l

Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0003beeb

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63    20964824    10482381   83  Linux
/dev/sda2        20964825    41929649    10482412+  83  Linux
/dev/sda3        41929650    62894474    10482412+  83  Linux
/dev/sda4        62894475   234436544    85771035    5  Extended
/dev/sda5        62894538    64998989     1052226   82  Linux swap / Solaris
/dev/sda6        64999053    67103504     1052226   82  Linux swap / Solaris
/dev/sda7        67103568   171526004    52211218+  83  Linux
/dev/sda8       171526068   192490829    10482381   83  Linux
/dev/sda9       192490893   213455654    10482381   83  Linux
/dev/sda10      213455718   234436544    10490413+  83  Linux

[Just18]

title PCLinuxOS (sda9)
root (hd0,8)
configfile /boot/grub/menu.lst

Can you locate a full boot stanza for this entry and try to use it?

Maybe copy it to the menu.lst you are using, after the above entry, and titled so you recognise it ....

Such a boot stanza should be in  /boot/grub/menu.lst  on /dev/sda9

[ternor]

That stanza opens the grub menu from sda9.  On that menu, the first (default) stanza is the one I would copy to menu.lst.  Initially, after I installed to sda9 from the remaster, the mbr was from sda9.  When I tried to boot, the boot failed so I used the equivalent stanza in the sda9 menu.lst to call the grub menu from sda2, booted that installation and used 'redo-mbr'.

The following is menu.lst from sda9:

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,8)/boot/gfxmenu
default 0

title linux
kernel (hd0,8)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=d539486c-0bac-4def-b63a-fef43459f733  quiet nokmsboot vmalloc=256M acpi=on resume=UUID=a3ebe1ab-ca95-4d8e-a144-9a78deeceeff splash=silent vga=788
initrd (hd0,8)/boot/initrd.img

title linux_nonfb
kernel (hd0,8)/boot/vmlinuz BOOT_IMAGE=linux_nonfb root=UUID=d539486c-0bac-4def-b63a-fef43459f733  quiet nokmsboot vmalloc=256M acpi=on resume=UUID=a3ebe1ab-ca95-4d8e-a144-9a78deeceeff
initrd (hd0,8)/boot/initrd.img

title failsafe
kernel (hd0,8)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=d539486c-0bac-4def-b63a-fef43459f733  quiet nokmsboot failsafe vmalloc=256M acpi=on
initrd (hd0,8)/boot/initrd.img

title PCLinuxOS sda2 (PCLinuxOS)
root (hd0,1)
configfile /boot/grub/menu.lst

title PCLinuxOS sda3 (PCLinuxOS)
root (hd0,2)
configfile /boot/grub/menu.lst

The first stanza is the one I have been using to try to boot sda9.  Would it make a difference to copy it to the grub menu from sda2? 

[Just18]

The first stanza is the one I have been using to try to boot sda9.  Would it make a difference to copy it to the grub menu from sda2?

Have you tried any of the other boot options from that list? ......  failsafe?

[ternor]

Thanks.  No, but I did try changing the options to "splash=verbose" and deleting 'quiet'.  I will try 'linux_nonfb' and 'failsafe' tomorrow and get back here afterwards.

[ternor]

I tried the other boot options.  In each case the message 'cannot open file delete' and the boot stanza were displayed, then nothing.