PFS3 - not visible partitions

OSH · 21 February 2018, 09:47

So, I have big problem.
MY PFS partitions aren't visible. I have A4000 with custom ROM 3.9 and HDD 120 GB. On first partition I have OS 3.9/FFS. Other partitions are under PFS3. Theoretically at least, because they aren't visible. In the beginning they had status „Unreadable”. HDToolbox recognized them as PFS\03. and partitioning was correct (it's my old HDD from A1200). But on the WB they were „Unreadable”. I 've tried to correct this situation and install PFS-AIO on the partition. Now all the partitions are invisible on WB. PFS 3 is installed in system. What is weird: when I've add PFS 3 to the partition, the identifier in window with partition's properties was other than in Window ADD/Change. When I tried to insert the „right” value (0x444f5301), I've got a message, the whole partition will be deleted. scsi.device is 43.45. HDTtoolbox still recognizes they correctly, but HDInsttools not. What is wrong?

fgh · 21 February 2018, 10:39

I would start by putting it in a pc and making an image of the whole drive before doing anything else. (you can make an image in winuae on the harddrive page)

1 Do not format any partitions.
2 Stop using Hdinsttools. It apparently has a nasty bug that can destroy partitions created in hdtoolbox. (insists on its own geometry somehow, not 100% sure on the details)
3 Do you have a backup of the RDB? (rigid disk block)

Changing dostypes and changing between regular and aio versions of pfs will
not destroy partitions even when hdtoolbox says so, but changing geometry will.
(actually it will only change the rdb, but if you then format it data will be lost)

OSH · 21 February 2018, 22:30

Well, it can be problematic. My PC has only SATA and this is IDE HDD. Fortunately, I only check this disk with Hdinsttools, not made any changes or save. You said, If I only enter correct identifier for PFS it won't destroy any partition?
No. I haven't any backup of RDB...
After inserting identifier 0x444F5301 partition has appeared, as WDH1:PFS\1. Now PFSDoctor recognizes it, but reports no errors...

th4t1guy · 22 February 2018, 00:02

You could use an IDE to USB adapter. They work fine mounting in winUAE and you can usually find them for a decent price.

OSH · 22 February 2018, 00:06

Well, I can. But it's something weird.
When I I'm using option Add/Update, then Add New File System and I choose for example PFS3, then I see
Identifier: 0x444F5301
File System Name pfs3ds [Fast File System]
FFS?!
And when I set identifier as 0x444F5301, partition apperas as WDH1:PFS\1 and PFS Doctor recognizes it properly. But when I set identifier as 0x50465303, partition isn't visible, and PFS Doctor cant recognize this partition!

fgh · 22 February 2018, 00:20

My USB to IDE adapter was £4

With PFS3 there are two different versions of the file system: Regular (TD64) should have dostype 0x50465303, and Direct SCSI is 0x50445303. The file system used must match the dostype.
With PFS3AiO you only have one file and it will autodetect DS, NSD or TD64, so you can use both dostypes above, but not the one you're using now.

OSH · 22 February 2018, 01:11

Thanks!!! After inserting right identifier partitions are finally visible! I can't understand, why after loading PFS3AIO the identifier was set for FFS! I have to insert it manually. But once again: thanks!!!

macce2 · 14 October 2022, 23:03

Quote:

Originally Posted by OSH

Well, I can. But it's something weird.
When I I'm using option Add/Update, then Add New File System and I choose for example PFS3, then I see
Identifier: 0x444F5301
File System Name pfs3ds [Fast File System]
FFS?!
And when I set identifier as 0x444F5301, partition apperas as WDH1:PFS\1 and PFS Doctor recognizes it properly. But when I set identifier as 0x50465303, partition isn't visible, and PFS Doctor cant recognize this partition!

I'm having similar problems;
now that I'm playing around with PFS aio and PFS aio Custom.

Which actually are the RIGHT IDENTIFIERS for those ?

I wonder PFS aio was uploaded to Aminet without Any documentation !?

Something went wrong and HDToolbox messes up the identifiers with the ones that have been previously used..?!!

Leon Besson · 15 October 2022, 00:19

Read this;

http://eab.abime.net/showthread.php?t=64949

Make sure you are using version 19.2 as 18.5 has issues Bromigo!

Also try using Dopus4 if the partitions don’t show up for format. Have had to use Dopus 4 to format them before now if they don’t show up in Workbench.

macce2 · 15 October 2022, 14:47

@Leon Besson

Thanks, I should have found that myself.
I successfully updated my filesystem
to PFS aio.

Leon Besson · 15 October 2022, 20:41

Quote:

Originally Posted by macce2

@Leon Besson

Thanks, I should have found that myself.
I successfully updated my filesystem
to PFS aio.

Welcome Bromigo!

21 February 2018, 09:47	#1
OSH Registered User Join Date: Oct 2003 Location: Poland Age: 43 Posts: 142	PFS3 - not visible partitions So, I have big problem. MY PFS partitions aren't visible. I have A4000 with custom ROM 3.9 and HDD 120 GB. On first partition I have OS 3.9/FFS. Other partitions are under PFS3. Theoretically at least, because they aren't visible. In the beginning they had status „Unreadable”. HDToolbox recognized them as PFS\03. and partitioning was correct (it's my old HDD from A1200). But on the WB they were „Unreadable”. I 've tried to correct this situation and install PFS-AIO on the partition. Now all the partitions are invisible on WB. PFS 3 is installed in system. What is weird: when I've add PFS 3 to the partition, the identifier in window with partition's properties was other than in Window ADD/Change. When I tried to insert the „right” value (0x444f5301), I've got a message, the whole partition will be deleted. scsi.device is 43.45. HDTtoolbox still recognizes they correctly, but HDInsttools not. What is wrong? Last edited by OSH; 22 February 2018 at 10:24.

21 February 2018, 22:30	#3
OSH Registered User Join Date: Oct 2003 Location: Poland Age: 43 Posts: 142	Well, it can be problematic. My PC has only SATA and this is IDE HDD. Fortunately, I only check this disk with Hdinsttools, not made any changes or save. You said, If I only enter correct identifier for PFS it won't destroy any partition? No. I haven't any backup of RDB... After inserting identifier 0x444F5301 partition has appeared, as WDH1:PFS\1. Now PFSDoctor recognizes it, but reports no errors... Last edited by OSH; 21 February 2018 at 23:39.

22 February 2018, 00:06	#5
OSH Registered User Join Date: Oct 2003 Location: Poland Age: 43 Posts: 142	Well, I can. But it's something weird. When I I'm using option Add/Update, then Add New File System and I choose for example PFS3, then I see Identifier: 0x444F5301 File System Name pfs3ds [Fast File System] FFS?! And when I set identifier as 0x444F5301, partition apperas as WDH1:PFS\1 and PFS Doctor recognizes it properly. But when I set identifier as 0x50465303, partition isn't visible, and PFS Doctor cant recognize this partition! Last edited by OSH; 22 February 2018 at 00:15.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Kickstart visible at f00000?	selco	support.Other	6	28 December 2018 14:23
Lost files from PFS3-AIO partitions on PATA SSD	Firestone	support.Hardware	5	03 December 2016 15:35
PFS3 or PFS3 SCSI Direct	xalakibaniou	project.ClassicWB	105	27 July 2013 22:08
PFS3 partitions full after format?	emuola	project.ClassicWB	3	19 August 2012 15:25
PFS3 error: INVALID PFS3 COPY !!! WTF?	keropi	support.Apps	10	18 March 2008 22:30

21 February 2018, 10:39	#2
fgh Registered User Join Date: Dec 2010 Location: Norway Posts: 817	I would start by putting it in a pc and making an image of the whole drive before doing anything else. (you can make an image in winuae on the harddrive page) 1 Do not format any partitions. 2 Stop using Hdinsttools. It apparently has a nasty bug that can destroy partitions created in hdtoolbox. (insists on its own geometry somehow, not 100% sure on the details) 3 Do you have a backup of the RDB? (rigid disk block) Changing dostypes and changing between regular and aio versions of pfs will not destroy partitions even when hdtoolbox says so, but changing geometry will. (actually it will only change the rdb, but if you then format it data will be lost)

22 February 2018, 00:02	#4
th4t1guy Registered User Join Date: Mar 2002 Location: Kansas City, MO, USA Posts: 683	You could use an IDE to USB adapter. They work fine mounting in winUAE and you can usually find them for a decent price.

22 February 2018, 00:20	#6
fgh Registered User Join Date: Dec 2010 Location: Norway Posts: 817	My USB to IDE adapter was £4 With PFS3 there are two different versions of the file system: Regular (TD64) should have dostype 0x50465303, and Direct SCSI is 0x50445303. The file system used must match the dostype. With PFS3AiO you only have one file and it will autodetect DS, NSD or TD64, so you can use both dostypes above, but not the one you're using now.

22 February 2018, 01:11	#7
OSH Registered User Join Date: Oct 2003 Location: Poland Age: 43 Posts: 142	Thanks!!! After inserting right identifier partitions are finally visible! I can't understand, why after loading PFS3AIO the identifier was set for FFS! I have to insert it manually. But once again: thanks!!!

15 October 2022, 00:19	#9
Leon Besson Banned Join Date: Feb 2022 Location: Anywhere and everywhere I have a contract Posts: 822	Read this; http://eab.abime.net/showthread.php?t=64949 Make sure you are using version 19.2 as 18.5 has issues Bromigo! Also try using Dopus4 if the partitions don’t show up for format. Have had to use Dopus 4 to format them before now if they don’t show up in Workbench.

15 October 2022, 14:47	#10
macce2 Retro maniac Join Date: May 2005 Location: Finland Age: 49 Posts: 1,219	@Leon Besson Thanks, I should have found that myself. I successfully updated my filesystem to PFS aio.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)