Puppy Linux Discussion Forum

UPDATE: I was able to download an iso file for the firmware update, burn to cd, boot cd, update the firmware.
Fossa booted faster than ever.
Thanks for all the help.

The drive in question is a M4-CT128M4SSD2 Firmware version 000f
G smart control reports "This drive may hang after 5184 hours of power-on time:"
This is a bug in the original firmware.
There is a firmware update available for windows and android but no update for Linux.

Folks have tried virtual machine and wine without success.
Do you think if I removed the drive and connected it externally to a win machine I would be able to update the firmware?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Original post:

This morning while booting it appears that file check ran and couldn't access the main drive,(sda). I booted to my old drive to post this in my copy of Thar I had on my previous computer, (sdb) before trying to boot again. Here is what the screen looked like when it finally stopped scrolling.

My best guess is that the ssd, (sda)has become corrupted or possibly I have a bad connection / cable.

Should I try and access it from this drive and run e2fsck on it or pull it and hook it up via usb? I have an adapter.

Thoughts? Thanks.

Should I try and access it from this drive and run e2fsck on it

If you are asking to boot with the Puppy version on another drive and checking sda with e2fsck running from it.

Yes.

If it still gives any errors what are they?

Is sda an internal drive or a USB connected SSD drive?

If USB connected.

Do not have any other USB drives plugged in when you boot.

Fossapup64 has a bug about not booting, if other USB drives are plugged in.

How is Fossapup64 installed on the SSD?
Frugal?
What boot loader boots it?

Both are internal ssd drives. I will run e2fsck on sda and see what I get.
Foassapup 9.5 64-(Frugal) Storage Internal, sda- ssd 128GB Fossa - sdb- ssd-256GB Tahr, which I am running on now.

e2fsck -p /dev/sda2 /dev/sda2 has unsupported feature(s): metadata_csum
e2fsck: Get a newer version of e2fsck!

Perhaps wrong syntax?

I am thinking of using gparted to check the disc?

Edit: G-smart control reports no errors on the disc. Not sure where to go from here.

What is the format of these partitions?
Fat32, ntfs, ext 2, 3, or 4?

sda1 is fat32 - boot, sda 2 and 3 are ext4
Gparted lists "check" as available for each partition. If I remember, back in the win days I repaired a copy of xp on ntfs with gparted.

@bigpup I was able to copy my fossa64 save file from that drive to another with no errors reported. That is a plus.
Should I try gparted to check the filesystem on the fossa partition?

More info. Looks like gparted doesn't recognize the partition.

Guessing now the drive is failing or still has a bad connection, or possibly the gifted motherboard is also failing.I am amazed though that from my old os, on another drive, I can still read and copy files from it.

peppyy wrote: ↑Sun Oct 16, 2022 11:29 pm

More info. Looks like gparted doesn't recognize the partition.
gparted-try.jpg
Guessing now the drive is failing or still has a bad connection, or possibly the gifted motherboard is also failing.I am amazed though that from my old os, on another drive, I can still read and copy files from it.

Well, if you have a backup of your savefile (and possibly all your working on all partitions), you could still try to locate badblocks and create partitions such a way that they don't come over most of the badblocks. But I have done it on a HDD not SSD, so no idea if it will work.

By the way, back when my computer first reported read-only filesystem, I partially knew my drive was failing. I ran badblocks on it directly (which I don't think is appreciated) and found over 3000 badblocks on an hdd of 300gb. I couldn't get my system booting till I tried doing the above method.

Think I might have figured it out. See first post.

peppyy wrote: ↑Sat Oct 15, 2022 11:34 am

by peppyy » Sat Oct 15, 2022 7:34 am

UPDATE:
The drive in question is a M4-CT128M4SSD2 Firmware version 000f
G smart control reports "This drive may hang after 5184 hours of power-on time:"
This is a bug in the original firmware.
There is a firmware update available for windows and android but no update for Linux.

Folks have tried virtual machine and wine without success.
Do you think if I removed the drive and connected it externally to a win machine I would be able to update the firmware?