SliTaz Forum
You are not logged in.
As the title says, I used the Install SliTaz utility and everything appeared to work OK but when Grub came up and I press enter I get the Error 21: Selected disk does not exist.
Any suggestions?
Offline
I seem to have the same error once, check how your hard drives are appointed.
In fact my usb install was seen as sda and hda as my hdd.
It is possible that seeks Grub view sda.
(i'm french, my english is not very good 
)
Offline
The error 21 appears when I reboot. So I reboot and grub come up with a single entry that says: SliTaz GNU/Linux (cooking) (Kernel vmlinuz-2.6.37-slitaz)
If I press enter or wait the 7 seconds then the following error shows up. I typed it below exactly how it shows on my laptop.
root (hd2,0)
Error 21: Selected disk does not exist
Press any key to continue...
I also don't know how to join webchat with freenode - sorry!
Offline
open a new onglet in firefox or your brother and address bar type webchat.freenode.net
type a pseudo; channel type #slitaz and recopy capchta.
Try this:
replace hd2,0 on hd0,0.
If you have only hard disk
Grub design disk :
first disk hd0
second disk hd1
Offline
I reran the install and got the same exact same thing. This time I edited grub and changed the hd2,0 to hd1,0 because that is what the installer said was the USB drive. I rebooted and now I'm getting the following error
Booting commend-list
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/sdc1 quiet
Error 15: File not found
Press any key to continue....
Anyone have any other directions on how to install to a USB (not make a liveUSB)?
Offline
Never depends with usb drive.
boot your usb live and type fdisk -l in console
i imaginate you use this partition schema (adapt for result return fdisk -l):
/dev/sda1: swap
/dev/sda2: /
or if your disk is IDE:
/dev/hda1: swap
/dev/hda2: /
Editing menu.lst and modify this part:
root (hd0,1)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/sda2 quiet
or if your disk is IDE:
root (hd0,1)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/hda2 quiet
Explain:
root (hdx,y) define where situated partition / or the separate /boot
hdx can be :
hd0 for first disk (not include usb device)
hd1 for second disk (always not include usb device)
y define partition (count at 0)
/dev/sda1 is define for 0 (full designation was (hd0,0) )
/dev/sda2 is define for 1 (full designation was (hd0,1) )
/dev/sdb1 is define for 0 but hdx incremente of 1 (full designation was (hd1,0) )
In your case i seem was (hd0,0) or (hd0,1) depend fdisk -l result
Offline
Well I've tried a few things and still am way beyond frustrated. Why mystifies me is that if you search on the internet, people are having problems all over the place with just installing SliTaz onto USB drives. Why wouldn't this be a top priority so it works? I've tried 4 different means to install to a USB and all have failed. I've tired the Install panel, tazusb.exe, unethbootin-windows-581 (aftermarket) and Universal-USB-Installer-1.9.1.6.exe and all I got was hours of my life taken away from me with nothing to show for it. If you want to grow in popularity the first and highest priority you have is to get your software onto people's computers. Without that, nothing else matters. How can people be so short sighted. Ubuntu and Mint are so popular. You know why? Because they both work!
I tired hd1,0 (error 15) hd2,0 (error 21) and hd0,0 (Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,33) Pid: 1, comm: swapper Not tainted 2.6.37-slitaz #2 They all give me different errors and none of them boot up.
What a shame and disappointment........
Offline
Feel free to do better or pay one of the developers to create a better version for you.
We are not Ubuntu. We are not backed by a company that sells training for it to other companies. We are not forked off a distribution that nearly existed for 20 years with over half a million developers and helpers to fix problems, nor based on Ubuntu like Mint.
SliTaz was made from scratch using the Linux Kernel. We have a handful of developers who have full time jobs. We do not have the luxury of solutions created by a random developer 10 years ago. We are still learning, especially with the rate things are changing.
What does that mean? Your comparison is both unfair and inaccurate. The LiveUSB problem is the least of our worries and can be EASILY fixed by searching this forum. Use the SliTaz Core iso with Unetbootin. Problem solved.
Now either fix your problems yourself or pay us to fix it for you. Otherwise kindly shut up and be patient like everybody else.
Offline
Well, first of all, I tried Unetbootin on 2 different USBs and it didn't work so problem NOT solved. Patient? I wonder just how far down your list it is to fix something so people can actually use your software. Hum? Doesn't sound like a very solid business model. I guess I'll go paint my pastry shop a nice new color and worry about making pastries later. I think people are much more interested in seeing new paint than they are eating my croissants.
Shut Up? No, just off to a different distro that works. Too bad because SliTaz did have the nicest looking distro but I need one that works not one that looks nice. Happy painting.
Offline
Hd0,0 where you got the kernel panic is almost the right grub command line
add rootdelay=9 to your kernel line in grub and it will work (that adds the necessary time for mounting the usb and finding the file, which in turn will avoid the kernel panic).
Some day we'll decide to add this as a default; it is REQUIRED when booting from an USB disk.
This is a recurrent problem that has been addressed several time in this forum
Let us know if that worked
By the way i agree with you that it is extremely frustrating and should be fixed as a default (but this is a grub issue, not a Slitaz issue)
Offline
Hi cforput,
First, replying to my post a week later.
All this to insult the SliTaz community that's trying always to best assist its users.
As pointed Trixar_za, we are not Ubuntu, each of us a job (or in my case student), and not necessarily the time to help everyone.
Finally this slight bug is not inherent in SliTaz.
this "bug" can not really be fix into the menu.lst because it would have an impact on boot time but a warning in the case of installation on a usb stick would be useful:
"If you install SliTaz on a USB key, do not forget to add rootdelay=10 to the kernel line in your menu.lst, otherwise you will get a kernel panic"
Offline
cfnorput: Nobody forced you to use SliTaz in the first place, so yeah go darken the forums of another distro and get flamed out me existence. 
Offline
We should fix it in the menu.lst at install time, adding some rootdelay as a default or asking the user if he is installing on a USB device or internal disk before installing grub.
Fine tuning grub will always be eaier for an experienced user, than it will be for newbies to install this properly at the first time. And the cost in terms of frustration on all sides is just too high.
To believe that newbies should have read the documentation before installing, is just to high of an expectation. Not even professionnals do that.
Offline
Yes, but professionals have learned how to google off their phones and how to infer solutions. Even a newbie has that ability. But yeah, grub4dos sucks ass. Fixing it would require an upgrade to grub2, a rewrite of the installer and possible a switch to the sd device naming convention. Anybody willing to do that?
Still, it's no excuse to be an unreasonable dick about it. Personally I like the fact that SliTaz teaches me so much. Only an idiot would expect Ubuntu in 35Mb.
Offline
Hello all who may be viewing, I'm new to this distro, but may I suggest the use of blkid for installations, as this overcomes the changing drive designations when installing to usb devices.
Sounds interesting so I'll have a look at it. Anything to simplify the install would be awesome.
Offline
I am using Grub2, and find it even worse to fix; each time i need a change i have to do a websearch to check the documentation. While grub1 is straightforward. I must be missing something, but I see no reason why anyone would want to move to grub2. The only reason i do is because it is the default with my main linux partition.
For using blkid it sounds like a good idea but i never could get it work properly with slitaz (ie wihtout reeverence to the device address). I think it would require some code change to make it work. Do to the way slitaz is loaded. If we are there, then shouldn't we just also set up some automatic delay for the loader to wait until the right device is mounted instead of defaulting to kernel panic...
Offline
By saying using blkid, I guess you mean UUIDs (blkid is a tool to list devices attributes)
it works properly with SliTaz:
[c]$ blkid
/dev/hda1: LABEL="Cooking" UUID="9deaac17-eddd-4f25-ab23-15c5a73c418a" TYPE="ext4"
# mount -t ext4 UUID=9deaac17-eddd-4f25-ab23-15c5a73c418a /mnt[/c]
Offline
you are right this is what i meant
I was also meaning that "just" replacing the device by the uuid in the grub1 spell does not boot (or at least, the few tests i did have not been successful, but i do not pretend to be an expert either)
I'd be happy to hear from anyone using uuid instead of devices with grub and slitaz (in which case i want the tested, working spell, not a reference to the documentation).
thanks for correcting me and apologies for the confusion...
Offline
I can't tell about Grub1 because I don't use it. So, I want to tell about Grub4dos that I use for my needs and that works wery well on my netbook with preinstalled windows xp. I use UUID with success:
My HDD was two partitions, I break second one to have room to install Linux:
[c]# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 637 5116671 12 Compaq diagnostics
/dev/sda2 * 638 18021 139636980 7 HPFS/NTFS
/dev/sda3 18022 19457 11534639+ f Win95 Ext'd (LBA)
/dev/sda5 18022 18151 1044193+ 82 Linux swap
/dev/sda6 18152 19457 10490413+ 83 Linux[/c]
So, window's Disk C: really is /dev/sda2 in the Linux notation, or (hd0,1) in Grub4dos notation.
I used /dev/sda6 for big Linux—Mint. It was used Grub2, but I rewrote it's config manually to have ability to boot it with my Grub4dos instead of Grub2.
Additionally I want to say that I have frugal installation of SliTaz (and some other small linuxes), and I use my USB-Flash for my SliTaz Linux /home partition (end of fdisk -l listing):
[c]Disk /dev/sdb: 4043 MB, 4043308544 bytes
125 heads, 62 sectors/track, 1018 cylinders
Units = cylinders of 7750 * 512 = 3968000 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 749 2898944 83 Linux
/dev/sdb2 * 749 1019 1047552 83 Linux[/c]
SliTaz home is /dev/sdb2 or:
[c]$ blkid /dev/sdb2
/dev/sdb2: LABEL="SliTaz" UUID="e7a605fb-cbb6-49ff-a5ac-8bfd89e5b4ed" SEC_TYPE="ext2" TYPE="ext3"[/c]
Files that I need to boot (/media/ACER here is mount point for /dev/sda2 partition, that is windows Disk C:):
[c]-rwxrwxrwx 1 root root 251152 Jun 9 2008 /media/ACER/ntldr
-rwxrwxrwx 1 root root 216 Jan 13 2012 /media/ACER/boot.ini
-rwxrwxrwx 1 root root 220005 Jun 11 2009 /media/ACER/grldr
-rwxrwxrwx 1 root root 3612 Nov 16 03:56 /media/ACER/Menu.lst
-rwxrwxrwx 1 root root 2492912 Mar 7 2012 /media/ACER/boot/slitaz4/bzImage
-rwxrwxrwx 1 root root 184523558 Sep 17 01:45 /media/ACER/boot/slitaz4/rootfs.gz[/c]
What is a strange process of booting!, you can say. Just I wanted to save my guarantee and not touch windows boot. It was so far… So here:
[*]bios boot /dev/sda2/ntldr — window's boot loader;
[*]ntldr use boot.ini to show window's boot menu; by default is menu entry with Grub4dos start;
[*]Grub4dos show me graphical menu—my entrance to Linux world;
[*]I select one of my linuxes or just wait to boot SliTaz.
My boot.ini that use ntldr to boot:
[c][boot loader]
timeout=5
default=c:\grldr
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home Edition RU" /noexecute=optin /fastdetect /TUTag=S6BN1T
c:\grldr="Start Linux"[/c]
And finally, you have all info to understand my Menu.lst:
[c]timeout=2
default 1
# graphic menu:
#gfxmenu (hd0,1)/boot/gfx/boshki.gz
#gfxmenu (hd0,1)/boot/gfx/ded-lego.gz
gfxmenu (hd0,1)/boot/gfx/message.distro-noball
#gfxmenu (hd0,1)/boot/gfx/message.mepis
#gfxmenu (hd0,1)/boot/gfx/message.pup1
title LinuxMint 11
rootnoverify (hd0,5)
kernel (hd0,5)/boot/vmlinuz-2.6.35-22-generic root=/dev/sda6 ro gfxpayload=800x600x24,800x600 quiet splash pcie_aspm=force elevator=deadline
initrd (hd0,5)/boot/initrd.img-2.6.35-22-generic
title SliTaz 4.0
rootnoverify (hd0,1)
kernel (hd0,1)/boot/slitaz4/bzImage rw root=/dev/null lang=ru_RU kmap=ru autologin home=UUID=e7a605fb-cbb6-49ff-a5ac-8bfd89e5b4ed
initrd (hd0,1)/boot/slitaz4/rootfs.gz
title SliTaz Rolling
rootnoverify (hd0,1)
kernel (hd0,1)/boot/rolling/bzImage rw root=/dev/null lang=ru_RU kmap=ru vga=789 home=UUID=60d18674-525e-4cf6-a784-498ec93f96db
initrd (hd0,1)/boot/rolling/rootfs.gz
title SliTaz 4.0 My
rootnoverify (hd0,1)
kernel (hd0,1)/boot/slitaz4my/vmlinuz rw root=/dev/null vga=789 lang=ru_RU kmap=ru autologin home=UUID=e7a605fb-cbb6-49ff-a5ac-8bfd89e5b4ed
initrd (hd0,1)/boot/slitaz4my/rootfs.gz
title SliTaz 4.0 CrossOver
rootnoverify (hd0,1)
kernel (hd0,1)/boot/SliTaz-CrossOver/vmlinuz rw root=/dev/null vga=789 lang=ru_RU kmap=ru autologin home=UUID=e7a605fb-cbb6-49ff-a5ac-8bfd89e5b4ed
initrd (hd0,1)/boot/SliTaz-CrossOver/rootfs.gz
title Puppyrus-Richy-end [menu]
configfile (hd0,1)/boot/prRe/menu.lst
title SliTaz 3.0
rootnoverify (hd0,1)
kernel (hd0,1)/boot/bzImage rw root=/dev/null home=/dev/sda2 vga=789 lang=ru_RU kmap=ru laptop
initrd (hd0,1)/boot/Rootfs.gz
#title HAIKU Release 1 alpha 3
#map (hd0,1)/haiku.iso (0xFF)
#map --hook
#root (0xFF)
#chainloader (0xFF)
#title Kolibri 0.7.5
#kernel (hd0,1)/boot/kolibri/memdisk
#initrd (hd0,1)/boot/kolibri/kolibri.img
title SliTaz 3.0 <— previous
rootnoverify (hd0,1)
kernel (hd0,1)/boot/bzImage rw root=/dev/null home=/dev/sda2 vga=789 lang=ru_RU kmap=ru laptop
initrd (hd0,1)/boot/previous.gz
###
title SliTaz 4.0 Core Clean
rootnoverify (hd0,1)
kernel (hd0,1)/boot/slitaz4o/bzImage rw root=/dev/null vga=789 lang=ru_RU kmap=ru autologin
initrd (hd0,1)/boot/slitaz4o/rootfs.gz
###
title SliTaz 4.0 Core Up + Governors
rootnoverify (hd0,1)
kernel (hd0,1)/boot/slitaz4o/bzImage rw root=/dev/null vga=789 lang=ru_RU kmap=ru autologin
initrd (hd0,1)/boot/slitaz4o/rootfs2.gz
###
title SliTaz 4.0 RazorQt
rootnoverify (hd0,1)
kernel (hd0,1)/boot/razorqt/bzImage rw root=/dev/null vga=789 lang=ru_RU kmap=ru autologin
initrd (hd0,1)/boot/razorqt/rootfs.gz
###
title commandline
savedefault --wait=2
commandline
title Reboot
reboot
title ShutDown PC
halt[/c]
I can't tell that I profi because I use rootnoverify instead of root in every menu entry, and use (hd0,1) as a prefix fo file path in every line. But it just works, and I don't need to fix that is not broken
Sorry for big amount of letters. I hope it help to someone.
By the way, you can find grldr (from Grub4dos) here on SliTaz mirror: http://mirror.slitaz.org/boot/grldr
Offline
So theoretically,
DEVID=$(/sbin/blkid | sed 'p;s/"//g' | fgrep "$DEVICE" | sed 's/:.*//;q')
(taken from /etc/init.d/bootopts.sh posted by Aleksej)
should find the UUID to enter into grub, such as or similar to,
title SliTaz 4.0 My
rootnoverify (hd0,1)
kernel (hd0,1)/boot/slitaz4my/vmlinuz rw root=/dev/null vga=789 lang=ru_RU kmap=ru autologin home=UUID=e7a605fb-cbb6-49ff-a5ac-8bfd89e5b4ed
initrd (hd0,1)/boot/slitaz4my/rootfs.gz
Don't know if it would actually work though.
This is how my grub2 grub.cfg uses it :-
menuentry 'Debian GNU/Linux, with Linux 3.2.0-2-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod gzio
insmod part_gpt
insmod ext2
set root='(hd0,gpt1)'
search --no-floppy --fs-uuid --set=root b93500b2-1489-4a82-ae24-da81e55e1170
echo 'Loading Linux 3.2.0-2-amd64 ...'
linux /boot/vmlinuz-3.2.0-2-amd64 root=UUID=b93500b2-1489-4a82-ae24-da81e55e1170 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-2-amd64
}
Just spent all morning trying to install to a usb hdd, eventually successful.
Here, briefly, is what happened.
Created a tazinst.conf & ran tazinst install tazinst.conf.
Went to boot into new installation,
Error 21: Selected disk does not exist.
grub.lst had my disk as (hd2,0) & root=/dev/sdc1
I installed from a pendrive to a usb hdd, whilst also having an internal hdd.
Kept getting file system does not exist, no matter what I tried.
Only after manually re writing menu.lst would it boot; had to add rootdelay option.
Retried booting, having entered my UUID in place of /dev/sdb1, & it 'does not boot'.
Therefore, I conclude, grub4dos does not support the use of UUID.
(Or, at least, not over usb.)
(Sorry for having given you false hope.)
I should have mentionned that I have been using grub4dos, grub1, and grub2
and always did hit that same problems that make grub2 a nightmare, and the use a UUID has not been a solution.
Using grub4dos or grub1 and manually adjusting the options has been the way to go, UNLESS, it works right out of the box after installation.
Offline
[*]grub1 (Grub Legacy) is no longer developped, and does not support the GPT partitioning scheme
[*]grub2 support GPT drives but needs an extra partition, is bloated and complicated.
So why not try syslinux?
syslinux have a few limitations: only ext2, ext3, ext4, brtfs filesystems are supported. It can't boot kernels on other partitions, however you can easily chainload another linux installations.
syslinux is simpler than both grub1 and grub2, disks with GPT or MSDOS partition scheme are supported.
Moreover, syslinux looks at the device from which it is booted *at boot time* and use that to find the kernel.
Offline
[ Generated in 0.016 seconds, 7 queries executed - Memory usage: 1.61 MiB (Peak: 1.77 MiB) ]