PFS3 19.0 issue -> READ ERROR - Rootblock could not be loaded

Yulquen74 · 25 June 2018, 21:55

I have played with Winuae 4 and is in the process of setting up
the main partition of a 16GB Kingston CF card, and along the way wanted to do a test with PFS doctor to see if everything was allright. Guess not.
PFS doctor displays the error message during start of check, and then
stops the operation without beeing able to do anything useful.

The partition is set up to just below 4GB with latest aminet version of pfsaio.

Its a basic 3.1 + betterwb install + other stuff on top.

Everything appears fine, I can read and write to the disk, and have not seen any pfs errors during normal use so far.

I get the symptom described above if I use the card in a real A1200.

I can provide more info, just tell me what.

Any help is appreciated.

Toni Wilen · 25 June 2018, 22:38

Sounds like pfsdoctor issue (or it checks something that should not be done) because filesystem can't be mounted without readable root block.

Does http://www.winuae.net/files/b/pfsdoc...perimental.zip report same? It should also include some more information.
("pfsdoctor check devicename")

Yulquen74 · 26 June 2018, 15:40

please see logfile: log.txt

Toni Wilen · 27 June 2018, 09:03

It looks fine. Strange because PFSDoctor logic is same in both versions, only difference is TD64/NSD support. (and large partition support but it makes no difference if partition size is less than 106G)

Do you get different results if you use original pfsdoctor in Direct SCSI mode?

Yulquen74 · 27 June 2018, 17:27

It worked perfect when ran in directscsi mode of course, silly me should have read the manual. Thanks!

25 June 2018, 21:55	#1
Yulquen74 Registered User Join Date: May 2013 Location: Kleppe / Norway Posts: 253	PFS3 19.0 issue -> READ ERROR - Rootblock could not be loaded I have played with Winuae 4 and is in the process of setting up the main partition of a 16GB Kingston CF card, and along the way wanted to do a test with PFS doctor to see if everything was allright. Guess not. PFS doctor displays the error message during start of check, and then stops the operation without beeing able to do anything useful. The partition is set up to just below 4GB with latest aminet version of pfsaio. Its a basic 3.1 + betterwb install + other stuff on top. Everything appears fine, I can read and write to the disk, and have not seen any pfs errors during normal use so far. I get the symptom described above if I use the card in a real A1200. I can provide more info, just tell me what. Any help is appreciated.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Strange issue with PFS3-AIO	Amiga1992	support.Apps	19	12 November 2017 11:28
Pfs3 error	Glen M	support.Apps	9	13 June 2017 00:49
read/write Cd error help	amigang	support.WinUAE	1	30 July 2010 22:57
PFS3 error: INVALID PFS3 COPY !!! WTF?	keropi	support.Apps	10	18 March 2008 22:30
Read/Write error?	one1	support.Games	8	04 June 2003 23:23

25 June 2018, 22:38	#2
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,506	Sounds like pfsdoctor issue (or it checks something that should not be done) because filesystem can't be mounted without readable root block. Does http://www.winuae.net/files/b/pfsdoc...perimental.zip report same? It should also include some more information. ("pfsdoctor check devicename")

26 June 2018, 15:40	#3
Yulquen74 Registered User Join Date: May 2013 Location: Kleppe / Norway Posts: 253	please see logfile: log.txt

27 June 2018, 09:03	#4
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,506	It looks fine. Strange because PFSDoctor logic is same in both versions, only difference is TD64/NSD support. (and large partition support but it makes no difference if partition size is less than 106G) Do you get different results if you use original pfsdoctor in Direct SCSI mode?

27 June 2018, 17:27	#5
Yulquen74 Registered User Join Date: May 2013 Location: Kleppe / Norway Posts: 253	It worked perfect when ran in directscsi mode of course, silly me should have read the manual. Thanks!

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