New Rolling ISO's available

Tags: #<Tag:0x00007f250d858070> #<Tag:0x00007f250d867f48> #<Tag:0x00007f250d867e80>

i will give it a try have a spare ssd

wont install for me gets to patitioner wont partition ssd

manual partition creating 3 partititions wont work but automatic works

I get that you had problems with partitioning but there is nothing a developer can actually work on in your statement.

Ah, so a user confronted with my statement might justifiably ask, “Well @ben79, how the heck do I get something a developer could work on?”. That, of course, depends on the nature of the problem, but one of the first things developer person will ask for is some kind of logs showing what happened. In this case since it involves an ssd and the Calamares installer they will ask for hardware information, at the least, exactly what make and model of ssd. Then they’ll ask for logs from Calamares installation attempt. Both are easy to do.

There are commands to get way more detailed information about you storage drives but let’s not deal with that unless we need to. To get general hardware information one easy way is with the inxi command. Like this. As regular user:

$ inxi -F

To run that a put the out put in a file you could post here for developers/contributors to read is still very simple:

$ inxi -F > inxi-f.txt

That will create the file: inxi-f.txt (2.3 KB) That would be the file I just created on this computer.

which you post here with the aid of the upload arrow.

Then there is one more step which is to get the logs from the Calamares installer. I’ll describe that in next post.

Actually I’m going to attempt to create a How To for the Resources section for “What to do if you have trouble installing OM Lx”. Maybe I can get that up by tomorrow some time. But it is just basic documentation we need to have.

I thought there was something in wiki about this but did not find it yet. Temporary wiki url is here. Resources list is here.

[grumpy@nvme ~]$ inxi -F 
System:
  Host: nvme Kernel: 5.5.2-desktop-1omv4002 x86_64 bits: 64 
  Desktop: KDE Plasma 5.17.5 Distro: OpenMandrivaLinux 4.2 Argon 
Machine:
  Type: Desktop Mobo: ASRock model: X570 Taichi 
  serial: <root required> UEFI: American Megatrends v: P2.00 
  date: 08/21/2019 
CPU:
  Topology: 8-Core model: AMD Ryzen 7 2700X bits: 64 
  type: MT MCP L2 cache: 4096 KiB 
  Speed: 4075 MHz min/max: 2200/3700 MHz Core speeds (MHz): 
  1: 4048 2: 4079 3: 4096 4: 4092 5: 4016 6: 3775 7: 3767 
  8: 3773 9: 4048 10: 3695 11: 4065 12: 3756 13: 3770 14: 4017 
  15: 3011 16: 4090 
Graphics:
  Device-1: AMD Ellesmere [Radeon RX 
  470/480/570/570X/580/580X/590] 
  driver: amdgpu v: kernel 
  Display: x11 server: OpenMandriva X.org 1.20.7 driver: amdgpu 
  FAILED: ati unloaded: fbdev,modesetting,vesa 
  resolution: 2560x1080~60Hz 
  OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.36.0 
  5.5.2-desktop-1omv4002 LLVM 9.0.1) 
  v: 4.5 Mesa 19.3.4 
Audio:
  Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 
  570/580/590] 
  driver: snd_hda_intel 
  Device-2: AMD Family 17h HD Audio driver: snd_hda_intel 
  Device-3: Logitech Logitech BRIO type: USB 
  driver: hid-generic,snd-usb-audio,usbhid,uvcvideo 
  Sound Server: ALSA v: k5.5.2-desktop-1omv4002 
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi 
  IF: wlp6s0 state: up mac: 3c:f0:11:da:f7:dc 
  Device-2: Intel I211 Gigabit Network driver: igb 
  IF: enp8s0 state: down mac: 70:85:c2:d6:78:6c 
Drives:
  Local Storage: total: 1.58 TiB used: 29.45 GiB (1.8%) 
  ID-1: /dev/nvme0n1 vendor: Gigabyte model: GP-ASACNE2512GTTDR 
  size: 476.94 GiB 
  ID-2: /dev/sda vendor: Intel model: SSDSC2BW240A4 
  size: 223.57 GiB 
  ID-3: /dev/sdb vendor: Intel model: SSDSC2BW240A4 
  size: 223.57 GiB 
  ID-4: /dev/sdc vendor: Samsung model: SSD 840 EVO 250GB 
  size: 232.89 GiB 
  ID-5: /dev/sdd vendor: Samsung model: SSD 850 EVO 250GB 
  size: 232.89 GiB 
  ID-6: /dev/sde vendor: Kingston model: SA400S37240G 
  size: 223.57 GiB 
Partition:
  ID-1: / size: 47.81 GiB used: 8.80 GiB (18.4%) fs: ext4 
  dev: /dev/nvme0n1p3 
  ID-2: /home size: 185.17 GiB used: 20.65 GiB (11.2%) fs: ext4 
  dev: /dev/nvme0n1p4 
Sensors:
  System Temperatures: cpu: 50.2 C mobo: N/A gpu: amdgpu 
  temp: 42 C 
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 935 
Info:
  Processes: 333 Uptime: 2m Memory: 62.75 GiB 
  used: 1.32 GiB (2.1%) Shell: bash inxi: 3.0.37 

.
@ben79 hi the ssd i was trying to install was sdd samsung,I used tha manual partitioner first making 3 partitiions uefi 512 mb, root parition 50000 mb,home rest of disk tried fat 32 and fat 16 for uefi patition bur no luck as soon as I use automatic partitioner it installs fine
regards Ron

1 Like

.

System:
  Host: ron-tobefilledbyoem Kernel: 5.5.2-desktop-1omv4002 x86_64 
  bits: 64 Desktop: KDE Plasma 5.17.5 
  Distro: OpenMandrivaLinux 4.1 Mercury 
Machine:
  Type: Desktop Mobo: ASRock model: X570 Taichi 
  serial: <root required> UEFI: American Megatrends v: P2.00 
  date: 08/21/2019 
CPU:
  Topology: 8-Core model: AMD Ryzen 7 2700X bits: 64 type: MT MCP 
  L2 cache: 4096 KiB 
  Speed: 4072 MHz min/max: 2200/3700 MHz Core speeds (MHz): 
  1: 4021 2: 4059 3: 4048 4: 4060 5: 4042 6: 4089 7: 4034 8: 4050 
  9: 4075 10: 4041 11: 4058 12: 4049 13: 4068 14: 4026 15: 4047 
  16: 4039 
Graphics:
  Device-1: AMD Ellesmere [Radeon RX 
  470/480/570/570X/580/580X/590] 
  driver: amdgpu v: kernel 
  Display: x11 server: OpenMandriva X.org 1.20.7 driver: amdgpu 
  FAILED: ati unloaded: fbdev,modesetting,vesa 
  resolution: 2560x1080~60Hz 
  OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.36.0 
  5.5.2-desktop-1omv4002 LLVM 9.0.1) 
  v: 4.5 Mesa 19.3.4 
Audio:
  Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 
  570/580/590] 
  driver: snd_hda_intel 
  Device-2: AMD Family 17h HD Audio driver: snd_hda_intel 
  Device-3: Logitech Logitech BRIO type: USB 
  driver: hid-generic,snd-usb-audio,usbhid,uvcvideo 
  Sound Server: ALSA v: k5.5.2-desktop-1omv4002 
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi 
  IF: wlp6s0 state: up mac: 3c:f0:11:da:f7:dc 
  Device-2: Intel I211 Gigabit Network driver: igb 
  IF: enp8s0 state: down mac: 70:85:c2:d6:78:6c 
Drives:
  Local Storage: total: 1.58 TiB used: 8.51 GiB (0.5%) 
  ID-1: /dev/nvme0n1 vendor: Gigabyte model: GP-ASACNE2512GTTDR 
  size: 476.94 GiB 
  ID-2: /dev/sda vendor: Intel model: SSDSC2BW240A4 
  size: 223.57 GiB 
  ID-3: /dev/sdb vendor: Intel model: SSDSC2BW240A4 
  size: 223.57 GiB 
  ID-4: /dev/sdc vendor: Samsung model: SSD 840 EVO 250GB 
  size: 232.89 GiB 
  ID-5: /dev/sdd vendor: Samsung model: SSD 850 EVO 250GB 
  size: 232.89 GiB 
  ID-6: /dev/sde vendor: Kingston model: SA400S37240G 
  size: 223.57 GiB 
Partition:
  ID-1: / size: 227.94 GiB used: 8.51 GiB (3.7%) fs: ext4 
  dev: /dev/sdd2 
Sensors:
  System Temperatures: cpu: 48.6 C mobo: N/A gpu: amdgpu 
  temp: 39 C 
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 928 
Info:
  Processes: 299 Uptime: 7m Memory: 62.75 GiB 
  used: 965.5 MiB (1.5%) Shell: bash inxi: 3.0.37

this is the one i had trouble today

1 Like

Post-edit: This issue really needs to have a proper bug report. And such a bug report needs to be filed by the person with the issue if you would be so kind. Developers do not and will not see every issue reported in a forum.

OK, thanks for the info. First was there already an existing /boot/efi partition on another drive? Not sure, but I recall that calamares installer won’t do that it will insist on using the existing /boot/efi because system will not allow more than one partition with esp, and boot flags.

Otherwise I am not aware of any reason why there should be a partitioning problem on Samsung 840 or 850 EVO drives. I don’t have either one of those. So best I can do to test is to try to do an install on empty space on an existing ssd on a computer that has an existing /boot/efi and see if there is any difficulty creating new partitions. (First attempt will be on a Sabrent Rocket 4.0 nvme ssd as that is what I have.) The difference form my normal installs is that normally on hardware I use existing partitions.

all of my linux operating systems have their own boot/uefi parition and there now 6 on this computer,I really think theres a bug in the installer i will post a screenshot of the ssd with the new openmandriva on it


just a thought i make my uefi partitions 512 mb i see the auto installer only makes the uefi partition 300 mb maybe i will retest and see

just tried to install manually creating partitions uefi,root and home crashes at installer wont make partitions

I am not sure what I said about /boot/efi partitions is correct. Otherwise I need to get to a test situation before I can say more about this. Other than that this issue needs a bug report.

Uh, oh, I just realized I’m not asking the first most basic question. @rbrick49 could you post the actual exact error you are getting?

So far I have tried this test basic set up: One ssd (both are nvme ssd) has 4 installed operating systems and existing /boot/efi partition in the first partition on that drive. The other drive was completely empty:

Then I used manual partitioning and partitioned the empty drive with a new /boot/efi, as well as /, and /home partitions:

and as I thought installation fails with a partitioning error. Note which partition it fails on.:

As I thought either calamares or more likely the partitioner (parted?) OM uses simply will not create a new /boot/efi with correct flags if there is an existing one. Whether that is or is not a bug other people can argue but I’m fairly certain this is known and expected behavior in OM Lx. @abucodonosor could confirm this if he sees this.

To me it seems far simpler to have all operating systems booting from the same bootloader. One of the principle reasons grub2 was created was to make that easier for users. UEFI was created in part to have virtually unlimited partitions, all primary partitions. Hence the combination of the two today in Linux. And even if one needs to use multiple boot loaders you can have that all in one /boot/efi and change which file it uses from your BIOS.

A /boot/efi partition does not have much in it really, they are mostly empty even at 300MB. On a multi-boot box mine shows 509 of 511 Mb free only 2 Mb used.

So there is more than enough room for more operating systems.

@ben79
ben i have openmandrive on an nvme ssd and it has installed with the 3 partitions so i dont know what the problem is,I wont be putting in a bug report as i feel a bit crook today thanks fot the help this far
regards Ron

OK, there is no problem,

I was just trying to figure out the why your partitioning initially failed. And made the dumbest mistake of not asking for the actual error message first. Basically so we can write a better partitioning/installation How To. So if you ever see that same error again please take a screen shot and post it here or in a pm to me.

@rbrick49 your time and help has helped me to realize some additional things that need to be covered in the forth coming How To. Thanks.

just found something out as we know the openmandriva partition editor wont let me partition the disk with 3 partitions but manjaro kde partition editor will strange so someting has gone wrong with openmandriva partition editor from when 4.1 got released a few weeks ago and the laterst rolling release a few days ago

yes getting the same failure as you are getting on your machine
but auto install makes a uefi partition and root partition but no
home partition

Ron

Talking to a developer the installer will create a new ESP (EFI System Partition) with auto partitioning. But auto partitioning will not create a /home partition. Currently it will not create a new ESP in manual partitioning. At least not based on tests I have done.

I’m attempting to write an explanation for why this is not allowed here. But the explanation is a work in progress as I learn more myself.