buntu 22 Desktop - specifically 22.04 - the most current one that any newbie downloads when they go to the Ubuntu website and click on Download Ubuntu
I tried the server install but that has the same issue it is just a lot harder to open a separate terminal session and run the various commands to see the problem. I don't have the contents of /var/log/installer/media-info since it took probably 6-8 install attempts and trying an enormous number of things I could google up regarding fakeraid cards all of which were fruitless. To figure out what I posted here represents probably 20 hours of work. I really needed the server so I just couldn't spend anymore time on it. I did end up pulling the card and using a different card and hard disk setup. (a Marvell fakeraid card which has even worse bugs then the LSI one does among them that only a single disk in channel 1 is recognized) The LSI card and it's disks are sitting in a box and if there is any real interest in solving this in a few weeks I can setup a test server devoted to a test bed. Incidentally this was also on a raidset configured raid5. It appears in recent dmraids that the dmraid45 binary has been subsumed into the dmraid program. Yet another bug with it with this LSI card is that the dmraid command claims it only supports raid 0, 1 and 10 with the lsi fakeraids yet in actual practice it supports raid 0 1 and 5 but raid 10 it does not work with since it badly miscalculates things. But that is another bug for another time. I am positive that somewhere around Ubuntu 16 that installation on a booting fakeraid set worked and the installer did properly copy the dmraid loadable kernel modules into the minikernel that grub boots, and initramfs properly assembled the array and found root and kicked off boot. I know a lot of people setup mdadm bootable arrays but that only works with fakeraid cards that can designate a physical disk as a boot disk and designate that there is no created array. While the LSI card can designate it's disks as just a bunch of dumb disks, it cannot designate any of them as bootable unless a raid configuration is created. The lsi megaraid card cannot, so when POST attempts to transfer BIOS control to a hard disk, it can't. One last thing with these cards like the LSI is that they write the raid config to the end of the disk and if the linux installer uses GPT it trashes the fakeraid configuration on the card. It seems that current versions of the Ubuntu installer just automatically use GPT instead of MBR if you select "erase disk and install ubuntu" even if /dev/mapper is present which is yet another bug. The installer should check for the presense of a fakeraid card by looking for a loaded dmraid and /dev/mapper/xxxx files and if it sees those it should offer the option of disklabelling msdos, deliberately shrink the automatically created partition so it can't possibly trash the fakeraid config, and in general be kinder to animals and plants instead of just trashing the msdos disklabel and automatically converting it to GPT. That's jerk behavior. GPT is only needed for giant disks and in these days of SSD's who in the heck is running a 4TB SSD boot disk??? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028471 Title: dmraid modules not properly loaded during installation Status in linux package in Ubuntu: New Bug description: There are actually 2 problems with this one. First is that although Ubuntu 22 Desktop does indeed see FakeRAID cards, it does a partition probe before dmraid sets up the array. On a system with a LSI Megaraid (older card, fakeraid) card I created the RAID array in the BIOS of the card then booted the desktop install. Then ran Live. At the Live desktop at the terminal prompt /dev/mapper/ddf1_4c5349202020202020000055000000000004711471100001450 was visible however fdisk -l on that device showed an actual disklabel (msdos partition table) existed along with a partition #1 completely filling the disk. Executing partprobe /dev/mapper/ddf1_4c5349202020202020000055000000000004711471100001450 created the /dev/mapper/ddf1_4c5349202020202020000055000000000004711471100001450 /dev/mapper/ddf1_4c5349202020202020000055000000000004711471100001450p1 entries with the p1 entry lined to /dev/dm-1 So I then ran the installer and at the disk screen changed grub install to /dev/mapper/ddf1_4c5349202020202020000055000000000004711471100001450 instead of /dev/sda and then I installed Ubuntu on the now visible first partition However after the install completed the system attempted to boot and errored out at an initramfs prompt with: ALERT! UUID=68ca7f1a-c462-4f7c-9657-05d3ad04e4ee does not exists. Dropping to a shell! I ran the following command and got this output: dmraid -ay 165.190010] device-mapper: table: 253:0: raid: unknown target type ERROR: device-mapper target type "raid" is not in the kernel: RAID set "ddf1_4c5349202020202020000055000000000004711471100001450" was not activated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
