** Description changed: See this Reddit thread for reference: https://www.reddit.com/r/linuxmint/comments/1oyhl0o/critical_install_error_what_do/ ...and this thread on the Linux Mint forum: https://forums.linuxmint.com/viewtopic.php?p=2708861#p2708861 linux mint GitHub bug report I created before this: https://github.com/inuxmint/cinnamon/issues/13203 (I thought the GitHub for Linux Mint was the right place to post it. Apparently it wasn't as the Ubiquity installer has this separate hub) The most noteworthy pieces of information have been added here: https://forums.linuxmint.com/viewtopic.php?t=457750 I was told to report this here. - I tried to install Linux Mint on an old DELL laptop of mine (probably - with this data sheet. (DELL Inspiron 14 7437) + I tried to install Linux Mint on an old DELL Inspiron 14 7437 laptop. This pc was released when SSDs started to become mainstream. It contains a very weird hybrid hard drive that has a 500 GB HDD and a 32 GB SSD section. Hard Drive 0: Info => https://www.disctech.com/Seagate-ST500LT032-500GB-SATA-Hard-Drive Hard Drive 1: Info => https://www.disctech.com/Lite-On-LMS-32L6M-717771-001-1.8-in-32GB-6gbps-MLC-mSATA-SSD System: Info => https://geizhals.de/dell-inspiron-14-7437-52011807-a1077854.html The laptop had Windows 10 installed before I tried to put the new - install on it. I used the newest version of Ventoy (1.1.07) to put the + install on it. I used the newest 1.1.07 version of Ventoy to put the newest Mint .iso on an 16 GB Kingston Data Traveler 2.0 USB stick as boot medium. - The install program seemingly didn't correctly detect the harddrive or understood it as a single medium. When I ran the install, it had somehow seemingly erased both sides of the internald harddrive and therefore automatically selected the USB stick as the harddrive instead, but didn't tell me that in the install program (The install program should probably tell people what the boot install software wants to install on) on the default option (= no custom partition selected). It then proceeded to try to install Linux Mint on the very same stick the install software was stored upon. Or at least what I think what happened. At least it gave me the error message you can see as the first picture in the Reddit thread. - After that, nothing worked. The pc wouldn't boot into the Linux Mint OS and I couldn't boot from the stick again. The stick was seemingly broken or wiped as it wouldn't show as a hard drive anymore on my parallelly used Win11 test/control laptop. + The install program seemingly didn't correctly detect any part of the + harddrive(s). + + When I ran the install, it had somehow seemingly erased both sides of + the internal harddrive and therefore automatically selected the USB + stick as the harddrive instead, but didn't tell me that in the install + program. + + The install program should probably tell people what the boot install + software wants to install on on the default option (= no custom + partition selected). + + It then proceeded to try to install Linux Mint on the very same stick + the install software was stored upon. Or at least what I think what + happened. At least it gave me the error message you can see as the first + picture in the Reddit thread. + + After that, nothing worked. The pc wouldn't boot into the Linux Mint OS + and I couldn't boot from the stick again. The stick was seemingly broken + or wiped as it wouldn't show as a hard drive anymore on my parallely + used Win11 test/control laptop. After downloading another .iso of linux mint and Ventoy on my test/control laptop, I found out that the stick was indeed not broken at all, but that the ISO was just erased. After reconfiguring the USB stick with Ventoy and the new .iso, I was able to boot linux mint from the stick on the old laptop again. This time I selected the custom ROM partition option to see what the program was suggesting to install upon. This was when I realized that the installation program tries to install linux mint on the very same stick the iso is stored upon, because it can't really detect the harddrive. - My best guess is that it's because the harddrive is such a weird piece of hardware, but I really don't know. - This is why I came here. I'm at my wits end. + My best guess is that it's because the harddrive is such a weird piece + of hardware, but I really don't know. I only have access to this laptop on the weekends so I can't post the syslog and partman files here.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2131958 Title: Installer doesn't seem to recogneize hybrid HDD + SSD harddrive - installs on itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2131958/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
