[SoaS] Mango Lassi USB Boot issue
Rajiv Bhushan
rajiv.bhushan at gmail.com
Thu Dec 16 16:55:05 EST 2010
The same thing occurs with SOAS Mirabelle
I am using Unetbootin release 372
I tried modifying syslinux.cfg as suggested in
https://answers.launchpad.net/soas/+question/95622
I modified
the line
append initrd=/ubninit root=live:CDLABEL=Fedora-14-i686-Live-SoaS
rootfstype=auto ro liveimg quiet rhgb rd_NO_LUKS rd_NO_MD rd_NO_DM
to
append initrd=/ubninit root=live:CDLABEL=Fedora-14-i686-Live-SoaS
rootfstype=iso966o ro liveimg quiet rhgb rd_NO_LUKS rd_NO_MD rd_NO_DM
selinux=0
Still produced the error
---------
No root device found
Boot has failed, sleeping forever
---------
Suggestions are welcome
Rajiv Bhushan wrote:
> I just use Unetbootin to write the latest Mango Lassi ISO on to a 4G USB
> stick.
>
> I booted onto a Compaq and a Toshiba laptop, and After the initial
> splash screens, the boot process stops, and I get the following message
>
> (Note '----------' indicates begining and end of message or file)
> ---------
> No root device found
> Boot has failed, sleeping forever
> ---------
>
> On examining the files on the USB stick
>
> in the /efi/boot folder, boot.conf is as below
>
> --------------
> default=0
> splashimage=/EFI/boot/splash.xpm.gz
> timeout 10
> hiddenmenu
>
> title Fedora-14-i686-Live-SoaS
> kernel /EFI/boot/vmlinuz0 root=live:LABEL=Fedora-14-i686-Live-SoaS
> rootfstype=auto ro liveimg quiet rhgb
> initrd /EFI/boot/initrd0.img
> title Verify and Boot Fedora-14-i686-Live-SoaS
> kernel /EFI/boot/vmlinuz0 root=live:LABEL=Fedora-14-i686-Live-SoaS
> rootfstype=auto ro liveimg quiet rhgb check
> initrd /EFI/boot/initrd0.img
> ------------------
>
> The root folder / the file syslinux.cfg is as follows
>
> ----------------
> default vesamenu.c32
> prompt 0
> menu title UNetbootin
> timeout 100
>
> label unetbootindefault
> menu label Default
> kernel /ubnkern
> append initrd=/ubninit root=live:CDLABEL=Fedora-14-i686-Live-SoaS
> rootfstype=auto ro liveimg quiet rhgb rd_NO_LUKS rd_NO_MD rd_NO_DM
>
> label ubnentry0
> menu label Fedora-14-i686-Live-SoaS
> kernel /EFI/boot/vmlinuz0
> append initrd=/EFI/boot/initrd0.img
> root=live:LABEL=Fedora-14-i686-Live-SoaS rootfstype=auto ro liveimg
> quiet rhgb
>
> label ubnentry1
> menu label Verify and Boot Fedora-14-i686-Live-SoaS
> kernel /EFI/boot/vmlinuz0
> append initrd=/EFI/boot/initrd0.img
> root=live:LABEL=Fedora-14-i686-Live-SoaS rootfstype=auto ro liveimg
> quiet rhgb check
>
> label ubnentry2
> menu label Boot
> kernel /EFI/boot/vmlinuz0
> append initrd=/EFI/boot/initrd0.img
> root=live:CDLABEL=Fedora-14-i686-Live-SoaS rootfstype=auto ro liveimg
> quiet rhgb rd_NO_LUKS rd_NO_MD rd_NO_DM
>
> label ubnentry3
> menu label Boot (Basic Video)
> kernel /EFI/boot/vmlinuz0
> append initrd=/EFI/boot/initrd0.img
> root=live:CDLABEL=Fedora-14-i686-Live-SoaS rootfstype=auto ro liveimg
> quiet rhgb rd_NO_LUKS rd_NO_MD rd_NO_DM xdriver=vesa nomodeset
>
> label ubnentry4
> menu label Verify and Boot
> kernel /EFI/boot/vmlinuz0
> append initrd=/EFI/boot/initrd0.img
> root=live:CDLABEL=Fedora-14-i686-Live-SoaS rootfstype=auto ro liveimg
> quiet rhgb check
>
> label ubnentry5
> menu label Memory Test
> kernel /EFI/boot/memtest
> append initrd=/ubninit
>
> label ubnentry6
> menu label Boot from local drive
> kernel /ubnkern
> append initrd=/ubninit
> --------------------------
>
> The ubnfilel.txt has
>
> --------------------
> EFI/boot/boot.conf
> EFI/boot/boot.efi
> EFI/boot/bootia32.conf
> EFI/boot/bootia32.efi
> EFI/boot/grub.conf
> EFI/boot/initrd0.img
> EFI/boot/isolinux.bin
> EFI/boot/isolinux.cfg
> EFI/boot/memtest
> EFI/boot/splash.jpg
> EFI/boot/splash.xpm.gz
> EFI/boot/vesamenu.c32
> EFI/boot/vmlinuz0
> LiveOS/osmin.img
> LiveOS/squashfs.img
> isolinux/boot.cat
> isolinux/initrd0.img
> isolinux/isolinux.bin
> isolinux/isolinux.cfg
> isolinux/memtest
> isolinux/splash.jpg
> isolinux/vesamenu.c32
> isolinux/vmlinuz0
> ------------------------
>
>
> The ubnpathl.txt has
>
> ---------------
> isolinux
> LiveOS
> EFI/boot
> EFI
> -----------------
>
> These are the only files that appear to be editable.
>
> Any ideas as to how to get sugar to boot?
More information about the SoaS
mailing list