|
|
| Post Number: 1
|
ajkannan83 
Group: Members
Posts: 8
Joined: Apr. 2011
|
 |
Posted on: Apr. 07 2011,02:48 |
|
   |
I was created mulitboot images Windows XP, Fedora 14 live cd.
Windows XP working fine.
But the fedora linux
The following error message is appeared when linux booting.
"No root device found. Boot has failed, sleeping forever "
How to solve this
|
 |
|
|
| Post Number: 2
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Apr. 07 2011,08:00 |
|
 |
@ajkannan83
As you are a new member I say welcome @ajkannan83 
Quote: "No root device found. Boot has failed, sleeping forever"
I downloaded latest Fedora from HERE
I’m not able to launch this application what ever I was trying – I tested following:
1. Used my script easyboot-iso.script to launch ISO as it is – but failed
2. Extracted everything from ISO to folder disk1 and used menu command: bootinfotable;run fedora.bif – but failed
3. Used bcdw-command: bcdw /efi/boot/isolinux.bin – but failed
Note: in all above tested ways fedora launches correctly the “boot-sequense” but as you said: "No root device found. Boot has failed, sleeping forever" was all I got in the end 
I finally tested downloaded ISO directly using Microsofts “virtual pc” but was presented with; “unexpected error”!
Tested using Qemu and here it worked a little bit longer but seems to stall and then doing nothing
Looks as “Mission Impossible” (maybe I shall call Tom Cruise for a solution  )
Sorry no solution in sights
Google some and it seems that fedora is a kind of trouble-maker
Perhaps you should use some other linux/isolinux application instead of this tiresome fedora 
balder
--------------
Download complete set of scripts including help file HERE
Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
|
|
|
| Post Number: 3
|
pica
Group: Members
Posts: 25
Joined: Oct. 2009
|
|
Posted on: Apr. 07 2011,22:23 |
|
|
"3. Used bcdw-command: bcdw /efi/boot/isolinux.bin – but failed"
I'm sure You can figure it out: http://www.ezbsystems.com/cgi-bin/ikonboard.cgi?act=ST;f=1;t=2071;st=10
On my test it works 100%.
Important: CDLABEL must be matched
It will work fine also on usb flash drive or usb external HDD using grub4dos.
You need UUID
|
|
|
|
| Post Number: 4
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Apr. 08 2011,03:12 |
|
|
@pica
@ajkannan83
Quote: ” Important: CDLABEL must be matched”
Yes I know – and that’s what I think is rather stupid
I googled and have already found - as you say - that path-name to CDLABEL is mandatory
You can easily integrate DSL, Knoppix, bitdefender, YLMF etcetera without setting path to label.
And it also works from USB without setting label – but not Fedora
Take attention to that from this point I’m talking about Easyboot and its menu system with built-in menu commands:
I did following:
1. extracted everything from fedora ISO-file to the root (folder disk1)
2. extracted boot-file from fedora ISO-file (used UltraIso for this operation) and saved boot-file in folder ezboot with the name fedora.bif
3. used menu command in EasyBoot: bootinfotable;run fedora.bif
4. before creating ISO I opened folder “isolinux” and modified isolinux.cfg to “CDLABEL=BootMenu” (BootMenu is what EasyBoot set as label for its created ISO)
5. tested “Joliet” and not “Joliet”
Same result: “No root device found. Boot has failed, sleeping forever"
Fedora was still unable to find the “CDLABEL”
BUT – now I found out that I’m getting sloppy – I totally forgot to open folder EFI\boot and there I found another “isolinux.cfg”-file
@pica is right – it is possible to launch Fedora14 and I could use the “frugal solution” like this:
1. Extracted folder “LiveOS” from fedora-iso-file to folder disk1 in easyboot
2. Deleted folder “LiveOS” in fedora-iso-file as I now have the fedora “system-folder” on the root (folder disk1 in Easyboot).
3. I extracted file “isolinux.cfg” from folder EFI\boot in this now reduced Fedora-ISO-file to a temporary folder and used notepad to replace all occurrences of text CDLABEL=Fedora-14-i686-Live-Desktop to CDLABEL=BootMenu and injected back the modified file to EFI\boot and did the same for “isolinux.cfg” in folder “isolinux” and injected back changed “isolinux.cfg” and finally saved changes to ISO-file.
4. I used my script easyboot-iso.script to integrate reduced and modified Fedora-ISO-file to EasyBoot.
5. When creating ISO I checked “Joliet” as it is mostly needed for other reasons – it’s vital Fedora can work with “Joliet” checked – AND IT DID WORK
Note: it’s possible that downloaded fedora-ISO-file has a different name than download I used (Fedora-14-i686-Live-Desktop)
Conclusion: I’m getting sloopy as I only modified “isolinux.cfg” in folder isolinux but forgot to make same changes tp “isolinux.cfg” in EFI\boot-folder
This works for CD\DVD-unit but not for USB device - as @pica correctly points out – you need to set ID for that particular USB device in “isolinux.cfg” as well.
Thanks @pica  for putting me up on the right track - let’s call it; the “less sloppy-track”
Regards balder
--------------
Download complete set of scripts including help file HERE
Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
|
|
|
| Post Number: 5
|
pica
Group: Members
Posts: 25
Joined: Oct. 2009
|
|
Posted on: Apr. 09 2011,00:27 |
|
|
I knew, You can do it, Congratulation!
This is the [URL=http://www.fedoraforum.org/forum/showthread.php?t=190427 ]link[/URL] how to find uuid & the uuid of my giga multiboot on multipartitions USB external HDD using GRUB4DOS:
70 windows&Linux-distros work so far.
About 90% of them work fine on NTFS partition and around 10% must be on vfat partition.
# blkid
/dev/loop0: TYPE="squashfs"
/dev/sda1: LABEL="XPortable" UUID="84806D08806D0252" TYPE="ntfs"
/dev/sda3: UUID="5aca34c0-2cda-4cec-86c0-dba39ecdd35c" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda4: UUID="31C0-6C18" TYPE="vfat"
/dev/sda5: LABEL="All ISOs" UUID="1300EFD94968622C" TYPE="ntfs"
/dev/sda6: LABEL="All Extracts" UUID="3D2F99265A616DE4" TYPE="ntfs"
#
I'm stuck right now with Gnacktrack & Opensuse?.
|
|
|
|
| Post Number: 6
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Apr. 09 2011,02:24 |
|
|
@pica
Yes I know it’s fairly easy to launch distros from USB device using grub4dos – this is well known
However in THIS forum we are dealing how to launch distros using EasyBoot menu
I have proved that it is possible to launch different distros and applications - not only DOS/Int13 distros - but also ISO-files (or part of ISO-files using the "frugal solution") from EasyBoot menu on CD\DVD - including launch these applications using EasyBoot menu - from USB (with some workarounds) 
I’m not sure you to 100% use EasyBoot menu to launch all you distros (including USB approach) – or do you
Quote: “how to find uuid”
That’s no problem for me.
I already have this “ID-check” built-in to my “USB-related scripts” – script automatically examines USB device and can set size, type etcetera to format with the right parameters etcetera
He, he I still think fedora and some other distros are “tiresome” as they are so “nitpicking” with path (no automatic search for base-files)
balder
Edited by balder on Apr. 09 2011,08:43
--------------
Download complete set of scripts including help file HERE
Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
|
|
|
| Post Number: 7
|
ajkannan83
Group: Members
Posts: 8
Joined: Apr. 2011
|
|
Posted on: Apr. 11 2011,06:43 |
|
|
Thanks for your reply.
Suppose i added Windows XP and Fedora 14 Live CD.
When i create ISO tick the Joliet Check Box.
Fedora 14 Live CD Working Fine. But Windows XP not loaded properly.
When i create ISO untick the Joliet Check Box.
Windows XP Working fine. But Fedora 14 Live CD failed.
How to solve this.
|
|
|
|
| Post Number: 8
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Apr. 11 2011,10:46 |
|
|
@ajkannan83
Quote: ”Fedora 14 Live CD Working Fine. But Windows XP not loaded properly”
Well checking “Joliet” shouldn’t in normal case disturb setup of WinXP
However, I’m pretty sure there must be something else you have done
Do you have “Allow Lower Case” checked when creating ISO (having Hiren in build or similar)?
You don’t need to check “Allow Lower Case” to build WinXP and\or Fedora. In fact, you shall only check “Allow Lower Case” when it is “mandatory” for the complete ISO to work (Hiren for example).
However, in some cases it is needed to check “Allow Lower Case”.
To solve issue with WinXP follow tutorials below.
Note: You are recommended to use solution A as first choice as all files and folder in folder disk1 in EasyBoot is uppercased by script if using solution B.
Solution A - when you need to have “Allow Lower Case” checked and solve problem with WinXP:
1. Start your project with integrating setup of WinXP
2. Use “easyboot-uppercase.script” (make sure you choose “Uppercase to all files and folders” in script). Use “help-button before you push the start-button in script. This script run uppercase to all files and folders. You only need to run uppercase to files in folder i386 and then manually rename folder i386 to I386 (uppercased letter “I”).
3. Continue with fedora as already described
4. Create ISO that now work regardless if you have “Allow Lower Case” checked or not as files in folder I386 is uppercased=BIG LETTERS
Or use solution B - when you need to have “Allow Lower Case” checked and solve problem with WinXP:
1. Integrate WinXP as usual.
2. When you run “easyboot-iso.script” to reduced fedora ISO-file, you check “Run uppercase to files and folders” in script. This solves your problem with WinXP. Don’t forget to uncheck “Run uppercase to files and folders” in script as this should be used with cautiousness.
3. Create ISO
That should do it
balder
--------------
Download complete set of scripts including help file HERE
Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
|
|
|
| Post Number: 9
|
ajkannan83
Group: Members
Posts: 8
Joined: Apr. 2011
|
|
Posted on: Apr. 12 2011,05:38 |
|
|
Hello Balder
Thank U.
I ask another one doubt. For example I want to create Multiboot CD for Windows XP SP3, ERD Commander 2009, Windows 2003 R2. Hiren Boot CD10.0.
But when create all in one windows xp, Erd commander, windows 2003 r2, hiren boot cd except fedora 14 live cd all are working normally.
But I add fedora live cd and make iso tick the joliet box the following error for each operating system.
Windows XP : Working normally
Windows 2003 R2 : The file acpi.sys is corrupted.
ERD Commander 2009 : Failed to install network adapter -- check WINBOM
Hiren Boot CD 10.0 : Working normally.
Fedora Live CD : Working Normally.
How to rectify the problem in Windows 2003, ERD Commander.
When uncheck Joliet check box all are working except Fedora 14 Live CD.
|
|
|
|
| Post Number: 10
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Apr. 12 2011,06:48 |
|
|
@ajkannan83
Quote: ”But I add fedora live cd and make iso tick the joliet box the following error for each operating system and Windows 2003 R2 : The file acpi.sys is corrupted”
File acpi.sys is the Automatic- Configuration Power-Interface - basically a driver which will attempt to throttle CPU usage when temperatures get to high.
It sure is a strange behaviour
Is this Windows 2003 R2 by any chance a “special” version?
Did you run nLight to source or something?
However you can test run “Uppercase” to folder Windows 2003 R2 – the same procedure as described in post nr; 8.
Make sure you also use “Uppercase” (BIG LETTERS) to that folder holding setup-files for Windows 2003 R2 as well.
----------------------------------------------
Quote: “ERD Commander 2009 : Failed to install network adapter -- check WINBOM”
What method did you use to integrate ERD Commander 2009?
Do you run ISO-file as it is (not extracted files only use ISO-file as it is)?
Instead of run ISO as it is - you can test integrating ERD-2009 using my script “easyboot-live.script”.
Note: you need to extract files and folders from ISO to a folder and point script to that source.
This ERD-2009 is not different from ERD-7 so you can test different ISO-files to see if you are able to get past this “winbom”-problem
However, this is an old “problem” that pops up from time to time 
As you most likely have found this ERD on Internet you do not have full control what drivers that are used in that particular build.
ERD is built using server-2003 as source and can be a “trouble-maker”.
By many reasons, server-2003 is not my first choice when creating a “Rescue-Live-build” – I use generally WinXP-sp2 as source to BartPE, Reatogo etcetera.
But I recommend this “Reasue-build” HERE
--------------------------------------------
Quote: “When uncheck Joliet check box all are working except Fedora 14 Live CD”
Yes this is the “reality” we have to face – sometimes it’s impossible to put different applications together as they interfere to each other.
Especially linux\isolinux is a problem in this matter
balder
--------------
Download complete set of scripts including help file HERE
Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
|
|
|
|
|
