Salix Live Xfce 13.37 RC2

[mimosa]

I've since wiped the stick:

Code: Select all

dd if=/dev/zero of=/dev/sdc


and created a new partition table and fat16 partition with Gparted, with no improvement. Here is some output:

Code: Select all

root[vanilla]# fdisk -l /dev/sdc

Disk /dev/sdc: 4022 MB, 4022337536 bytes
6 heads, 28 sectors/track, 46762 cylinders, total 7856128 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0004e1e5

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048     7856127     3927040    6  FAT16
root[vanilla]# parted /dev/sdc print
Model: Kingston DataTraveler 2.0 (scsi)
Disk /dev/sdc: 4022MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  4022MB  4021MB  primary  fat16        boot

I'm currently trying to install the RC2 on a different stick (and will use the opportunity to test your script again). I used the board's "Select all" feature and pasted it into vim using shift + middle mouse button.

Yes the new script works. Now I'll reboot and see if Salix does. If not, it's surely not the other stick that's at fault!

[mimosa]

OK, I've finally got it working with the other USB.

No time to test more now because I have a plane to catch, but I can report two more things:


A worrying error message about "missing label" right at the beginning of boot


Persistent storage still only seems to work after rebooting. I created the persistent file, copied some stuff and installed an app, and none of it was there when I rebooted.

[Shador]

Did you also use FAT16 for that other stick that worked? Do other bootloaders/live cds/... work for the failing stick? Did you choose to overwrite the MBR loader? If you didn't try that first.

If it still doesn't work you can try with a different MBR loader. Run 'lilo -M /dev/sdc mbr'.

If nothing of this helps try the following:
You could try booting that stick with qemu. Be sure to umount the stick otherwise that could result in data corruption. Then run 'qemu -hda /dev/sdX'.

You could try running 'grub-install --boot-directory=/media/<your stick>/boot /dev/sdX'. That's the way grub2 was installed alone (i.e. without syslinux) with 13.1.

[mimosa]

The stick that worked had my old Salix Live 13.1 on it, fat32 I think - now overwritten.

When I get back from Rio I'll try putting that on the faulty stick, and try formatting as fat32 - in the spirit of the scientific method. My guess is it's a hardware fault though.

Thanks for all your help!

[mimosa]

Salix 13.1works on the "faulty" USB, still formatted as fat16. I took it with me, and so I'll test to see if the 13.37 problem has anything to do with fat16 versus fat32. Results tomorrow probably!

[JRD]

Just a note, I saw that you have the file "salixliveusb-2012-01-06.live" in the root of your USB disk. This file has the wrong name. It should be "salix-xfce-13.37-32-rc2.live". You cannot change the name.
FAT16 is no problem for SaLT system. Maybe it causes a problem with syslinux, but I do think that syslinux works for FAT16 and FAT32.

[Shador]

Just a note, I saw that you have the file "salixliveusb-2012-01-06.live" in the root of your USB disk. This file has the wrong name. It should be "salix-xfce-13.37-32-rc2.live". You cannot change the name.

Doesn't liveclone rebuild the grub2-linux.img? So if it's liveclone who changed that name and the grub2-linux.img was updated accordingly it should be fine.

[Akuna]

Doesn't liveclone rebuild the grub2-linux.img? So if it's liveclone who changed that name and the grub2-linux.img was updated accordingly it should be fine.

Yes, that is what LiveClone is supposed to do. It might be good to check if there is a different behaviour building the live usb key 'manually' or with LiveClone.

BTW, I encountered that behaviour as well (the flashing prompt instead of the grub menu) but that was with a key that did work on some machines while it didn't on other machines, so I assumed it was a problem related to a particular machine rather than with the usb key.

I'll do more testing when I'm back home (in a few days).

[Shador]

Please somebody try tinstalling the lilo mbr loader. I had a problem at some point to with the default parted mbr loader which caused flashing coursor. But it was fixed by zeroing the mbr and creating a new partition table.

[mimosa]

That sounds like what happened to me - also what Akuna says about wondering whether to blame the stick. I think this happened with LiveClone as well as with (Shador's improved) install-on-usb script.