http://forum.porteus.org/viewtopic.php? ... 37804b1b2f
@burninbush; You are a very lucky man, you win a warning, and maybe, next time you will be able to win a ban
![Wink ;)](./images/smilies/icon_e_wink.gif)
++
Seems you don't read this forum nor had a serious look at the Salix LiveCDs. One of the reasons I am a rather heavy user of Salix Live is the possibility to adapt it to your needs through modules ('.salt', not '.xz').burninbush wrote:My interest in Salix was only for the live media, don't need another standard install of slack 13.37. I saw the structure of the dvd and thought perhaps you intended to support expansion of that system with xz modules, a la Slax/Nimblex/Porteus/others, but in looking at the site I see no evidence for that.
Just to say thank you.JRD wrote:The SaLT system use "blkid" and "file" to find and determine the filesystem. If any of these tools have problem with ext4, then it is the reason of not finding the distro. I will look into these.
P.S. These tools are not the exact tools you can find in your distro. The first one in the one of busybox, the second one is statically compiled by me to be included in the initrd.
That's not true. At least not with Salix. Other distros automatically recreate the grub.cfg on certain events so it's a bad idea as it might get overwritten. Also for a regular system the auto-generation is much more convenient.ikke wrote:One of the reasons I don't use grub2 is that I am not allowed to edit the grub.cfg
I don't have it anymore. But that's what I used: http://www.supergrubdisk.org/wiki/Loopb ... _an_iso.3Fikke wrote:I do not know how to handle grub2 so that salixlive frugally installed can be booted. Can you provide with your grub2 entry to boot the iso from an ext4 partition. Would like to try it.
Code: Select all
menuentry 'Arch Linux GNU/Linux, mit Linux pf kernel' {
set root='hd0,msdos3'
linux /boot/vmlinuz-linux-pf root=/dev/sda3 ro quiet resume=/dev/sda2 resume=swap:/dev/sda2
initrd /boot/initramfs-linux-pf.img
}
Code: Select all
'/$IDENT_FILE:$IDENT_CONTENT' not found in $d
Guess this is a grub2 entry for an Arch linux full install not frugal.Shador wrote:That's an example from my Arch linux menuentry.Code: Select all
menuentry 'Arch Linux GNU/Linux, mit Linux pf kernel' { set root='hd0,msdos3' linux /boot/vmlinuz-linux-pf root=/dev/sda3 ro quiet resume=/dev/sda2 resume=swap:/dev/sda2 initrd /boot/initramfs-linux-pf.img }
Shador wrote:Anyway, I'm planning to do a short overview about the possibilities to boot live, which can grow in detail in the future.
This is the hint which may help solve the problem ... Discovered the SalixLive is looking for the salix-xfce-13.37-32.live-file on the hard disk only.Shador wrote: Could you post the content of the .live file here. It would also be useful if you try booting with 'debug' on the kernel cmdline. When you're dropped to a debugshell just continue. Try to look for lines like this:Especially try to catch whether the device with Salix on it appears.Code: Select all
'/$IDENT_FILE:$IDENT_CONTENT' not found in $d
Code: Select all
Finding salix Live v.xfce-13.37-32 device
Mounting /dev/sdc1 on /mnt/sdc1 with type 'ext2' and options ...
Mounting /dev/sda1 on /mnt/sda1 with type 'ntfs-3g' and options ...
/salix-xfce-13.37-32.live:88d818ae211826b61c7f038ab0e1dee1 not found in /dev/sda1
Fatal Error
Could not find the distro to boot
File searched : salix-xfce-13.37-32.live
Content searched : 88d818ae211826b61c7f038ab0e1dee1
Code: Select all
Mounting /dev/sdc1 on /mnt/sdc1 with type 'ext2' and options ...
Code: Select all
# blkid
# cat /tmp/devices
# file -s -f /dev/sdc1
This mount fails (silently) because the partition is mistakenly detected as ext2 by file and thus checking the device is skipped. So it's trying to look there but can't. Could you check what a normal system's file outputs for that partition:ikke wrote:Mounting /dev/sdc1 on /mnt/sdc1 with type 'ext2' and options ..
Code: Select all
file -s /dev/sdc1
Yes, but for a frugal install it's just the kernel parameters that's different, right? And those entirely depend on the distro anyway.ikke wrote: Guess this is a grub2 entry for an Arch linux full install not frugal.
Thank you very much JRD and Shador for prompt reaction. We might be on the right way ...JRD wrote:Ahhh, very helpfull output!
Seems that your ext4 usb partition is recognized as...ext2 as you can see it from this:
When you have a shell (in debug) can you post the ouptput of the three following commands:Thanks...I'm pretty sure I will find a fix with these output.Code: Select all
# blkid # cat /tmp/devices # file -s -f /dev/sdc1
Code: Select all
# blkid
Label="zangu_8M"
/dev/sdc1 UUID="64 ... f4"
/dev/sda1 UUID="46 ... FB"
/dev/ram0 "03 ... 7e"
#cat /tmp/devices
/dev/sdc1: Linux rev 1.0 ext2 filesystem (mounted or unclean) UUID="64 ... f4" (extents) (large files) (huge files)
/dev/sda1 X86 boot sector, code offset 0X52 OEM-ID "NTFS" ...
#file -s /dev/sdc1
/dev/sdc1: Linux rev 1.0 ext2 filesystem (mounted or unclean) UUID="64 ... f4" (extents) (large files) (huge files)
#file -s -f /dev/sdc1
Code: Select all
# dd if=/dev/sdc1 of=first1M bs=1M count=1
Code: Select all
# dd if=/dev/zero of=ext4 bs=1M count=10 2>/dev/null && mkfs.ext4 -F ext4 >/dev/null 2>&1 && file ext4 && tune2fs -O ^has_journal ext4 && file ext4
ext4: Linux rev 1.0 ext4 filesystem data, UUID=e8052e1a-c68a-4e69-a801-2bd113194d68 (extents) (huge files)
tune2fs 1.41.14 (22-Dec-2010)
ext4: Linux rev 1.0 ext2 filesystem data, UUID=e8052e1a-c68a-4e69-a801-2bd113194d68 (extents) (huge files)
Code: Select all
# tune2fs -j /dev/sdc1