(old)Puppy Linux Discussion Forum

BarryK wrote:
OK, give me a bit of time to think what you can do to investigate this. pressed for time right now. probably this evening will take a look at it.

EDIT:
OK, I think maybe I know where the problem is. Run easypup again, and click on the 'initrd' for your easyos installation, to open it up.

Click on the 'init' script in the initrd, to edit it. At line 616 you will see this code:

Code: Select all

 if [ "${WKG_FS}" == "ext4" ];then #200621 change journal commit interval from 5 to 30...
  #rw,relatime,data=ordered are the defaults anyway...
  mount -t ${WKG_FS} -o commit=30,rw,relatime,data=ordered /dev/$WKG_DEV /mnt/$WKG_DEV
 else
  mount -t ${WKG_FS} /dev/${WKG_DEV} /mnt/${WKG_DEV}
 fi
 [ $? -ne 0 ] && err_exit "Unable to mount working-partition ${WKG_DEV}"

It seems that in your case, the -o options above, is causing the problem. I don't know why, it worked for me.

Anyway, just delete all of "-o commit=30,rw,relatime,data=ordered", save, exit, click on 'initrd' again to update it, then see if easyos boots.

Terry H wrote:

BarryK wrote:
OK, give me a bit of time to think what you can do to investigate this. pressed for time right now. probably this evening will take a look at it.

EDIT:
OK, I think maybe I know where the problem is. Run easypup again, and click on the 'initrd' for your easyos installation, to open it up.

Click on the 'init' script in the initrd, to edit it. At line 616 you will see this code:

Code: Select all

 if [ "${WKG_FS}" == "ext4" ];then #200621 change journal commit interval from 5 to 30...
  #rw,relatime,data=ordered are the defaults anyway...
  mount -t ${WKG_FS} -o commit=30,rw,relatime,data=ordered /dev/$WKG_DEV /mnt/$WKG_DEV
 else
  mount -t ${WKG_FS} /dev/${WKG_DEV} /mnt/${WKG_DEV}
 fi
 [ $? -ne 0 ] && err_exit "Unable to mount working-partition ${WKG_DEV}"

It seems that in your case, the -o options above, is causing the problem. I don't know why, it worked for me.

Anyway, just delete all of "-o commit=30,rw,relatime,data=ordered", save, exit, click on 'initrd' again to update it, then see if easyos boots.

Success, doing as advised, easyOS2.3.2 now boots successfully. Thanks for the quick response and instructions.

  mount -t ${WKG_FS} -o commit=30 /dev/$WKG_DEV /mnt/$WKG_DEV

# dumpe2fs /dev/nvme1n1p4 | grep -i "Filesystem features:"
dumpe2fs 1.44.5 (15-Dec-2018)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg encrypt sparse_super large_file huge_file dir_nlink extra_isize metadata_csum

  mount -t ${WKG_FS} -o commit=30 /dev/$WKG_DEV /mnt/$WKG_DEV 2>/dev/null
 [ $? -ne 0 ] && mount -t ${WKG_FS} /dev/$WKG_DEV /mnt/$WKG_DEV

scsijon wrote:The Adapter card you got is a pci-e X16 interface card usually used for adding a first nvme or a second nvme to allow for raid 0 and 1 and therefore automaps to match your existing nvme if you have one installed.

As you already had a nvme installed and didn't want the raid function, you should have got a X4 card which would have assigned a different configuration and looks like https://www.scorptec.com.au/product/Con ... ORICO-PSM2 and used the x4 slot.

You should still be able to separate them in the 'bios' firmware though, if your firmware allows two independant nvme 'drives'. You may need to update it though.

hansi wrote:mount: mounting /dev/sdb2 on mount /mnt/sdb2 failed invalid argument
ERROR: Unable to mount working partition sdb2...

I had the same boot failure after my first upgrade of easyos ...
Until now now i always did an new install, but not this time (want to preserve my adjustments.

Thanks for the quick solution, BK

OscarTalks wrote:

alfons wrote:BCRYPT
The program bcrypt (Menu -> Personal -> "Bcrypt file encryption") has not been working for a long time. I don't know if this is still useful in EasyOS

I think this is because a weakness/vulnerability in bcrypt was reported as a bug and Debian patched it to disable encryption but leave it available (with a warning) in case anyone needed it to decrypt anything.
If you want it to encrypt as well you can just compile the source and substitute the executable, bearing in mind that the "bug" exists.
This reply was posted from NetSurf 3.10 in EasyOS 2.3.2

BarryK wrote:

scsijon wrote:The Adapter card you got is a pci-e X16 interface card usually used for adding a first nvme or a second nvme to allow for raid 0 and 1 and therefore automaps to match your existing nvme if you have one installed.

As you already had a nvme installed and didn't want the raid function, you should have got a X4 card which would have assigned a different configuration and looks like https://www.scorptec.com.au/product/Con ... ORICO-PSM2 and used the x4 slot.

You should still be able to separate them in the 'bios' firmware though, if your firmware allows two independant nvme 'drives'. You may need to update it though.

I will need to have another look at that adapter card. it seemed that most of the pins are not used, only those at one end go to the m.2 socket.

I couldn't see anything in the uefi bios for separating them.
The uefi setup doesn't even see the nvme drive plugged into the adapter card, so I cannot boot from it. I tried, with an esp fat32 partition in that drive, but it isn't seen at bootup.

After bootup, both are seen, and everything is working fine.

ras wrote:Nice,

I will remake my dedicated easyos "install/repair" thumbdrive when you come out with refind included in the next version release.

Do you have a link to a resource with boot codes for refind? I might want to migrate from grub 4dos. I have various puppys and dogs in the kennel as frugal installs on ext partitions already.

BarryK wrote:Android connectivity fixed:

https://bkhome.org/news/202007/android- ... fixed.html