SliTaz Forum
You are not logged in.
Hello all. I have a problem in using Slitaz. When I use Slitaz live CD to boot a windows OS, it doesn't show NTFS partitions. The output of df is as :-
tux@slitaz:~$ df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 451.6M 172.4M 279.2M 38% /
tmpfs 250.9M 0 250.9M 0% /dev/shm
/dev/hdc 424.6M 424.6M 0 100% /media/hdc
My host OS is Linux mint (nadia). I am using windows XP OS in VM Ware. Trying to read the XP filesystem using Slitaz live CD-ISO.
Whereas when i insert a Pen drive in NTFS, Slitaz mounts it. Any one any ideas?
Offline
Have you tried to mount the ntfs using Mountbox app?
Offline
Silly question, but did you try to see it in pcmanfm ? and mount it from there
I cant remember for sure but i think the on-disk ntfs partition will not be mounted automatically....
Offline
@ kriss332
What version of SliTaz do you use?
With 4.0, no problem for me: PCManfm sees my hard disks (NTFS)
With rolling, SpaceFM doesn't see my hard disks till I didn't mount them manually.
Offline
If the slitaz live cd iso is running in a cd device in the same VM as the vmdk formated ntfs with winxp installed.Slitaz should be able to mount the partition and read the winxp files. Cooking requires a terminal mount,pcmanfm in 4.0 does it with a click in a VM in virtualbox with a vmk formated ntfs.
I think the problem is with VM WARE and has nothing to do with slitaz.
Offline
Sorry for late posting. It is time zone gap. I am using Slitaz 4. PCmanfm didn't see the NTFS filesystem of windows. But as I connect my pen drive it automatically picks it up. I tried to mount dev/sda, dev/sda1 .....etc from terminal. but of no use. The same thing happened with Win-7 also in VM Ware. I am using VM Ware-9. Mojo, I guess issue is with VM Ware. I am going to boot my original hard disk (which is dual boot in Win-7 & Linux mint) with Slitaz live image.
But hey...for info- BackTrack is able to read the same VM Ware's Win-XP NTFS partitions.
Anyways I am going to try to boot my entire hard disk and check it...
Offline
Guys...no luck. I tried to Live boot my entire hard disk with Slitaz live image using a bootable pen drive (bootable made using Unetbootin). I have dual boot with Win-07 and Linux mint.
It gives error:-
SATA Link down
VFS: cannot open root device ......
Please append a correct "root= " boot option. Hre are available options
Kernel panic - not syncing : VFS: Unable to mount root fs on unknown block (0,66)
Pid:1, Comm: Swapper tainted
etc...
I am not able to figure out what may be wrong. Do I have a corrupted ISO?
Offline
when booting from a pen drive you need to add [c]rootdelay=5[/c]to the grub command line for it to work.
This should solve the kernel panic message.
Some hint if the sata link down is still there afterwards:
I think i have already seen some strange message with Sata if your system supports uefi, are you bios based or uefi based ?
Offline
Christophe, my Motherboard is MSI- P55a GD65 and BIOS based.
I added 'rootdelay=5' in grub loader (while booting it gave boot loader, I pressed 'e' and then appended it at bottom. I guess i followed correctly)
Adding it doesn't make any difference.
Offline
I booted live my HP-Mini-notebook as well, bit it showed the same error. What i feel from error is that Image is not able to find correct partition. Here is the detailed message-
VFS: Cannot open root device "(null)" or unknown-block(0,66)
Please append a correct "root=" boot option; here are the available partitions:
0800 156290904 sda driver: sd
0801 102400 sda1 00000000-0000-0000-0000-000000000sda1
0802 67096576 sda2 00000000-0000-0000-0000-000000000sda2
0803 71678976 sda3 00000000-0000-0000-0000-000000000sda3
0804 1 sda4 00000000-0000-0000-0000-000000000sda4
0805 17409024 sda5 00000000-0000-0000-0000-000000000sda5
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,66)
Pid: 1, comm:swapper not tainted 2.6.37-slitaz #2
Call Trace:
further down below it gives some more traces, it is very hectic to type all of that.
Offline
please tell us what is the grub command line. This is where the error lies. (and your feeling about the root of the error is correct)
Offline
I write about the grub on my mini laptop. It is dual boot with Win-7 and backtrack.
grub> root (hd0, {on tab completion, it shows following partitions}
Possible partitions are:
Partition num: 0, filesystem type unknown, partition type 0x7
Partition num: 1, filesystem type unknown, partition type 0x7
Partition num: 2, filesystem type unknown, partition type 0x7
Partition num: 4, filesystem type is ext2fs, partition type 0x83
grub> kernel /boot/vmlinuz- {on hitting tab, it gives error}
Error 12: Invalid device requested
I am not very good in linux as of now, so plz be a bit detailed in questions, so that I could execute proper things. Thanks
Offline
what we need is the content of the command line which appears from the boot menu,
when you enter the edit menu though "e" on the main boot menu
Offline
Hello kriss332
I'm not sure to understand clearly your configuration; you said
I tried to Live boot my entire hard disk with Slitaz live image using a bootable pen drive (bootable made using Unetbootin). I have dual boot with Win-07 and Linux mint.
How do you boot exactly? Grub from your internal hard disk?
Where is SliTaz installed? On an USB pendrive? Live, frugal... ?
By the way, LiveUSB made with Unetbootin (at least under windows) don't work with SliTaz 4.0
Offline
Hi kriss332,
for create a slitaz live USB, you can use dd command:
dd if=/path/to/slitaz-4.0.iso of=/dev/sdx (x represent your usb key)
example for usb key /dev/sdb
dd if=/home/username/Downloads/slitaz-4.0.iso of=/dev/sdb
It"s seem SliTaz iso is hybrid from release 4.0.
Offline
Christphe! here is the boot entry-
*(for default linux index)-
recordfail
insmod ext2
set root='(hd0,5)'
search --no-floppy --fs-uuid --set 55d337bd-f9d1-41fc-a5eb-3913f4e43962
linux /boot/vimlinuz-2.6.39.4 root =UUID=55d337bd-f9d1-41fc-a5eb-3913f4e43962 ro text splash vga=791
*(for recovery mode index)-
echo 'loading linux 2.6.39.4...'
linux /boot/vimlinuz-2.6.39.4 root =UUID=55d337bd-f9d1-41fc-a5eb-3913f4e43962
echo 'loading initial ramdisk...'
*There are two more entries for memory test. I guess they aren't required...
*(5th entry is for Windows 7 loader on /dev/sda1)-
insmod ntfs
set root='(hd0,1)'
search --no-floppy --fs-uuid --set 0ECEED76CEED507D
chainloader +1
Hello ceel!
I used unetbootin to make a bootable pendrive for live booting with Slitaz. Later i tried it by using LinuxLive USB creator (it recognized Slitaz while creating bootable USB). In order to boot with Live Slitaz, I simply changed the boot order from BIOS & boot the hard disk with Pen drive. Select Default mode i.e. Live mode.
Offline
Christphe! here is the boot entry-
*(for default linux index)-
recordfail
insmod ext2
set root='(hd0,5)'
search --no-floppy --fs-uuid --set 55d337bd-f9d1-41fc-a5eb-3913f4e43962
linux /boot/vimlinuz-2.6.39.4 root =UUID=55d337bd-f9d1-41fc-a5eb-3913f4e43962 ro text splash vga=791
*(for recovery mode index)-
echo 'loading linux 2.6.39.4...'
linux /boot/vimlinuz-2.6.39.4 root =UUID=55d337bd-f9d1-41fc-a5eb-3913f4e43962
echo 'loading initial ramdisk...'
*There are two more entries for memory test. I guess they aren't required...
*(5th entry is for Windows 7 loader on /dev/sda1)-
insmod ntfs
set root='(hd0,1)'
search --no-floppy --fs-uuid --set 0ECEED76CEED507D
chainloader +1
Hello ceel!
I used unetbootin to make a bootable pendrive for live booting with Slitaz. Later i tried it by using LinuxLive USB creator also but no use, it shows the same error (Linux Live recognized Slitaz while creating bootable USB). In order to boot with Live Slitaz, I simply changed the boot order from BIOS & boot the hard disk with Pen drive. Select Default mode i.e. Live mode.
Offline
I had missed the liveusb unetbootin comment.
Just follow Shann's advice and reinstall slitaz on usb that way. It's both simple and proven.
Offline
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.57 MiB (Peak: 1.77 MiB) ]