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.
Used Install SliTaz for USB but get Error 21: Selected disk does not exist
(25 posts) (7 voices)- Started 12 years ago by cforput
- Latest reply from domcox
- This topic is not resolved
-
Anonymous
offlineUnregisteredPosted 12 years ago # -
Trixar_za
offlineKey MasterSounds interesting so I'll have a look at it. Anything to simplify the install would be awesome.
Posted 12 years ago # -
christophe
offlineMemberI 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...
Posted 12 years ago # -
domcox
offlineAdministratorBy saying using blkid, I guess you mean UUIDs (blkid is a tool to list devices attributes)
it works properly with SliTaz:
$ blkid /dev/hda1: LABEL="Cooking" UUID="9deaac17-eddd-4f25-ab23-15c5a73c418a" TYPE="ext4" # mount -t ext4 UUID=9deaac17-eddd-4f25-ab23-15c5a73c418a /mntPosted 12 years ago # -
christophe
offlineMemberyou 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...
Posted 12 years ago # -
Aleksej
offlineCoder-hobbyistI 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:
# 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 LinuxSo, 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):
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 LinuxSliTaz home is /dev/sdb2 or:
$ blkid /dev/sdb2 /dev/sdb2: LABEL="SliTaz" UUID="e7a605fb-cbb6-49ff-a5ac-8bfd89e5b4ed" SEC_TYPE="ext2" TYPE="ext3"Files that I need to boot (/media/ACER here is mount point for /dev/sda2 partition, that is windows Disk 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.gzWhat 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:
[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"And finally, you have all info to understand my Menu.lst:
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 haltI 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/grldrPosted 12 years ago # -
Anonymous
offlineUnregisteredSo 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.gzDon'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
}Posted 12 years ago # -
Anonymous
offlineUnregisteredJust 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.)Posted 12 years ago # -
christophe
offlineMemberI 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.
Posted 12 years ago # -
domcox
offlineAdministrator- 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.Posted 12 years ago #
Reply
You must log in to post.
