SolydK10 installation failing on computer with multiple drives

Questions about SolydX and SolydK installation.
cmf5
Posts: 24
Joined: 12 Mar 2014 14:01

SolydK10 installation failing on computer with multiple drives

Postby cmf5 » 06 Jul 2020 06:05

I have tried unsuccessfully to install SolydK10- 201909 from a bootable USB onto my desktop computer that has four hard drives, one for the OS's and the other three for data. I should point out that I am trying to install SolydK as a dual boot with Windows 10, which is on the same hard drive. I created two ext4 partitions (and a swap partition) for installing / and /home onto separate partitions. After the installer starts up, I receive a message about an unreadable partition table on each of the data drives (which are formatted as ext4), with the offer to create a new partition table on each drive, thereby destroying the data on the drive. I answer "no" to these three prompts (I do not receive this error prompt for the OS drive to which I wish to install SolydK), and then the installer fails with the message linked below as an image.

I have a vague memory of running into this issue years ago when I was running SolydK (between running Mepis and Linux Mint), and I think the solution was to open the desktop case, disconnect the data drive cables, install SolydK, then reconnect the drives. A hassle.

Surely this has been fixed since then, right? It seems like there should be an easier fix. Any help is much appreciated.

https://flic.kr/p/2jizfkD

User avatar
ilu
Posts: 2716
Joined: 09 Oct 2013 12:45

Re: SolydK10 installation failing on computer with multiple drives

Postby ilu » 06 Jul 2020 13:34

Well it does not seem to be fixed, we'd need to know the exact problem first. Nobody else has reported this behaviour as far as I remember. Obviously the installer sees something on your data drives it does not recognise. So we want to know why. Since you say they are EXT4 Windowws can't have anything to do with it.
Please start the live ISO and post the output of fdisk -l.

Debugging purposes aside, if I were you, I'd really disconnect the data drives. Better safe than sorry.

The problem with the installer is that we want it to be as easy to use as possible. It would be much easier if we could just ask the user where to install. But a lot of people wouldn't be able to answer that question. So the installer tries to find its own way around the system ... which might fail under special circumstances.

An idea to improve this situation could be an option to "ignore this partition, just mount it afterwards" - which the user could check, for whatever reason. Arjen, what do you think?

User avatar
Arjen Balfoort
Site Admin
Posts: 9506
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: SolydK10 installation failing on computer with multiple drives

Postby Arjen Balfoort » 06 Jul 2020 16:45

It might be possible to do something about the error but I will need to recreate the circumstances exactly. Including recreating the error and that might not be possible to do in VB.


SolydXK needs you!
Development | Testing | Translations

cmf5
Posts: 24
Joined: 12 Mar 2014 14:01

Re: SolydK10 installation failing on computer with multiple drives

Postby cmf5 » 06 Jul 2020 16:52

ilu wrote:
06 Jul 2020 13:34
Well it does not seem to be fixed, we'd need to know the exact problem first. Nobody else has reported this behaviour as far as I remember. Obviously the installer sees something on your data drives it does not recognise. So we want to know why. Since you say they are EXT4 Windowws can't have anything to do with it.
Please start the live ISO and post the output of fdisk -l.

Debugging purposes aside, if I were you, I'd really disconnect the data drives. Better safe than sorry.

The problem with the installer is that we want it to be as easy to use as possible. It would be much easier if we could just ask the user where to install. But a lot of people wouldn't be able to answer that question. So the installer tries to find its own way around the system ... which might fail under special circumstances.

An idea to improve this situation could be an option to "ignore this partition, just mount it afterwards" - which the user could check, for whatever reason. Arjen, what do you think?
Thanks for your reply.

Does the installer offer a "Something else" option when it comes to choosing where to install, allowing the user to select where to install the bootloader, root, and home partitions? I ask because I can't get very far into the installer before it crashes.

Here is my fdisk output. Just to clarify, I installed Windows to the sda 1, 2, 3, 4 partitions. I wish to install SolydK / to sda6 and /home to sda7:

Code: Select all

solydxk@solydxk:~$ sudo fdisk -l
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 840 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 2BA51CC4-D8A3-4D74-AB63-AF39635B03CA

Device         Start       End   Sectors  Size Type
/dev/sda1       2048    923647    921600  450M Windows recovery envi
/dev/sda2     923648   1128447    204800  100M EFI System
/dev/sda3    1128448   1161215     32768   16M Microsoft reserved
/dev/sda4    1161216 236136447 234975232  112G Microsoft basic data
/dev/sda5  236136448 242280447   6144000    3G Linux swap
/dev/sda6  242280448 303720447  61440000 29.3G Linux filesystem
/dev/sda7  303720448 488396799 184676352 88.1G Linux filesystem


Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EZEX-00Z
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xbc1a9a55

Device     Boot Start        End    Sectors   Size Id Type
/dev/sdb1          63 1953520064 1953520002 931.5G  5 Extended
/dev/sdb5         126 1953520064 1953519939 931.5G 83 Linux

Partition 1 does not start on physical sector boundary.
Partition 5 does not start on physical sector boundary.


Disk /dev/sdc: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 850 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x16510357

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdc1          63 976768064 976768002 465.8G  5 Extended
/dev/sdc5         126 976768064 976767939 465.8G 83 Linux


Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD1002FAEX-0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000627e2

Device     Boot Start        End    Sectors   Size Id Type
/dev/sdd1          63 1953520064 1953520002 931.5G  5 Extended
/dev/sdd5         126 1953520064 1953519939 931.5G 83 Linux




Disk /dev/sde: 7.5 GiB, 8004304896 bytes, 15633408 sectors
Disk model: Cruzer Edge     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1a895776

Device     Boot Start     End Sectors  Size Id Type
/dev/sde1  *        0 4620287 4620288  2.2G  0 Empty
/dev/sde2         284    4379    4096    2M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 2.1 GiB, 2273968128 bytes, 4441344 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


cmf5
Posts: 24
Joined: 12 Mar 2014 14:01

Re: SolydK10 installation failing on computer with multiple drives

Postby cmf5 » 06 Jul 2020 20:36

FWIW, I tried installation using the 202007 iso, and I encountered the same error.

User avatar
ilu
Posts: 2716
Joined: 09 Oct 2013 12:45

Re: SolydK10 installation failing on computer with multiple drives

Postby ilu » 07 Jul 2020 00:25

I overlooked the link to the screenshot you posted in your first post and I can neither read nor download it from that site. You can upload screenshots here in this forum, there's a tab called "attachments" under the editor window.
Does the installer offer a "Something else" option when it comes to choosing where to install, allowing the user to select where to install the bootloader, root, and home partitions? I ask because I can't get very far into the installer before it crashes.
Of course, but the installer probably crashed before that window even comes up.
After the installer starts up, I receive a message about an unreadable partition table on each of the data drives (which are formatted as ext4), with the offer to create a new partition table on each drive, thereby destroying the data on the drive.
I'd like to see the exact wording of that message, when that message comes up and, dunno, maybe also what it looks like.

For screenshots please use the upload function of this forum.

cmf5
Posts: 24
Joined: 12 Mar 2014 14:01

Re: SolydK10 installation failing on computer with multiple drives

Postby cmf5 » 07 Jul 2020 01:55

Please see the screenshot below. Unfortunately I do not have a picture of the partition warning, but it showed up for each of the non-OS drives, cited the drive by string that included the vendor and model, asked to install a partition table on the drive, and warned that the data would be destroyed if I agreed to install a partition table.

I was able to install openSUSE as a dual boot today without a problem and am testing that out. I'd prefer to stick with a Debian based distro, but this experience has me concerned about potential future problems with SolydK so I'm trying out openSUSE in the meantime.

Thanks again for your help.

50081981731_ab05cc9c98_c.jpg

cmf5
Posts: 24
Joined: 12 Mar 2014 14:01

Re: SolydK10 installation failing on computer with multiple drives

Postby cmf5 » 07 Jul 2020 15:36

Just a follow up to my last post. If we can solve this issue soon, I'd love to use SolydK as my main distro. I can't afford to have my desktop out of commission for very long though, so I'm hoping we find a solution asap.

Also, regarding the missing partition table message, it seems to be one that normally shows up when installing on a blank drive. I saw this same message show up in a video (https://youtu.be/mVbYwFeaqrA?t=66) that demonstrated installation into a virtual drive. The problem is that this message is showing up for drives that are formatted correctly for ext4, contain data, and are not the drives on which I wish to install SolydK. As noted before, I don't think the drive on which I intend to install SolydK showed up in such a message, oddly enough.

Finally, these missing partition table messages may be a separate issue from the error message that showed up after I said no to the three queries about creating new partition tables on my data drives and before the installer quit. I've posted that error message in a previous post above. I don't know enough to interpret that message, but I'm hoping someone else can. Thanks.

User avatar
ilu
Posts: 2716
Joined: 09 Oct 2013 12:45

Re: SolydK10 installation failing on computer with multiple drives

Postby ilu » 07 Jul 2020 17:05

I think that's two separate errors. The installer should not fail with an exception if it doesn't find a usable partition. It should fail gracefully. I think there's an uncaught exception. But that is Arjens turf and not really relevant to your problem.

The installer does not do its own magic but uses the GNU parted library. I'm wondering why parted doesn't recognise your partitions. The only atypical thing I can see on the disks in question is that they don't have a primary partition, just an extended one. I don't know if that can cause the problem.
Let's try sudo parted -l. You should be able to issue that command from Suse but it would probably be better to use the live ISO just to be consistent. If it doesn't have parted, install it with apt install parted. I want to see the type of either primary/extended/logical on the dos (non-gpt) disks.

If parted -l does not work, try sudo parted /dev/sda. Then type print and after that quit. Now do the same on the next disk. Don't do anything else but "print". Here's an example of how parted works: https://serverfault.com/questions/45172 ... y-in-linux

cmf5
Posts: 24
Joined: 12 Mar 2014 14:01

Re: SolydK10 installation failing on computer with multiple drives

Postby cmf5 » 07 Jul 2020 21:21

Thanks for your reply, ilu. Here is the output of parted -l:

Code: Select all

solydxk@solydxk:~$ sudo parted -l
Model: ATA Samsung SSD 840 (scsi)
Disk /dev/sda: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system     Name                          Flags
 1      1049kB  473MB  472MB   ntfs            Basic data partition          hidden, diag
 2      473MB   578MB  105MB   fat32           EFI system partition          boot, esp
 3      578MB   595MB  16.8MB                  Microsoft reserved partition  msftres
 4      595MB   121GB  120GB   ntfs            Basic data partition          msftdata
 5      121GB   124GB  3146MB  linux-swap(v1)
 6      124GB   156GB  31.5GB  ext4
 7      156GB   250GB  94.6GB  ext4


Model: ATA WDC WD10EZEX-00Z (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type      File system  Flags
 1      32.3kB  1000GB  1000GB  extended
 5      64.5kB  1000GB  1000GB  logical   ext4


Model: ATA Samsung SSD 850 (scsi)
Disk /dev/sdc: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size   Type      File system  Flags
 1      32.3kB  500GB  500GB  extended
 5      64.5kB  500GB  500GB  logical   ext4


Model: ATA WDC WD1002FAEX-0 (scsi)
Disk /dev/sdd: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type      File system  Flags
 1      32.3kB  1000GB  1000GB  extended
 5      64.5kB  1000GB  1000GB  logical   ext4


Model: SanDisk Cruzer (scsi)
Disk /dev/sde: 4013MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start  End     Size    Type     File system  Flags
 2      147kB  2245kB  2097kB  primary               esp


solydxk@solydxk:~$ print
I noticed that sda has a gpt partition map with what appear to be primary partitions, while the others have msdos with extended/logical partitions. Does the SolydK installer not recognize msdos partition maps? Why would a problem with those drives cause a the installer to fail when the intended drive had a gpt map? :?

User avatar
Arjen Balfoort
Site Admin
Posts: 9506
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: SolydK10 installation failing on computer with multiple drives

Postby Arjen Balfoort » 08 Jul 2020 07:18

No, I don't think that that causes the problem. However, I see that you some disks (sdb, sdc, sdd) do not have a primary partition, only an extended partition. Is that right?

If I have time this weekend I'll try to recreate the setup in VB and see if that brings us any further.


SolydXK needs you!
Development | Testing | Translations

cmf5
Posts: 24
Joined: 12 Mar 2014 14:01

Re: SolydK10 installation failing on computer with multiple drives

Postby cmf5 » 08 Jul 2020 17:15

Arjen Balfoort wrote:
08 Jul 2020 07:18
No, I don't think that that causes the problem. However, I see that you some disks (sdb, sdc, sdd) do not have a primary partition, only an extended partition. Is that right?

If I have time this weekend I'll try to recreate the setup in VB and see if that brings us any further.
Yes, that is correct. Assuming that SolydK needs to be installed on a disk with a primary partition, it seems like the installer should have defaulted to using sda, which is formatted with the necessary partition and partition map.

From the picture of the long error message, can you determine whether the problem is the extended partitions on the data disks or something else entirely? I'm curious about what that message is telling you.

User avatar
ilu
Posts: 2716
Joined: 09 Oct 2013 12:45

Re: SolydK10 installation failing on computer with multiple drives

Postby ilu » 09 Jul 2020 03:21

Sadly the picture is such a low resolution that I'm not able to read all of the message. But it tell us, that python had to stop executing the installer because a needed data entry is missing. This entry should have been provided by parted which for some reason did not happen. When you called parted in the terminal everything worked allright - so why? mbr and gpt are very common things, so that's not it. But the missing primary partition is specific to your hardware setup so maybe .... Let's see what Arjen finds.

User avatar
Arjen Balfoort
Site Admin
Posts: 9506
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: SolydK10 installation failing on computer with multiple drives

Postby Arjen Balfoort » 09 Jul 2020 12:00

I recreated (more or less) your situation in VB:

Code: Select all

solydxk@solydxk:~$ sudo parted -l
Model: ATA VBOX HARDDISK (scsi)
Disk /dev/sda: 34.4GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name  Flags
 1      1049kB  496MB   495MB   ntfs                  hidden, diag
 2      496MB   606MB   110MB   fat32                 boot, esp
 3      606MB   624MB   17.8MB                        msftres
 4      624MB   2721MB  2097MB  ntfs                  msftdata
 5      2721MB  4818MB  2097MB  linux-swap(v1)        swap
 6      4818MB  25.8GB  21.0GB  ext4
 7      25.8GB  34.4GB  8569MB  ext4


Model: ATA VBOX HARDDISK (scsi)
Disk /dev/sdb: 17.2GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type      File system  Flags
 1      1049kB  17.2GB  17.2GB  extended
 5      2097kB  17.2GB  17.2GB  logical   ext4


Warning: Unable to open /dev/sr0 read-write (Read-only file system).  /dev/sr0
has been opened read-only.
                                                                    Model: VBOX CD-ROM (scsi)
Disk /dev/sr0: 2548MB
Sector size (logical/physical): 2048B/2048B
Partition Table: msdos
Disk Flags: 

Number  Start  End     Size    Type     File system  Flags
 2      590kB  8978kB  8389kB  primary               esp
Sizes differ and I was unable to create a swap partition without the swap flag, but I don't think that's what's causing the error.

Run live-installer-3 from terminal to see the output:

Code: Select all

solydxk@solydxk:~$ live-installer-3
Listing '/usr/lib/live-installer-3/'...
Listing '/usr/lib/live-installer-3/localize'...
Listing '/usr/lib/live-installer-3/scripts'...
set background_image /usr/share/live-installer-3/images/splash-bgk.png
Run command: apt-get update
Hit:1 http://deb.debian.org/debian bullseye InRele...
Hit:2 http://deb.debian.org/debian bullseye-update...
Hit:3 https://repository.solydxk.com solydxk-11 In...
Reading package lists...
Run command: apt-get install  -y --allow-downgrades --allow-remove-essential --allow-change-held-packages live-installer-3*
Reading package lists...
Building dependency tree...
Reading state information...
live-installer-3 is already the newest version (20...
live-installer-3-slideshow is already the newest v...
0 upgraded, 0 newly installed, 0 to remove and 3 n...
Executing: cat /proc/cmdline
Executing: ps -ef | grep -v grep | grep 'python3' | grep 'gtk_interface.py' | awk '{print $2}'
Executing: logname
Executing: dpkg -S bin/mkfs. | grep -v cramfs | cut -d'.' -f 2 | sort
--------------------->>> Setup information init <<<---------------------
Live Setup
Logged user: solydxk
Target directory: /target
Debian frontend: DEBIAN_FRONTEND=noninteractive
apt options: --assume-yes --quiet --allow-downgrades --allow-remove-essential --allow-change-held-packages -o Dpkg::Options::=--force-confmiss -o Dpkg::Options::=--force-confnew
-------------------------------------------------------------------------
Executing: pidof xfce4-session
Command 'pidof xfce4-session' returned non-zero exit status 1.
Executing: cat /etc/timezone
Executing: isoquery --iso 3166-1 | cut -f1,4-
Executing: isoquery --iso 639-3
Executing: awk -F'[@ \.]' '/UTF-8/{ print $1 }' /usr/share/i18n/SUPPORTED | uniq
awk: warning: escape sequence `\.' treated as plain `.'
Error adding locale 'ber_DZ'
Error adding locale 'ber_MA'
Executing: convert /usr/share/pixmaps/faces/user-generic.png -resize x96 /tmp/live-installer-3-face.png
Executing: awk '/^[^#]/{ print $1,$2,$3 }' /usr/share/zoneinfo/zone.tab | sort -k3
Executing: setxkbmap -query | awk -F"(,|[ ]+)" '/^(model:|layout:)/ {print $2}'
Set user language: nl_NL
Executing: modprobe efivars >/dev/null 2>&1
Executing: findmnt -n -o source /lib/live/mount/findiso 2>/dev/null || :
Executing: LC_ALL=en_US.UTF-8 lsblk -rindo TYPE,NAME,RM,SIZE,MODEL | sort -k3,2
Executing: cat /sys/block/sda/queue/rotational 2>/dev/null
device = /dev/sda
pen_drives = []
detachable = False
Executing: cat /sys/block/sdb/queue/rotational 2>/dev/null
device = /dev/sdb
pen_drives = []
detachable = False
Disks: [('/dev/sda', 'VBOX_HARDDISK (34GB)', False, False), ('/dev/sdb', 'VBOX_HARDDISK (17GB)', False, False)]
Executing: env LANG=C cryptsetup status sda1
Command 'env LANG=C cryptsetup status sda1' returned non-zero exit status 4.
Executing: blkid -o value -s TYPE /dev/sda1
Executing: blkid -o value -s TYPE /dev/sda1
Executing: lsblk -n -o LABEL /dev/sda1 | grep -v "^$"
Command 'lsblk -n -o LABEL /dev/sda1 | grep -v "^$"' returned non-zero exit status 1.
Executing: grep /dev/sda1 /proc/mounts | awk '{print $2}'
Executing: mkdir -p /tmp/live-installer-3/sda1; mount --read-only /dev/sda1 /tmp/live-installer-3/sda1
Executing: grep /dev/sda1 /proc/mounts | awk '{print $2}'
Executing: umount -f /dev/sda1
Executing: env LANG=C cryptsetup status sda2
Command 'env LANG=C cryptsetup status sda2' returned non-zero exit status 4.
Executing: blkid -o value -s TYPE /dev/sda2
Executing: blkid -o value -s TYPE /dev/sda2
Executing: lsblk -n -o LABEL /dev/sda2 | grep -v "^$"
Command 'lsblk -n -o LABEL /dev/sda2 | grep -v "^$"' returned non-zero exit status 1.
Executing: grep /dev/sda2 /proc/mounts | awk '{print $2}'
Executing: mkdir -p /tmp/live-installer-3/sda2; mount --read-only /dev/sda2 /tmp/live-installer-3/sda2
Executing: grep /dev/sda2 /proc/mounts | awk '{print $2}'
Executing: umount -f /dev/sda2
Executing: env LANG=C cryptsetup status sda3
Command 'env LANG=C cryptsetup status sda3' returned non-zero exit status 4.
Executing: blkid -o value -s TYPE /dev/sda3
Executing: blkid -o value -s TYPE /dev/sda3
Executing: blkid -o value -s TYPE /dev/sda3
Executing: lsblk -n -o LABEL /dev/sda3 | grep -v "^$"
Command 'lsblk -n -o LABEL /dev/sda3 | grep -v "^$"' returned non-zero exit status 1.
Executing: grep /dev/sda3 /proc/mounts | awk '{print $2}'
Executing: mkdir -p /tmp/live-installer-3/sda3; mount --read-only /dev/sda3 /tmp/live-installer-3/sda3
mount.nilfs2: Error while mounting /dev/sda3 on /tmp/live-installer-3/sda3: Invalid argument
Executing: grep /dev/sda3 /proc/mounts | awk '{print $2}'
WARNING: Partition /dev/sda3 or type  failed to mount ([Errno 2] No such file or directory: '')
Executing: env LANG=C cryptsetup status sda4
Command 'env LANG=C cryptsetup status sda4' returned non-zero exit status 4.
Executing: blkid -o value -s TYPE /dev/sda4
Executing: blkid -o value -s TYPE /dev/sda4
Executing: lsblk -n -o LABEL /dev/sda4 | grep -v "^$"
Command 'lsblk -n -o LABEL /dev/sda4 | grep -v "^$"' returned non-zero exit status 1.
Executing: grep /dev/sda4 /proc/mounts | awk '{print $2}'
Executing: mkdir -p /tmp/live-installer-3/sda4; mount --read-only /dev/sda4 /tmp/live-installer-3/sda4
Executing: grep /dev/sda4 /proc/mounts | awk '{print $2}'
Executing: umount -f /dev/sda4
Executing: env LANG=C cryptsetup status sda5
Command 'env LANG=C cryptsetup status sda5' returned non-zero exit status 4.
Executing: blkid -o value -s TYPE /dev/sda5
Executing: blkid -o value -s TYPE /dev/sda5
Executing: lsblk -n -o LABEL /dev/sda5 | grep -v "^$"
Command 'lsblk -n -o LABEL /dev/sda5 | grep -v "^$"' returned non-zero exit status 1.
Executing: grep /dev/sda5 /proc/mounts | awk '{print $2}'
WARNING: Partition /dev/sda5 or type swap failed to mount ([Errno 2] No such file or directory: '')
Executing: env LANG=C cryptsetup status sda6
Command 'env LANG=C cryptsetup status sda6' returned non-zero exit status 4.
Executing: blkid -o value -s TYPE /dev/sda6
Executing: blkid -o value -s TYPE /dev/sda6
Executing: lsblk -n -o LABEL /dev/sda6 | grep -v "^$"
Command 'lsblk -n -o LABEL /dev/sda6 | grep -v "^$"' returned non-zero exit status 1.
Executing: grep /dev/sda6 /proc/mounts | awk '{print $2}'
Executing: mkdir -p /tmp/live-installer-3/sda6; mount --read-only /dev/sda6 /tmp/live-installer-3/sda6
Executing: grep /dev/sda6 /proc/mounts | awk '{print $2}'
Executing: umount -f /dev/sda6
Executing: env LANG=C cryptsetup status sda7
Command 'env LANG=C cryptsetup status sda7' returned non-zero exit status 4.
Executing: blkid -o value -s TYPE /dev/sda7
Executing: blkid -o value -s TYPE /dev/sda7
Executing: lsblk -n -o LABEL /dev/sda7 | grep -v "^$"
Command 'lsblk -n -o LABEL /dev/sda7 | grep -v "^$"' returned non-zero exit status 1.
Executing: grep /dev/sda7 /proc/mounts | awk '{print $2}'
Executing: mkdir -p /tmp/live-installer-3/sda7; mount --read-only /dev/sda7 /tmp/live-installer-3/sda7
Executing: grep /dev/sda7 /proc/mounts | awk '{print $2}'
Executing: umount -f /dev/sda7
Executing: dd bs=512 count=1 if=/dev/sda1 2>/dev/null | strings
Executing: dd bs=512 count=1 if=/dev/sda2 2>/dev/null | strings
Executing: dd bs=512 count=1 if=/dev/sda3 2>/dev/null | strings
Executing: dd bs=512 count=1 if=/dev/sda4 2>/dev/null | strings
Executing: dd bs=512 count=1 if=/dev/sda5 2>/dev/null | strings
Executing: dd bs=512 count=1 if=/dev/sda6 2>/dev/null | strings
Executing: dd bs=512 count=1 if=/dev/sda7 2>/dev/null | strings
========================================================
Screenshot_20200709_092135.png
========================================================

Hit "No"
Fill in fields
Disk without primary partition is not listed

========================================================
Screenshot_20200709_092628.png
========================================================

Repartitioning the disk with a primary ext4 partition shows the disk in live-installer.

The live-installer did not crash.

So, I have updated live-installer-3 which now skips the "No partition table" message if a disk with a primary partition was already found and now also lists disks with only an extended partition (no primary).

To test, start a live session, connect to the internet and run live-installer-3 from the terminal. It should update itself to version 2020.07.09.


SolydXK needs you!
Development | Testing | Translations

transadd
Posts: 24
Joined: 18 Jun 2015 16:55
Location: Colchester Essex uk

Re: SolydK10 installation failing on computer with multiple drives

Postby transadd » 25 Jul 2020 09:03

Arjen Balfoort wrote:
06 Jul 2020 16:45
It might be possible to do something about the error but I will need to recreate the circumstances exactly. Including recreating the error and that might not be possible to do in VB.
Hi
PC 1
sda. windows XP
sdb. windows data
sdc. SolydX 10 and other Linux Distro's and data
sdd data backup

I have installed and ran the original SolydX 10 Xfce on PC with multiple partitions and works it fine

PC 2
sda. SolydX and other Distro's
sdb. Data files misc
sdc. Data video files

When installing SolydX 10.4 again with multiple partitions .

First attempt:
Because I had no internet connection on that day, and checking that the updates could be loaded at a later stage I continued.
There was the following observation.
The installer wanted to format my Data drive sdb as it said there was no partition table. But there was, and and all other distro's had not commented. There was the option not to destroy the data by writing a new table , which I took. NOTE this could be FATAL for a new user by destroying all their data
When installed the system appeared to work.

Second attempt:
Internet connection back to normal.
Installation had no problem with sdb and there was no comment.
The installation disk did not eject on shutdown?

Regards

John


Return to “Installation”

Who is online

Users browsing this forum: Bing [Bot] and 1 guest