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?
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?
hi cforput,
error 21 appear when reboot or in SliTaz Installer ?
Have you possibility to join webchat.freenode.net #slitaz for discuss instantly ?
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 ;) )
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!
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
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)?
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
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........
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.
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.
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)
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"
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. :)
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.
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.
You must log in to post.