Puppy Linux Discussion Forum

Hi all,
I have been using EasyOS from time to time. I have it installed within a partition with Arch Linux, and have noticed that each time I reboot EasyOS the hard drive is a bit messed up, similar to when you don't shut down a pc properly... e.g. getting "clearing orphaned inodes" messages at boot up. My files hasnt been damaged, but that kind of worries me a bit.
Has someone had a similar issue? how can it be solved?

Hi hinojojojo,

the 'orphaned' problem existed in older EasyOS versions.

Downloading and installing the newest version of EasyOS 'EasyOS-Dunfell 2.7.2' will be my advise to you.

Thanks for your answer FeodorF
Just downloaded and installed Dunfell most recent version (2.7.2) also within the same partition but I still have the same issue there too. Is this an issue of EasyOS? or could it be something in my grub configuration?
Here is the grub config I am using for it, which is basically the same I use for puppies (although I dont have this issue with other puppies in the same partition). I installed the easyOS within the /easosDun/ folder at sda3
menuentry "easyOS Dunfell"{
set root='(hd0,3)'
search --no-floppy --fs-uuid --set a8777435-c45e-419b-be3a-6db726efdaf9
linux /easyosDun/vmlinuz pmedia=atahd psubdir=easyosDun
initrd /easyosDun/initrd
}

The following picture shows how a 'frugal' installation looks like - also called an installation to a partition.
I used EasyOS Dunfell 2.7.2 for it.

hinojojojo wrote: ↑Mon Apr 26, 2021 12:22 am

Thanks for your answer FeodorF
Just downloaded and installed Dunfell most recent version (2.7.2) also within the same partition but I still have the same issue there too. Is this an issue of EasyOS? or could it be something in my grub configuration?
Here is the grub config I am using for it, which is basically the same I use for puppies (although I dont have this issue with other puppies in the same partition). I installed the easyOS within the /easosDun/ folder at sda3
menuentry "easyOS Dunfell"{
set root='(hd0,3)'
search --no-floppy --fs-uuid --set a8777435-c45e-419b-be3a-6db726efdaf9
linux /easyosDun/vmlinuz pmedia=atahd psubdir=easyosDun
initrd /easyosDun/initrd
}

Note that Easy does not recognize "pmedia=atahd psubdir=easyosDun". Instead, there is a 'BOOT_SPECS' file inside 'initrd' that has everything needed for Easy to know where the boot and working partitions and folders are located, for example:

BOOT_UUID='21D3-5A8C'
BOOT_DIR=''
WKG_UUID='9a9f023c-a130-11eb-80f3-287fcfeb4376'
WKG_DIR='easyos/'

What filesystem is your sda3? It is best to use ext4.

2 things I note pertaining to the prior post, above.

1. Easy does not abhere to GRUB2

2. Puppy Linux uses different boot feature & parms. It has SAVESPEC file in recent creates. For example

   Code: Select all

   SS_ID='Linux'
   SS_DIR='/Sessions'
   SS_MEDIA='atahd'

Though similar in function, Easy does it differently.

Hope this is helpful in some small way.