PFS3AIO v3.1 Final

[nexus]

ok i figured out that it throws the above errors when im writing something and the dvd drive spins down if i abort the retry it tosses tons of errors then write protects the partition and only a reboot am i allowed to reformat it
also i have to reformat as it wont show the files that were copied to delete just appears empty but space still used

i tested the drive spinning down theory many times soon as it stops spinning a error appears 100% of the time

[Toni Wilen]

Originally Posted by nexus

ok i figured out that it throws the above errors when im writing something and the dvd drive spins down if i abort the retry it tosses tons of errors then write protects the partition and only a reboot am i allowed to reformat it
also i have to reformat as it wont show the files that were copied to delete just appears empty but space still used

i tested the drive spinning down theory many times soon as it stops spinning a error appears 100% of the time

Odd side-effect..

If you want to debug this more:

Do you also get some error if you don't use Direct SCSI mode? (or for example use plain FFS) Unfortunately I don't think warp engine has >4G support (do not use NSD patch, it just redirects to direct scsi) so you must repartition and only use max 4G from the beginning of the drive. Which makes this very boring test...

If it does NOT cause errors: warpdrive.device must use some workaround.

Does CD spin down also cause problem if you don't mount the CD drive? (CD filesystem not loaded, drive not visible in AmigaOS)

It is normal for pfs3 becoming read-only when it detects error. It is protection mode. C:Lock can be used to remove write protection.

[nexus]

it might be my termination due to the sca 80 to 50pin adapter for the harddrive that is causing this as the dvd is my terminator and is 50pin im not a super pro at old scsi so like said before it could be incorrect termination
so this is my chain warpengine that is terminated with a 3 port cable with sca 80 to 50 pin on harddrive in the middle with 50pin dvdrom terminating the end

if the above is ok then ill do the other test i just dont want you fixing a hardware issue

[trixster]

Originally Posted by Joel_w

A new version of PFS3-AIO was just released and I wonder if I can update my A1200 by just using the Add/Update feature in HD Toolbox or if I have to reformat?

The disk was formatted with the previous version, and when I run the PFS Doctor program it tells me that my disk was formatted with “PFS II 18.5”. The new file from Aminet has version number 19. But I guess that doesn't really matter, the important part is what version is loaded from RDB at boot, right?

I have the same question as Joel!

[nexus]

if its under 5GB then no and the new is 19
you cant use pfsdoctor with these
http://eab.abime.net/showpost.php?p=...8&postcount=14

[Toni Wilen]

Reformat is not needed (Except if pfsdoctor reports unfixable errors due to recently fixed old bug).

v19 is fully backwards compatible with v18 (and older). Only if using v19 only feature (Partition is larger than 104G) makes it incompatible with v18 and also requires updated pfsdoctor. (which is linked in first post).

--

v3.1 was just uploaded to aminet. New thread or thread rename? (which I can't do)

[nexus]

did you add anything new since the last? test 3

[Toni Wilen]

No, it is almost identical to test #3, only difference is accidentally introduced useless data hunk removed. (which made test #3 non-rommable)

[DamienD]

Originally Posted by Toni Wilen

v3.1 was just uploaded to aminet. New thread or thread rename? (which I can't do)

If you want the thread renamed Toni then let me know

[Toni Wilen]

I think renaming this thread is better option, changes are relatively minor, at least when compared from v2.x to v3.x. I'll update first post after rename.

[DamienD]

Done

[apex]

Thank you Toni for 3.1!!! :-)

[spudje]

Haven't tried AmigaOS 3.1.4 yet, is this included there, as they support larger partitions now? If not, can I still configure this manually and will it work as usual with AmigaOS 3.1.4?

[gulliver]

Thank you very much for your continued work and support on PFS3.

[Gilloo]

Got a 8GB thumb disk orchestred with pfs3aio with 1.3/2.04/2.1/3.1/3.1 + P96/3.1.4
It depends of the exec.library version and cpu, and selects the good OS.
It works well on WinUAE, and also A2000 (for the moment 1.3 and 3.1)
Well done Toni ! (many thanks for your work)

[cip060]

double click and winuae crash

[Hedeon]

Thanks Toni for your terrific work in continuing work on PFS, a personal favorite of mine since the last century :-)

During switching a jumper on my Mediator I inadvertently broke a 12V power line of a Molex connector (the yellow one). I noticed this when I switched on the A1200 and it lit up like a christmas tree inside (literally!), plus the smell of plastic. I haven't identified where the smell came from, everything seems in order and still works after removing the affected powercords.

The end of this powercord was connected to my CF2IDE card with a 4GB flash card in it.

The Amiga now says no device present in HD1: (this is the first partition on the disk, don't ask me why) which is 900MB large. All other partitions are still there (3 others, all around 900-1000MB). I looked with AZAP to HD1: and the first sector is still starting with the correct identifier. The filesystem at that time was 18.5. I have upgraded today to V19 (3.1).

I started pfsdoctor with the CHECK parameter and it says ERROR: not an AFS, PFS-II or PFS-III disk (the experimental pfsdoctor) rootblock not found. It has been saying now for ages 'Searching filesystem 2048....'

So my real question is:

Could something be implemented that gives something of a progress? I am not sure if it is doing something (HD light is off) or it that it is just hanging in some loop. The system itself is still responsive. I can break it off with CTRL-C.

Or do I need the regular pfsdoctor for this as it does not have >104GB partitions or doesn't that matter?

Original PFS doctor does complete the test but sadly finds nothing to repair. Not sure if there is extra search logic in the experimental pfsdoctor?

EDIT: unformat with the original PFSdoctor at least restored the partition :-D

EDIT2: original PFSdoctor with CHECK did stop on an invalid identifier for a rext block, so actually didn't complete check. Unformat corrected that. Not sure why experimental pfsdoctor keeps hanging on CHECK. As the partition is fixed now I can no longer check.

[DamienD]

Originally Posted by cip060

double click and winuae crash

What does that mean? Double-click what exactly? Are you saying when starting your .HDF after applying the latest version of PFS3AIO?

@Toni; think you'll might have to use your powerful crystal ball for this one

[Toni Wilen]

Originally Posted by cip060

double click and winuae crash

Unlikely and you are doing it very wrong. This thread is not for filesystem basics.

[Toni Wilen]

Originally Posted by Hedeon

Or do I need the regular pfsdoctor for this as it does not have >104GB partitions or doesn't that matter?

Both should work.

Original PFS doctor does complete the test but sadly finds nothing to repair. Not sure if there is extra search logic in the experimental pfsdoctor?

There is no extra logic, only differences are:
- GUI is gone
- NSD/TD64/DS supported. (original only has DS)
- Support for >104G partitions
- Support for >4G file sizes

EDIT: unformat with the original PFSdoctor at least restored the partition :-D

EDIT2: original PFSdoctor with CHECK did stop on an invalid identifier for a rext block, so actually didn't complete check. Unformat corrected that. Not sure why experimental pfsdoctor keeps hanging on CHECK. As the partition is fixed now I can no longer check.

Impossible to say without having HDF of image that does not work.