EasyOS Scarthgap-series version 6.6.3

[n00b]

The string of errors was all about 'cp can't preserve ownership .... ' related to the .sfs.

You could use gnome disk utility (gnome disks) to view the SMART Data of the SSD.

[measter]

You could use gnome disk utility (gnome disks) to view the SMART Data of the SSD.

There's still a lot of confusion on my part about why things are 'being so difficult' but I don't think it is the fault of the ssd/s.

I have a fair amount of good news; but due to my windiness I'll give some backstory; all related to EasyOS one way or another. I have two HP Compaq 6005 SFF desktops and two ssd/s, one in each. One of them still has a working hdd spinner, the other does not, so on 'the other' the ssd is the first and only hdd. We'll let the one I've been talking about earlier be #1 and the current msg involves both #1 & #2 which #2 is the one w/ only the ssd.

On that machine, the bios boot menu shows the ssd, but not on #1. On that machine #2, I can now successfully boot a ventoy install from the bios boot menu. Now for the progress on 'our' #1 we've been discussing earlier. The ssd now has a linux mint on its 1st partition, which I boot from the optical PBM6. That similar earlier install lost its accessibility, since reinstalled; couldn't fix what I did to the boot manager w/ limine. I believe the next Easy part is true so far, but I've been disappointed before at apparent success which didn't prove to be true in the longer run. On the ssd's 2nd part is/was first the easyos dir and 3 files. After all the confusion which preceded this, I've learned how to deal w/ what has been happening by trial and error.

When I copy, say, the easy.img from a usb hdd storage on #1, I cannot paste it onto the ssd part w/o elevating my privileges, and I don't know why that is. This, the privilege elevation, gives the .img very restricted ownership and permissions; likewise subsequent mounting the img to copy the easyos dir & files causes that dir/files to similarly have the same root restrictions. Then, if I would use a ventoy usb F6 to access the easyos, it fails.

Now I've learned how to fix the owner/permissions problem on the easyos dir/files and I can successfully ventoy F6 boot the Easy 663, which I'm typing here now. Presumably I'll be able to save on the ssd part and everything will be wonderful.

[measter]

Presumably I'll be able to save on the ssd part and everything will be wonderful.

Since easy on the ssd doesn't save anything but what has been saved in files, I'm putting it on the back burner for now. I've written the latest Bookworm pup to a 1G USB, done a frugal install to the ext4 space I reserved for Easy and it saves its settings as expected in an .sfs and boots w/ the settings.

[BarryK]

Just a note, there has been some EasyOS activity post-6.6.3, despite my current involvement in a new custom trike project:

"Fix orange ball install as root"
https://bkhome.org/news/202503/fix-oran ... -root.html

"Fix resize partition on NVME drive"
https://bkhome.org/news/202502/fix-resi ... drive.html

These apply to Daedalus also.

[BarryK]

Another fix:

viewtopic.php?t=13874

[tammi806]

Perhaps worth mentioning when I powered up this desktop which had been not used for a bit it went to the install screen where it wanted me to choose the keyboard language.

I did a hard power off and then powered up again where the same thing occurred so I chose my key board language and the chose #2 choice where I booted from last working saved and all returned to normal.

I then did an upgrade / update from Scarthgap 6.6.1 version to Scarthgap 6.6.3 version and all went without a hitch and everything I've used at this point has worked without issues.

[BarryK]

Perhaps worth mentioning when I powered up this desktop which had been not used for a bit it went to the install screen where it wanted me to choose the keyboard language.

It will do that if a change in hardware is detected. Maybe you changed the keyboard?

EasyOS has "hardware profiling", for booting up a usb drive on different computers.
If a hardware change is detected, that Easy thinks is connected with keyboard interface, then you will be asked to choose keyboard layout.

[tammi806]

Perhaps worth mentioning when I powered up this desktop which had been not used for a bit it went to the install screen where it wanted me to choose the keyboard language.

It will do that if a change in hardware is detected. Maybe you changed the keyboard?

EasyOS has "hardware profiling", for booting up a usb drive on different computers.
If a hardware change is detected, that Easy thinks is connected with keyboard interface, then you will be asked to choose keyboard layout.

Okay i bet because I use my USB flash drives with Easy OS on them on different computers I have that that is what happened interesting and I would have never thought of that but it makes sense since it profiles hardware.

Thanks @BarryK