SliTaz Forum

Problem Installing SliTaz Rolling version

(17 posts) (8 voices)

• Started 11 years ago by jared19
• Latest reply from Paul
• This topic is not a support question

Tags:

No tags yet.

1. 

   jared19
   

   offline

   Member

   Hi,

   I got SliTaz 4.0 already installed on my VirtualBox. Now I want to install the rolling version on top of it (replace the 4.0). When trying to install it, I encounter the following problems:

   1. GPartEd is spending a whole lot of time detecting the (virtual) HDD. I eventually close it after 5 min, and use the previous partition setup instead (2 partition, 1 root and another if home)

   2. When selecting the source media, there's no explicit selection of the LiveCD. There's a selection for an ISO file, but IDK what to fill cos the select box beside it only listed "<none>". So I choose from web instead, selecting the rolling version.

   3. When I selected install boot loader, the installer whines "Error: No disk selected, can't install boot loader". Where's the disk selector??? So I go ahead unselecting it.

   4. After install, I selected to reboot instead of exiting the installer. The virtual machine crashes when deleting "something.conf"

   5. I remove the LiveCD and reboot, Grub says "Error 15" and hangs there.

   Where did I go wrong?

   Posted 11 years ago #
2. 

   domcox
   

   offline

   Administrator

   Hello jared19!

   What's the output of :
   # parted -l

   on your virtual system?

   Posted 11 years ago #
3. 

   claimshell
   

   offline

   Member

   Haha, I have the same problem, but because he never responded I'm kinda afraid to try what you suggested. Well, here goes nothing!

   Attachments

   1. parted.png (78.3 KB, 1,197 downloads) 10 years old

   Posted 10 years ago #
4. 

   domcox
   

   offline

   Administrator

   Hmm, I'll install virtualbox and others (I already have vmware player) on my SliTaz USB key, and see what is wrong, I suspect missing scsi drivers, like a BusLogic SCSI driver.

   Posted 10 years ago #
5. 

   claimshell
   

   offline

   Member

   I essentially had the same setup for my dual boot before (which worked fine). NTFS was for Win7, while ext3 was for SliTaz 4.0 stable. Then I made USB for 4.0 rolling and formatted the ext3 one, but never got to install it on HDD. I was thinking it has to do with the bootlader I had before. It was grub, but no idea where it was installed and trying

   #mkdir /mnt/sda1
   #mount /dev/sda1 /mnt/sda1

   didn't get me the menu.lst some people are looking for. There's no grub folder.

   Posted 10 years ago #
6. 

   claimshell
   

   offline

   Member

   Ok, now it's even weirder. Decided that I don't really know how to deal with this partition crap and tried to clean it all up. Got my SliTaz 4.0 rolling Live USB running, so deleted every partition on HDD and formatted it all. That can't go wrong. Even with just one partition, SliTaz installer says that I can't install bootloader, so I deselect it again (as well as Windows Dual Boot option). But now, I get Error 22 on boot, the same place where I used to get Error 15.

   I'm really surprised because the first time I got both versions of SliTaz (live and on HDD) working with first try. That can only mean I have really messed up. I will try and work my way up from understanding thing you said about SCSI drivers and partitioning in general...

   

   Attachments

   1. nutmeg.png (21.7 KB, 1,327 downloads) 10 years old

   Posted 10 years ago #
7. 

   Ceel
   

   offline

   Administrator

   Hmm, Error 15 and Error 22 are message from GRUB. So GRUB is already installed on a disk -/dev/sdb1 I suppose because of the boot flag- and search the kernel at a wrong place. You should have a /boot/grub directory somewhere.

   Posted 10 years ago #
8. 

   mojo
   

   offline

   Key Master

   @domcox
   tazinst version
   3.90
   Can't list partitions when running a livecd on optical drive (/dev/hdb).
   * bootloader:
   auto grub syslinux

   Warning: Unable to open /dev/hdb read-write (Read-only file system).
   /dev/hdb has been opened read-only.
   Error: Invalid partition table - recursive partition on /dev/hdb.
   Ctrl+D <= My keyboard input
   * partition_table
   /dev/hda: msdos
   /dev/hdb: unknown
   /dev/hdc: msdos
   Warning: Unable to open /dev/hdb read-write (Read-only file system).
   /dev/hdb has been opened read-only.
   Error: Invalid partition table - recursive partition on /dev/hdb.
   Ctrl+D <= My keyboard input
   * winboot:
   auto

   I verified the live cd was not mounted.
   parted -lm outputs the same error which is in functions list_partition_table list_winboot list_bootloader p_table

   If I eject the cd from the drive tazinst list completes without errors.

   Posted 10 years ago #
9. 

   claimshell
   

   offline

   Member

   Ok, progress, I guess.
   Found two /boot folders (one in Live USB, one in mounted HDD). Only one of them had /grub folder, none had menu.lst

   

   So I tried installing new Grub on the HDD from the handbook instructions. Edited device.map file by deleting /dev/fd0 line (havent seen it anywhere, so thought it doesn't belong). menu.lst file was empty however, so need to write stuff there myself. Got this example from manual

   title SliTaz GNU/Linux 3.0 (Kernel 2.6.34-slitaz)
   root(hd0,0)
   kernel /boot/vmlinuz-2.6.34-slitaz root=/dev/hda1 vga=normal

   Trying to look up all the info I need, don't want to reboot and get stuck again.

   *edit

   Don't really know how to edit the menu.lst file. Replaced title and kernel number. Guessed the second line. Have the kernel file in place and changed the root directory at the end of third line. I have no idea if this will work. See you in couple of minutes then.

   title SliTaz GNU/Linux cooking (Kernel 3.2-slitaz)
   root(sd0,0)
   kernel /boot/vmlinuz-2.6.34-slitaz root=/dev/sda1 vga=normal

   Attachments

   1. grubber.png (10.4 KB, 1,245 downloads) 10 years old

   Posted 10 years ago #
10. 

    claimshell
    

    offline

    Member

    Guys, you won't believe me. Because installing SliTaz was my first ever experience with Linux on my first ever laptop, this feels like a goddamn adventure. I've just returned from lands I never expected to return from.

    After initial reboot, tried to boot the HDD, got the bootloader screen with SliTaz selection on it. After pressing Enter, there was an error, of course. Third line from menu.lst was printed and it said that file was missing. Reboot, started USB again. But this time something went wrong and I could only start SliTaz as command line (don't know how it's called). Which was a first one for me. Managed to mount /sda1 and find the boot folder. Turns out I have mixed up kernel number. Opened menu.lst with Nano (never done that before, was lucky to know the name of app) and fixed kernel number. Rebooted and that shit worked! SliTaz launched.

    Was weird to see it being SliTaz 4.0 stable though. Is there any chance of getting the stable version while using cooking.iso? Or I just messed up my files and installed stable version? I will look to fix LiveUSB now, so i can try to reinstall HDD version.

    Thanks for help so far, I massively appreciate this. Loving every step forward.

    Posted 10 years ago #
11. 

    mojo
    

    offline

    Key Master

    The output of uname -a command in terminal identifies version.
    Slitaz-4.0 release: 2.6.37
    Cooking: 3.2-slitaz when it should output 3.2.53-slitaz because the modules path is wrong.

    Posted 10 years ago #
12. 

    claimshell
    

    offline

    Member

    Thank you, mojo! Your numbers were correct. I now have rolling version on my HDD.

    Posted 10 years ago #
13. 

    Paul
    

    offline

    Key Master

    @mojo

    The output of uname -a command in terminal identifies version.
    Cooking: 3.2-slitaz when it should output 3.2.53-slitaz because the modules path is wrong.

    Any idea where uname reads this from?

    Is it a file or the kernel

    Thx

    Posted 10 years ago #
14. 

    kultex
    

    offline

    Key Master

    it reads from /lib/modules

    but why it takes 3.2-slitaz and not the linked 3.2.50-slitaz I have no idea

    the problem is, that you can not rename the folder to experiment a bit

    Attachments

    1. uname1.jpg (60.7 KB, 1,280 downloads) 10 years old

    Posted 10 years ago #
15. 

    Darjeeling
    

    offline

    Member

    Kulti, how did you get SpaceFM to show your internal (and external?) drives and how did you mount them? Did you do it manually from a root terminal or does SpaceFM actually allow mounting drives on your machine? I'm asking because none of this works here with the latest Rolling booted from a CD and running entirely in RAM, although I've only got one lousy 1 GB PATA drive which is connected with an old-fashioned twisted cable as slave to the channel that controls the CD drive.

    Posted 10 years ago #

RSS feed for this topic

Reply »

You must log in to post.