F-12:After installing LIVE-USB to disk - system won't boot

[perazim]

Created custom LIVE image with livecd-creator and copied to USB. This works. Next tried to install from the LIVE-USB to hard drive. Anaconda finished without exception but when system is restarted, it fails part way through bootup sequence.

This is what I see (I had to type this in manually, so it may not be letter perfect):

sd 4:0:0:0: [sdb] assuming drive cache: write through
sd 4:0:0:0: [sdb] assuming drive cache: write through
sd 4:0:0:0: [sdb] assuming drive cache: write through
sd 4:0:0:0: [sdb] assuming drive cache: write through
end_request: I/O error, dev sdb, sector 241254720
Buffer I/O Error on dev sdb, logical block 241254720
end_request: I/O error, dev sdb, sector 241254720
Buffer I/O Error on dev sdb, logical block 241254720
end_request: I/O error, dev sdb, sector 241254720
Buffer I/O Error on dev sdb, logical block 241254720
end_request: I/O error, dev sdb, sector 241254720
Buffer I/O Error on dev sdb, logical block 241254720
end_request: I/O error, dev sdb, sector 241254720
Buffer I/O Error on dev sdb, logical block 241254720
end_request: I/O error, dev sdb, sector 241254720
Buffer I/O Error on dev sdb, logical block 241254720
end_request: I/O error, dev sdb, sector 241254720
Buffer I/O Error on dev sdb, logical block 241254720
end_request: I/O error, dev sdb, sector 241254720
Buffer I/O Error on dev sdb, logical block 241254720
Traceback (most recent call last):
File ""/init", line 157 in <module>
if __name__=='__main__': main()
File "/init",line 129, in main
xo_ver=get_xo_version()
File :/init", line 84, in get_xo_version
raise Exception("Not an XO laptop?")
Exception: Not an XO laptop?
Kernel Panic - not syncing: Attempted to kill init.
[drm:drm_fb_helper_panic] *ERROR* panic occurred, switching back to text console

I then checked for bad sectors on sdb and found none.

I would have tried the STOCK Fedora 12 LIVE desktop image but it won't boot on my Acer AOD250 (this was subject of a previous thread and resolved by blacklisting some modules)

Thanks

[DCC11]

I am having a similar problem. However, I made a LiveCD with Fedora 11 (Fedora-11-i686-Live.iso). I boot to the cd, select the "Boot" option from the fedora menu, and get the same messages as posted above, but without the sd 4:0:0:0 lines.

System specs:

Dell Studio 15
Intel Core 2 Duo 2.66
4gb DDR2 RAM
Windows 7 64 bit (on my internal HD, looking to install Fedora 11 on external)
BIOS: Ver 1.00 A05 PARTTBL

Wouldn't expect these specs to come into play, but posted anyway.

The ISO file was written to disk using ISORecorder V3.

Thanks in advance for any help.

[live11]

Created custom LIVE image with livecd-creator and copied to USB. This works. Next tried to install from the LIVE-USB to hard drive.
.

. . .
Buffer I/O Error on dev sdb, logical block 241254720
end_request: I/O error, dev sdb, sector 241254720
Buffer I/O Error on dev sdb, logical block 241254720
end_request: I/O error, dev sdb, sector 241254720
Buffer I/O Error on dev sdb, logical block 241254720
end_request: I/O error, dev sdb, sector 241254720

. . .

Sorry this won't help shed too much light on the situation, but anyway . . .

I am having a similar problem. However, I made a LiveCD with Fedora 11 (Fedora-11-i686-Live.iso). I boot to the cd, select the "Boot" option from the fedora menu, and get the same messages as posted above,

I'd try a boot and verify in your instance - it takes longer, but it'd rule out that sort of problem with the iso burn.


Anyway . . .
same /similar error message to what I used to experience when first using Fedora 11 Live in the regard of
if the live CD iso was burned to a CD, then all computers WOULD boot up by the DVD ROM drive -

-but, in an old Omnitech that we were refurbishing, a F11 Live iso burned to a DVD could NOT boot in that same DVD drive -
and always gave these same type message.
If that same F11 Live iso (on a DVD disk) were used in any of the bank of Dell and other computers, those DVD drives would boot up the DVD.
In our particular instance, I figured it was a problem with driver and I/O of the DVD trying to boot from that DVD drive on that one computer.

We just had more copies of F11 iso burned to DVD - we all finally just gave up on that one computer/DVD drive, as our CD iso copy on CD could work on that one computer.

[DCC11]

I have tried the boot and verify, I have the same problem.

Would trying to boot to a live USB be something worth trying?

[kyryder]

Hello,
If your bios is capable of booting from usb and you have a empty usb stick that is big enough to hold the install or live cd/dvd you could always just "dd" the dvd.iso or the live.iso to the usb stick and boot from it. I have done this when I don't have a cd/dvd drive in a box or just ran out of cd/dvd's.

[live11]

Running F11 Live on USB is the way to go - at least for me.

If I can boot from USB, I boot from the F11 LiveUSB directly -
(made with liveusb-creator (Windows and linux versions) see :http://fedoraproject.org/wiki/FedoraLiveCD/USBHowTo

If I need to boot from a CD drive, I boot with a ploplinux CD iso in the CD drive and the same USB made with liveusb-creator in the any of the (unbootable) USBs - it must be in place when you start ploplinux so it sees it, and can direct the boot there.

http://www.plop.at/en/ploplinux.html

http://i372.photobucket.com/albums/oo161/sunblush/ploplinux.jpg

http://i372.photobucket.com/albums/oo161/sunblush/ploplinuxusb.jpg

Then the ploplinux CD iso is unmounted and removed, and I can then again still run entirely off the USB.

This is exactly how I am now - on a university computer where my account in Windows Vista -does have alot of software -
but does NOT give me some admin privileges to do some simple file rescue yada yada yada.

Running on a USB is alot faster vs. a CD iso or DVD iso in a CD drive, and especially with any CD drive I/O situations,
but always faster at least for me with F11 Live.

So, yes, even without any problems, I'd run off a USB - my 2 ¢ anyway.

[perazim]

Maybe I was not clear as to my situation:

1) Ran livecd-creator to compose custom f-12

2) Ran livecd-iso-to-disk to copy iso file to USB and set it up.

3) Booted USB flash in PC. Runs fine.

4) Ran Install to hardrive and anaconda copies this LIVE to a hard drive and configures it.

Everything completes fine up until this point.

5) Reboot PC from hard drive just installed. Doesn't boot and this is where I receive the above errors.

This problem has nothing to do with dvd writers.

Perazim

[DCC11]

Sorry peraz, I sort of jacked your thread since your error message was close to mine and didn't want to bother people making a 'dupe' topic. I believe they may have been addressing my problem. Good luck.

(And I am getting a big enough USB today to try this, since the one I have currently cannot be wiped since I need the data).

[Darr247]

Created custom LIVE image with livecd-creator and copied to USB. This works. Next tried to install from the LIVE-USB to hard drive. Anaconda finished without exception but when system is restarted, it fails part way through bootup sequence.

File "/init",line 129, in main
xo_ver=get_xo_version()
File :/init", line 84, in get_xo_version
raise Exception("Not an XO laptop?")
Exception: Not an XO laptop?
Kernel Panic - not syncing: Attempted to kill init.
[drm:drm_fb_helper_panic] *ERROR* panic occurred, switching back to text console


For those who found this thread with a google search, that error is caused by the Dracut - One Laptop Per Child (OLPC) module being installed on a non OLPC computer...

If it was your only installed kernel, boot from the CD/DVD and choose the 'rescue installed system' option, then hammer through the rest of the defaults (enable the network adapter if you want, though I don't think it's necessary), and once you're in the bash shell use the chroot /mnt/sysimage command as noted in the dialog just prior to the shell/diagnostic/reboot menu.

(otherwise, boot from a working kernel and)

do
# yum erase dracut-modules-olpc*

That should get rid of the module causing the kernel panic.

then
# dracut -f /boot/initramfs-(panic'd-kernel-version).img (panic'd-kernel-version)

to make a new ramdisk image.

An example of the dracut command:
# dracut -f /boot/initramfs-2.6.32.11-99.fc12.i686.PAE.img 2.6.32.11-99.fc12.i686.PAE


The -f forces an overwrite... some would counsel mv'ing to *.backup first, but I don't see any sense backing up a ramdisk image that won't boot anyway. YMMV.

I don't recommend using $(uname -r), either, even if you think it's the same kernel you booted from...
instead, just do
# cd /boot
and
# ls
to list the kernel/ramdisk file names so you can double check the dracut command line before you hit enter.

Now when you reboot, the kernel should work fine.