I just reinstalled and the installer got a critical error and started a desktop so I could report but I forgot the name of the tool. I have seen this before. Could it be that Grub II bootloader doesn't like SSD's or specifically the Samsung 860 EVO's with V-NAND technology? Amazon.com website said they were good with Linux.
-
Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.
http://www.kubuntu.org/getkubuntu -
I am running TWO Samsung 860 EVO 500Gb SSD's with NO problems at all. When you booted into the ISO to install it did the checksummng routine complete its examination of the ISO and found no errors?Originally posted by steve7233 View Post
I'm running an 8 year old Acer Aspire V3-771G laptop with Nvidia GT 650M as the GUP and an Intel i7 CPU, along with 16 GB of RAM. I have a 3rd spinner HD setting in a CDROM HDCADDY, but its sector count is on its last legs. When it goes it will be replaced with another 860 EVO 500GB, or maybe a 1TB, if the price is low enough.
How old is your machine and what is your hardware?"A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
– John F. Kennedy, February 26, 1962. -
I used netbootin to use USB install. It is from day 1 of the release so it might be a known issue. If it was fixed then you would think the updates would have squashed the bug. I don't know for sure how old the computer is but the HD's were all just replaced with 1 to 4 TB SSD's, All the same brand and model. I don't remember if I checked the checksum. I have used the installer before. Sometimes it fails the Grub II install and other times it works. Probably some kind of hardware fluke. I am using BRTFS. Last time I chose EXT4 for /.Originally posted by GreyGeek View PostJust to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.
http://www.kubuntu.org/getkubuntuComment
-
I tried again and the installer crashed again. The same error.Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.
http://www.kubuntu.org/getkubuntuComment
-
I am going to try making an ext4 partition just for Grub II. How big should I make it?Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.
http://www.kubuntu.org/getkubuntuComment
-
I've had problems with Unetbootin writing to USB sticks so I switched to Balena Etcher. Never had a duff write since!Constant change is here to stay!Comment
-
I agree, Etcher is the easiest and most reliable USB flasher I have ever used. It takes very little time and verifies the ISO after it's finished. I've used both Unetbootin and the native Kubuntu flasher, and neither of them are as easy and reliable as Etcher.Comment
-
What is the name of its repository?Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.
http://www.kubuntu.org/getkubuntuComment
-
-
I justried to install grub manually.
What does that cow line mean?? Something BTRFS?Code:kubuntu@kubuntu:~$ sudo grub-install /dev/sda Installing for i386-pc platform. grub-install: error: failed to get canonical path of `/cow'. kubuntu@kubuntu:~$
Shouldn't that 64 bit stuff?Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.
http://www.kubuntu.org/getkubuntuComment
-
That's the BIOS/MBR grub, with a 32 bit boot. If you boot in UEFI mode, that won't work. I did this a few weeks ago, trying to install to an old disc with the MBR partition table. The grub packages are confusing, some of them are set to conflict with others, and some not.Originally posted by steve7233 View PostRegards, John LittleComment
-
After googling a bit I started to think it might be something like that. Why didn't the installer sort it out? I bet 20.04 will have the same problem.Originally posted by jlittle View PostJust to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.
http://www.kubuntu.org/getkubuntuComment
-
I found this cmd while googling.
I must have a different problem.Code:kubuntu@kubuntu:~$ test -d /sys/firmware/efi && echo efi || echo bios bios kubuntu@kubuntu:~$
Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.
http://www.kubuntu.org/getkubuntuComment
-
I think I found the problem. A possible regressed bug.
https://bugs.launchpad.net/ubuntu/+s...2/+bug/1059827
Now to solve it??Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.
http://www.kubuntu.org/getkubuntuComment
-
Do you want a BIOS/MBR system? That would be appropriate for only old hardware that hasn't got a UEFI (or used by old change-resistant holdovers like some in KFN I suppose).
It's very easy when booting install media to boot in legacy mode inadvertently, and thus install a BIOS/MBR grub, even on a UEFI system. I was suggesting that this is what's happened, and it's causing you trouble. Maybe you know all about this, but having a BIOS/MBR install, as evidenced by "Installing for i386-pc platform", looks odd and likely to cause trouble. The right way to boot the install media to get a UEFI install depends on the computer, specifically the motherboard.Regards, John LittleComment
Comment