Live USB stick problems.

I see that someone has already made a post like mine. I read over it and see that he or she has what I assume is the same problem as me. Which is "can't mount the root file system". I am making this topic because the other topic is marked as [SOLVED] and because I have more info to give from what I have seen. I downloaded Mageia-2-LiveCD-GNOME-Europe1-Americas-x86_64-CD.iso and Mageia-2-LiveCD-KDE4-Europe1-Americas-x86_64-CD.iso. I looked around and fount this page Dump Mageia ISOs on a USB stick?. I tried mandriva-seed but could not get it to work. I also tried Rufus, Fedora LiveUSB Creator, SARDU and UNetbootin. I get the problem "can't mount the root file system" with all of them but UNetbootin. I decided to try the Live USB stick in Oracle VM VirtualBox. I had the same problem, so I decided to post screenshots.
Fedora LiveUSB Creator GNOME screenshot

Fedora LiveUSB Creator KDE screenshot

SARDU GNOME screenshot

SARDU KDE screenshot

With Rufus I got more errors than what is shown in Oracle VM VirtualBox
Rufus GNOME screenshot

On the computer for GNOME there errors are
Rufus KDE screenshot

On the computer the errors for KDE is
I do not know why the errors for GNOME is different than the errors for KDE.
For UNetbootin, I get no errors it just sits there loading the Mageia logo. I think that problem is because of my video card and the video card drivers, but not sure for this. The just sitting there loading the distro logo happens with more than 1 distro and is because of video card drivers. The Nouveau driver is usually the problem. They need to update or fix that driver.
I hope this helps out on the problem and solution.
Fedora LiveUSB Creator GNOME screenshot

Fedora LiveUSB Creator KDE screenshot

SARDU GNOME screenshot

SARDU KDE screenshot

With Rufus I got more errors than what is shown in Oracle VM VirtualBox
Rufus GNOME screenshot

On the computer for GNOME there errors are
- Code: Select all
mount: wrong fs type, bad option, bad superblock on /dev/sdb,
missing codepage or helper program, or other error
In some cases useful info is found in syslog – try
dmesg | tail or so
losetup: failed to setup loop device: No such file or directory
mount: /dev/loop0: can't read superblock
dracut Warning: /sysroot has no proper rootfs layout, ignoring and removing offending mount hook
dracut Warning: Can't mount root filesystem
Dropping to debug shell
sh: 0: can't access tty; job control off
dracut:/# [ 6.327317] sd 3:0:0:0: [sdc] No Caching mode page present
[ 6.327364] sd 3:0:0:0: [sdc] Assuming drive cashe: write through
[ 6.332200] sd 3:0:0:0: [sdc] No Caching mode page present
[ 6.332246] sd 3:0:0:0: [sdc] Assuming drive cashe: write through
[ 6.343948] sd 3:0:0:0: [sdc] No Caching mode page present
[ 6.343995] sd 3:0:0:0: [sdc] Assuming drive cashe: write through
Rufus KDE screenshot

On the computer the errors for KDE is
- Code: Select all
mount: wrong fs type, bad option, bad superblock on /dev/sdb,
missing codepage or helper program, or other error
In some cases useful info is found in syslog – try
dmesg | tail or so
losetup: failed to setup loop device: No such file or directory
mount: /dev/loop0: can't read superblock
dracut Warning : /sysroot has no proper rootfs layout, ignoring and removing offending mount hook
dracut Warning: Can't mount root filesystem
Dropping to debug shell
sh: 0: can't access tty; job control off
dracut:/# [ 6.311170] sd 3:0:0:0: [sdc] No Caching mode page present
[ 6.311217] sd 3:0:0:0: [sdc] Assuming drive cashe: write through
[ 6.316052] sd 3:0:0:0: [sdc] No Caching mode page present
[ 6.316098] sd 3:0:0:0: [sdc] Assuming drive cashe: write through
[ 6.327675] sd 3:0:0:0: [sdc] No Caching mode page present
[ 6.327722] sd 3:0:0:0: [sdc] Assuming drive cashe: write through
I do not know why the errors for GNOME is different than the errors for KDE.
For UNetbootin, I get no errors it just sits there loading the Mageia logo. I think that problem is because of my video card and the video card drivers, but not sure for this. The just sitting there loading the distro logo happens with more than 1 distro and is because of video card drivers. The Nouveau driver is usually the problem. They need to update or fix that driver.
I hope this helps out on the problem and solution.