Welcome, Guest. Please login or register.
Amiga Kit Amiga Store Iridium Banner AMIStore App Store A1200/A600 4xIDE Interface

AuthorTopic: damn checksum error on FFS partition!  (Read 586 times)

0 Members and 1 Guest are viewing this topic.

Offline F1Lupo

damn checksum error on FFS partition!
« on: March 15, 2020, 10:25:50 PM »
so I know there's a new DiskDoctor and although DiskSalv has saved my partitions before I remembered it's only for drives less than 4GB soooooooo how to use DiskDoctor ???
go to shell, run diskdoctor sys:...it runs examining the disk BUT does is there a separate command to fix checksum errors etc.?
____________________________________________________________________
c64-dual sids, A1000, A1200-060@50, A4000-CSMKIII
Indivision AGA & Catweasel MK4+= Amazing
! My Master Miggies-Amiga 1000 & AmigaOne X1000 !
--- www.mancave-ramblings.blogspot.ca ---
  -AspireOS.com & Amikit- Amiga for your netbook-
***X1000- I BELIEVE *** :angel:
 

Offline F1Lupo

Re: damn checksum error on FFS partition!
« Reply #1 on: March 15, 2020, 10:32:27 PM »
wow ! so did that just & re-booted few times with no annoying checkum errors so looks like DiskDoctor actually did more than 'examining' ;D
____________________________________________________________________
c64-dual sids, A1000, A1200-060@50, A4000-CSMKIII
Indivision AGA & Catweasel MK4+= Amazing
! My Master Miggies-Amiga 1000 & AmigaOne X1000 !
--- www.mancave-ramblings.blogspot.ca ---
  -AspireOS.com & Amikit- Amiga for your netbook-
***X1000- I BELIEVE *** :angel:
 

Offline olsen

Re: damn checksum error on FFS partition!
« Reply #2 on: March 16, 2020, 12:40:29 PM »
wow ! so did that just & re-booted few times with no annoying checkum errors so looks like DiskDoctor actually did more than 'examining' ;D

No, the new Disk Doctor can only read from the partition, it will never write to it. This is baked into the design itself, as a precaution. The plan was to add a repair operation, but I still needed to figure out how to perform it, and which goals to follow.

If a reboot alone solved the problem then the cause may have been memory corruption, for example. When did you last verify that your RAM is in good working order? The simplest test involves copying as many files into the RAM disk until it either fills up or the system crashes. The RAM disk is particularly vulnerable to memory corruption and flaky DRAMs due to how it manages its data, which is why it (accidentally) makes for a "convenient" RAM test.
 
The following users thanked this post: F1Lupo

Offline F1Lupo

Re: damn checksum error on FFS partition!
« Reply #3 on: March 16, 2020, 05:29:41 PM »
@ olsen
interesting info...the checksum errors on my system popped up after literally hours of transferring files from a CF card in the pcmcia port to a 32GB DOM in the onboard IDE port...I believed a small electricity interruption in my house stopped the transferring and that's when errors started popping up......

so the new DiskDoctor with OS3.1.4 only 'examines' hard drives so what to use then on drives larger than 4GB's nowadays to try to 'repair' issues ?
____________________________________________________________________
c64-dual sids, A1000, A1200-060@50, A4000-CSMKIII
Indivision AGA & Catweasel MK4+= Amazing
! My Master Miggies-Amiga 1000 & AmigaOne X1000 !
--- www.mancave-ramblings.blogspot.ca ---
  -AspireOS.com & Amikit- Amiga for your netbook-
***X1000- I BELIEVE *** :angel:
 

Offline kolla

Re: damn checksum error on FFS partition!
« Reply #4 on: March 17, 2020, 07:00:49 AM »
so the new DiskDoctor with OS3.1.4 only 'examines' hard drives so what to use then on drives larger than 4GB's nowadays to try to 'repair' issues ?

SYS:System/Format - there are no tools around to "repair" a broken "modern" FFS.

DiskDoctor is not a good name, it doesn't by any means "doctor" disks, a more describing name would be "FFSDump", as that is all it does - dump the content of a broken FastFileSystem.

I wish there was ways to prevent the built in validator from starting, as it often crash for various reasons (low memory situations etc), and just allow _manual_ optimistic read-only mounting of FFS also when running AmigaOS (and not just when running NetBSD or Linux...)
« Last Edit: March 17, 2020, 07:01:21 AM by kolla »
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM460 and Mac minis with MorphOS
 

Offline F1Lupo

Re: damn checksum error on FFS partition!
« Reply #5 on: March 17, 2020, 07:41:34 AM »
@ kolla
ouch  :o so we have nice large new FFS partitions with new roms and OS3.1.4 + but no way to fix or try to repair common issues on them unless we keep them beneath the old 4GB limit :o :-\ :'(
____________________________________________________________________
c64-dual sids, A1000, A1200-060@50, A4000-CSMKIII
Indivision AGA & Catweasel MK4+= Amazing
! My Master Miggies-Amiga 1000 & AmigaOne X1000 !
--- www.mancave-ramblings.blogspot.ca ---
  -AspireOS.com & Amikit- Amiga for your netbook-
***X1000- I BELIEVE *** :angel:
 

Offline kolla

Re: damn checksum error on FFS partition!
« Reply #6 on: March 17, 2020, 10:29:54 AM »
@ kolla
ouch  :o so we have nice large new FFS partitions with new roms and OS3.1.4 + but no way to fix or try to repair common issues on them unless we keep them beneath the old 4GB limit :o :-\ :'(
And also "no long file names".

But seriously - how often do you really need to repair filesystem on Amiga? I know that it doesn't really happen so often with my systems.

One thing I have been looking for, is a proper "shutdown" tool, that makes sure all local drives are dismounted ("BUSY") before popping up a requester with a "Reboot" button, telling me that it is now ok to power off the system.
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM460 and Mac minis with MorphOS
 

Offline olsen

Re: damn checksum error on FFS partition!
« Reply #7 on: March 17, 2020, 10:44:51 AM »
@ olsen
interesting info...the checksum errors on my system popped up after literally hours of transferring files from a CF card in the pcmcia port to a 32GB DOM in the onboard IDE port...I believed a small electricity interruption in my house stopped the transferring and that's when errors started popping up......

Sounds like the destination device may have been affected by the electricity hickup. If everything on the medium still looks OK, you'd be the lucky one :)

Quote
so the new DiskDoctor with OS3.1.4 only 'examines' hard drives so what to use then on drives larger than 4GB's nowadays to try to 'repair' issues ?

As of this writing I cannot recommend any tool for the job. The new Disk Doctor was supposed to be the tool which should solve the whole issue of multiple file systems, large storage devices and what have you. It's just that by the time the error detection and data recovery were finally coming together well, there was too little time left to wrap up the project with data repair included. Repairing an Amiga file system is hard because so much can go wrong.

In the mean time, what works would be to copy the data off your possibly corrupted volume to a different volume with Disk Doctor, then reformat your corrupted volume and copy everything back. Disk Doctor handles soft and hard links and will make a perfect file copy. Not that you'd want to bite that bullet unless you have to  :o

Still, it's helpful to have a known-good backup of the data you value and want to preserve.
 
The following users thanked this post: F1Lupo

Offline olsen

Re: damn checksum error on FFS partition!
« Reply #8 on: March 17, 2020, 10:57:57 AM »
so the new DiskDoctor with OS3.1.4 only 'examines' hard drives so what to use then on drives larger than 4GB's nowadays to try to 'repair' issues ?

SYS:System/Format - there are no tools around to "repair" a broken "modern" FFS.

DiskDoctor is not a good name, it doesn't by any means "doctor" disks, a more describing name would be "FFSDump", as that is all it does - dump the content of a broken FastFileSystem.

The new Disk Doctor can both find and report defects as well as recovering data from the volume, with various options to restrict the set of directories, files and links which you want to keep. The recovery operation preserves all file attributes (date, owner, protection, comment) and will reproduce both soft and hard links (if possible; if the target for the hard link is not copied you won't get the link). It spends far more effort on the task than dumping what it finds on the source volume.

My ambition still is to go beyond the examine/copy operation, which all by themselves turned out to be far more complex than I had anticipated. The learning process was painful and it colours how a possible repair operation would have to work.

Disk Doctor is arguably a poor name, especially in the light that a medical doctor's duty is so different from what, by analogy, the original Workbench 1.2/1.3 Disk Doctor did. For one thing, destructive changes made to the disk contents should require the user's informed consent, but the 1.2/1.3 Disk Doctor never went that far. It just did its best to make a presumably damaged disk accessible to normal file system operations again. It was recommended that when the 1.2/1.3 was "finished" with a disk, that its contents should be copied to a known-good disk and the disk whence the contents came from should be reformatted. The 1.2/1.3 Disk Doctor was expected to make irreversible changes with negative impact to the disk.

Keeping the name "Disk Doctor" was to make a point of how to properly do the kind of job which the original tool was not designed to handle well. You should be in control of what Disk Doctor does, and you should be informed about the choices you have when you are looking at a possibly damaged volume and want to recover its data. It's uncommon but not wrong to try and apply medical ethics to data recovery.

Quote
I wish there was ways to prevent the built in validator from starting, as it often crash for various reasons (low memory situations etc), and just allow _manual_ optimistic read-only mounting of FFS also when running AmigaOS (and not just when running NetBSD or Linux...)

Only write-protecting a volume will keep the validation process from starting. Back in the day when the Disk-Validator was separate from the ROM file system you could prevent it from becoming active by removing it from the boot volume.

Most storage media is auto-mounted and cannot be made to appear write-protected. This is an unsolved problem which is not supposed to happen.
« Last Edit: March 17, 2020, 11:02:23 AM by olsen »
 
The following users thanked this post: F1Lupo

Offline kolla

Re: damn checksum error on FFS partition!
« Reply #9 on: March 17, 2020, 02:15:31 PM »
HDToolBox (RDB) and Early-startup could allow setting partitions read-only, or "non-validate".
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM460 and Mac minis with MorphOS
 

Offline F1Lupo

Re: damn checksum error on FFS partition!
« Reply #10 on: March 17, 2020, 06:01:27 PM »
@ olsen
thanks so much for the detailed explanation. I guess I'm lucky in that I can transfer files from my affected partition to my CF card with no problems so far...the process will be slow as I had alot of data on that partition but at least DiskDoctor has allowed me to backup/transfer files.
So I wonder if there are any 'repair' programs if I choose to format the affected partition with SFS (or others) next time.....I thought the new FFS was the more stable/secure option for larger than 4GB partitions moving forward but this experience has left me snake bitten
____________________________________________________________________
c64-dual sids, A1000, A1200-060@50, A4000-CSMKIII
Indivision AGA & Catweasel MK4+= Amazing
! My Master Miggies-Amiga 1000 & AmigaOne X1000 !
--- www.mancave-ramblings.blogspot.ca ---
  -AspireOS.com & Amikit- Amiga for your netbook-
***X1000- I BELIEVE *** :angel:
 

Offline kolla

Re: damn checksum error on FFS partition!
« Reply #11 on: March 18, 2020, 01:26:24 PM »
Always use frequent backups and distribute them for safety.
(even when it means breaking the software license that the operating system is distributed with - sigh!)
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM460 and Mac minis with MorphOS
 

Offline F1Lupo

Re: damn checksum error on FFS partition!
« Reply #12 on: March 18, 2020, 11:51:08 PM »
true the answer is always to backup whats important for sure but I've saved many partitions on my miggies over the years from the dreaded checksum errors using DiskSalv but of course all those partitions were below the magical 4GB mark ;) ...looks like I'll be making some more 4GB partitions as I've always done before moving forward to at least save time and headaches next time a little power bleep occurs while my hard drive is working ;D
« Last Edit: March 18, 2020, 11:53:37 PM by F1Lupo »
____________________________________________________________________
c64-dual sids, A1000, A1200-060@50, A4000-CSMKIII
Indivision AGA & Catweasel MK4+= Amazing
! My Master Miggies-Amiga 1000 & AmigaOne X1000 !
--- www.mancave-ramblings.blogspot.ca ---
  -AspireOS.com & Amikit- Amiga for your netbook-
***X1000- I BELIEVE *** :angel:
 

Offline olsen

Re: damn checksum error on FFS partition!
« Reply #13 on: March 19, 2020, 10:34:06 AM »
HDToolBox (RDB) and Early-startup could allow setting partitions read-only, or "non-validate".

Thank you! I can see how this would be made to work.

To begin with, we could use the file system control flags which were introduced with AmigaOS 3.1.4. Currently, the FFS uses such control flags to enable/disable TD64/NSD64 support on demand. There should be another flag bit available which would indicate that the volume should be mounted read-only.

That feature would (initially) be supported by the FFS only. Upon startup, it could check that flag bit and pretend for the time being that the mass storage medium is write-protected. If you wanted to revert to how things really are (not write-protected), the DiskChange command could do that.

The "mount as read-only" option should (initially) find its place in the early startup menu.

Offline kolla

Re: damn checksum error on FFS partition!
« Reply #14 on: March 19, 2020, 12:30:08 PM »
@olsen

Yes, sounds like a good plan :)
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM460 and Mac minis with MorphOS