ISO testing 201410

[belgiumsolydk]

Hi,

I tried to install the Solydk 64 iso but failed. (used last beta iso)
The life-usb booted well and when I established an internet connection the installer started up.
After putting in my name and password and push "next" the installer crashed with a fault (long one).
The SSD in the laptop is already partitioned in 1 partition btrfs and has 2 subvolumes : rootvol and home.
I did :
sudo mount -o noatime,discard,autodefrag,compress=lzo,space_cache,subvol=rootvol /dev/sda1 /mnt/rootvol/
sudo mount -o noatime,discard,autodefrag,compress=lzo,space_cache,subvol=home /dev/sda1 /mnt/home/

I suppose this is the reason the installer crashes. Any idea how to solve this?
Main reason for this setup is of course the snapshot possibility and the increased ssd-speed thanks to the compression.

[Deleted User 2775]

Hi,

Why not use correctly formatted md5sum file?
More than once i've had this error when trying to check the dwnloaded iso:
md5sum: solydx64_201411.iso.md5sum: no properly formatted MD5 checksum lines found

Currently the md5 file contains this:
SolydX 64-bit: c2791574a34e682f5b83bbc0be65e4c4

while a properly formatted formatted file would contain this:
c2791574a34e682f5b83bbc0be65e4c4 solydx64_201411.iso

[Deleted User 2764]

Both laptops the latest ISO installed fine. I did try without internet on the T61 and it complained of an index out of order in some python script when launching the installer but it didn't hang. Exited that dialog and connected to the internet and tried again. All went well after that.

[Arjen Balfoort]

It's 6:30 AM and I'm away for a few days.
The new ISOs are now in dev but I hadn't have the time to test them all.

[Deleted User 2764]

I'm working on the new system so when I'm ready I'll go grab SolydK64 ISO and use that on the new computer.

[bmccann]

I downloaded the 11/5/2014 Solydk-64 ISO and burned it to a USB stick using 'dd'. It boots fine into the Live environment (which I'm using to post this bug) but the installer fails. It starts and runs up to the disk partitioning step. At that time it crashes with the following error:

Code: Select all

Traceback (most recent call last):

  File "/usr/lib/live-installer/frontend/gtk_interface.py", line 828, in wizard_cb
    partitioning.build_partitions(self)

  File "/usr/lib/live-installer/partitioning.py", line 55, in build_partitions
    partition_setup = PartitionSetup()

  File "/usr/lib/live-installer/partitioning.py", line 204, in __init__
    self.disks = _get_attached_disks()

  File "/usr/lib/live-installer/partitioning.py", line 191, in _get_attached_disks
    type, device, removable, size, model = line.split(" ", 4)

ValueError: need more than 4 values to unpack

I'm trying to install to a new M-ITX build that currently only has Windows 10 Tech Preview (yes, Windows 10) installed. It has a GPT disk layout that was created when I installed Windows 10 onto a blank SSD:

Code: Select all

udo /sbin/parted -l /dev/sda
Model: ATA KINGSTON SH103S3 (scsi)
Disk /dev/sda: 120GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      1049kB  316MB   315MB   ntfs         Basic data partition          hidden, diag
 2      316MB   420MB   105MB   fat32        EFI system partition          boot, esp
 3      420MB   555MB   134MB                Microsoft reserved partition  msftres
 4      555MB   41.7GB  41.1GB  ntfs         Basic data partition          msftdata
 5      41.7GB  42.1GB  472MB   ntfs                                       hidden, diag

Model: ATA WDC WD6400BEVT-2 (scsi)
Disk /dev/sdb: 640GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size   Type     File system  Flags
 1      1049kB  344GB  344GB  primary  ntfs
 2      344GB   640GB  297GB  primary               lvm


Error: Invalid partition table - recursive partition on /dev/sdc.
Ignore/Cancel? i                                                          
Model:  USB Flash Memory (scsi)
Disk /dev/sdc: 2008MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start  End  Size  Type  File system  Flags

Note there are two disks, one GPT and one with the legacy partition table format. The second is a data hard drive.

Crap, I just noticed that parted isn't very happy with the partition table on the USB stick itself. I don't know if that's relevant. The 'fdisk' utility was OK with it:

Code: Select all

sudo /sbin/fdisk -l /dev/sdc

Disk /dev/sdc: 2008 MB, 2008023040 bytes
64 heads, 32 sectors/track, 1915 cylinders, total 3921920 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: 0x4870e929

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           0     3692543     1846272   17  Hidden HPFS/NTFS

BTW, I'm assuming GPT disks are supported by Solydxk. If that's not true then let me know. Otherwise, let me know if there's other data you need.

Thanks for your work on Solydxk.

[bmccann]

Just got the same error from 'get_attached_disks' in live-installer/partitioning.py while trying to install SolydX (not K like before) on an old laptop. That laptop has the old style MBR disk partition with Linux Mint installed. No Windows, no GPT. Just vanilla MBR partition.

This SolydX installation was also using yesterday's 11/5 ISO files.

The install process on latest ISO's seem pretty broken but they work OK running Live.

[Deleted User 2764]

I'll wait on the ISO then. I am upgrading RAM and HD this weekend, hopefully.

[freecicero]

FWIW - I downloaded and installed the current 2014-10 version today onto a brand new machine with no linux previously installed. I have run into a couple of minor issues:

1 - The user that I set up during the install refused to allow me to log in on first boot. I went around it an logged in as root, but I could not get that user to work despite trying several times to reboot, and also logging out after logging in as root. It didn't say bad password - just went blank for a second and returned to the login screen. I went ahead and set up a new user and deleted the old one but I've never had that happen before.

2 - Also, the software manager icon appears gone, and it is not in my favorites list. Typing the name into the selection box, brings it up, but with no icon.

3 - My screen, which is an old panel that is probably only 1026x768 (or whatever the standard size is) brings up no wallpaper, just a solid blue screen.

[rokytnji]

@freecicero

Did you md5sum the iso before installing? Because it sounds like a corrupted downloaded iso maybe.

[freecicero]

Strike what i said below -- just checked the dowloaded ISO again, and the mdsum was fine.

And i can add to the list of things to report that the updatemanager did not autostart either.

Of course all these things could be something I did wrong - just reporting FWIW - probably nothing

No, I didn't check the md5, so that may well be it. On first check now it DOESN'T match, so that must be it. Thanks!

[zerozero]

i'm installing the latest SolydK-64bit (from 05-Nov-2014 08:09) and i noticed also a few issues.
this time it seems like it's going to finish without issues.
i would recommend (from my experience so far) to:

1. check that you have an active internet connection (this is a known issue but the proposed fix isn't working as expected)

2. start the live-installer from the terminal with

Code: Select all

gksu live-installer

this shouldn't be needed but i found out that otherwise i was getting a

Code: Select all

Error opening /dev/sda: Permission denied

[zerozero]

installation is complete.
a few notes:
as i said above i had to start the live-installer with

Code: Select all

gksu live-installer

2 previous attempts (one without internet and another with) crashed in the same place: opening the partitioning page with this error

install-python-error.txt

(910 Bytes) Downloaded 80 times

attempting to install off-line failed with the output attached

install-error-nonet.txt

(4.58 KiB) Downloaded 81 times

which i very similar to the output of trying to install with net

install-error-net.txt

(2.89 KiB) Downloaded 74 times

===
finally the log of the successful installation

install-ok.txt

(35.8 KiB) Downloaded 77 times

===
one of things i immediately noticed as a regression is the lack of information in the partitioning page;
specially for me that have always several distros installed and not always know where is what

there's no indication of the operation systems on the partitions and the free space.

[bmccann]

Just got the same error from 'get_attached_disks' in live-installer/partitioning.py while trying to install SolydX (not K like before) on an old laptop. That laptop has the old style MBR disk partition with Linux Mint installed. No Windows, no GPT. Just vanilla MBR partition.

This SolydX installation was also using yesterday's 11/5 ISO files.

The install process on latest ISO's seem pretty broken but they work OK running Live.

The installer is still crashing in the partitioning step with a failure in 'get_attached_disks'. (See my previous posting for the stack trace). I verified:

• MD5 checksum on the ISO is correct.

• Internet connection is up.

• Live-installer was started using 'gksu' as suggested by zerozero.

I checked the partitioning.py script and it is parsing the output of 'lsblk' to identify disk drives. It expects 5 columns separated by spaces but one of my 'drives' only has four columns. Here is the output of 'lsblk -rindo TYPE,NAME,RM,SIZE,MODEL' on my machine:

Code: Select all

disk sda 0 59.6G STT_FT64GX25H
disk sdb 1 1.9G USB Flash Memory
loop loop0 0 1.4G

Note the loopback device has no description. I modified partitioning.py to first check only for the type and device and then, only for disks, re-parse the lsblk output to pick up the other data:

Code: Select all

        def _get_attached_disks():
            disks = []
            exclude_devices = '/dev/sr0 /dev/sr1 /dev/cdrom /dev/dvd'.split()
            lsblk = getoutput('lsblk -rindo TYPE,NAME,RM,SIZE,MODEL | sort -k3,2')
            for line in lsblk:
                # Don't do a full parse until we know this line describes a disk.
                type, device = line.split(" ", 1)
                if type == "disk" and device not in exclude_devices:
                    type, device, removable, size, model = line.split(" ", 4)
                    device = "/dev/" + device
                    # convert size to manufacturer's size for show, e.g. in GB, not GiB!
                    size = str(int(float(size[:-1]) * (1024/1000)**'BkMGTPEZY'.index(size[-1]))) + size[-1]
                    description = '{} ({}B)'.format(model.strip(), size)
                    if int(removable):
                        description = _('Removable:') + ' ' + description
                    disks.append((device, description))
            return disks

This got me past the installer crash. I'm setting up partitions now.

The remainder off the installation was uneventful and I'm running now on a new 10/15 installation of SolydX. Looks good so far!

[zerozero]

@bmccann
you were hit by a different issue;
thaanks for reporting and also for the workaround
Schoelje is not available in the next few days but surely when he comes back he will pick these issues.

[bmccann]

@bmccann
you were hit by a different issue;
thaanks for reporting and also for the workaround
Schoelje is not available in the next few days but surely when he comes back he will pick these issues.

You're welcome.

I noticed another bug in the same installer function. The 'exclude_devices' logic won't work because 'lsblk' reports device names without the '/dev/' but the exclude device list does include '/dev/' in each device name. The following patch fixes that by removing '/dev/' in 'exclude_devices':

Code: Select all

        def _get_attached_disks():
            disks = []
            exclude_devices = 'sr0 sr1 cdrom dvd'.split()
            lsblk = getoutput('lsblk -rindo TYPE,NAME,RM,SIZE,MODEL | sort -k3,2')
            for line in lsblk:
                # Don't do a full parse until we know this line describes a disk.
                type, device = line.split(" ", 1)
                if type == "disk" and device not in exclude_devices:
                    type, device, removable, size, model = line.split(" ", 4)
                    device = "/dev/" + device
                    # convert size to manufacturer's size for show, e.g. in GB, not GiB!
                    size = str(int(float(size[:-1]) * (1024/1000)**'BkMGTPEZY'.index(size[-1]))) + size[-1]
                    description = '{} ({}B)'.format(model.strip(), size)
                    if int(removable):
                        description = _('Removable:') + ' ' + description
                    disks.append((device, description))
            return disks

[grizzler]

As I wrote in my 30-10-2014 SolydK test report, I think the Dutch translation of the slide show needs work. My suggestions are attached.

[balloon]

I tried latest iso and advanced an installer in Japanese and grasped that a part was displayed in English.
I recognize that translation work of each national language is necessary, but how should this support?

[Arjen Balfoort]

I'm still trying to get this technically correct and translations are of lower priority for me right now.
However, if you feel you like to check the translations for your language now, I've uploaded the .po files.

live-installer: https://github.com/SolydXK/live-install ... changes/po
live-installer-slideshow: https://github.com/SolydXK/live-install ... ow/po4a/po

[Arjen Balfoort]

I have finally succeeded in building ISOs that actually install.
All of them were tested with different settings. I used ext4 only to install.

You can download them from dev: http://downloads.solydxk.nl/dev/