11 May 2016, 17:02 | #1 |
Registered User
Join Date: May 2015
Location: Belgium
Posts: 132
|
FastATA 4000 MK-VI - maxtransfer and filesystems
I'm having some random freezes during CWB boot with my FastATA 4000 MK-V... and I was wondering if I might have setup my CF wrongly.
|
11 May 2016, 17:52 | #2 |
Registered User
Join Date: Oct 2009
Location: Germany
Posts: 3,310
|
I guess with "may be used with >4GB HDDs independently of the installed filesystem" they mean the Split feature (each 2GB partitions).
Yes. |
12 May 2016, 08:54 | #3 |
Repulsive
Join Date: Nov 2015
Location: stockholm Sweden
Posts: 89
|
Yes they mean the split feature, I use a 20G harddrive splitted in 6(!) partitions of 4G.
The split function split a large harddisk in 4G pieces and then present them to the OS as independent disks that you then can partition with hdtoolbox. And even if people claim 2G is the max limit the real limit is 4G per partition with standard FFS, the only resason that C= recommended a max size of 2G is that there is a limit of 2G per file, and there is no system to stop you from accidenticaly create a file larger than 2G, therefore it is a potential danger to have partitions larger than 2G. I have used kick 3.1 and 4G partitions about 20 years now.. Yes you probably should load the fastata driver after blizkick Regarding the maxtransfer I only change it when its needed, and thats not very often so I don't know. Last edited by glenn; 12 May 2016 at 08:57. Reason: explained disk -> partition |
12 May 2016, 09:03 | #4 |
Registered User
Join Date: May 2015
Location: Belgium
Posts: 132
|
Thanks for the replies.
I have 3 partitions, a boot partition of about 500MB, and 2 other partitions of around 7GB. All formatted with PFS3 and maxtransfer 0x1FE00. So no need to use the SPLIT function of FastATA I guess. |
12 May 2016, 15:25 | #5 |
Registered User
Join Date: Oct 2009
Location: Germany
Posts: 3,310
|
You can use Thomas its MaxTransTest Tool to check if the MaxTransfer value is safe to use or not.
If you use SFS/PFS or a new proper FFS version, then you can avoid the Split option of the FastATA. With a large HD split into 2GB wouldn`t make much sense. |
12 May 2016, 22:32 | #6 | |||||
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,033
|
Quote:
Quote:
AFAIK the FastATA driver supports all available command sets, so in combination with a suitable file system you can partition the harddrive as you like. Even one big 20GB boot partition will work. Quote:
Quote:
Quote:
If the harddrive or IDE bus freezes, you usually can use the system just normally only disk accesses are not responded to. For example you can close Workbench windows but not open new ones. |
|||||
13 May 2016, 10:43 | #7 | ||||
Registered User
Join Date: May 2015
Location: Belgium
Posts: 132
|
Thanks a lot for your clear explanation @thomas, it's much appreciated!
Quote:
Strangely enough I don't see a difference in "version scsi.device" before or after loading the FastATA.driver? Quote:
Quote:
When I put "C:fastATA.driver QUIET" before "C:BlizKick DEVS:custom.rom CPUCARD QUIET" workbench sometimes starts, sometimes not... I see the same behavior with cold, warm, hot reboots. Quote:
|
||||
13 May 2016, 14:42 | #8 | ||
Registered User
Join Date: Oct 2009
Location: Germany
Posts: 3,310
|
Quote:
Edit: Only true for FastATA A1200. Not for FastATA A4000! Until another scsi.device is loaded the verson in ROM is used. That is important to know if you start your Amiga without Startup-Sequence. At that point the limits of the ROM scsi.device are valid. If you do write access to HD start the FastATA driver first. Edit end. Quote:
Are you sure that the driver for FastATA A4000 MK IV is named "fastATA.driver"? I ask because the driver for FastATA A1200 is named "ata3.driver". However, about your boot problems you may add "set echo on" on top of your startup-sequence to see if something goes wrong. Its also a good idea to remove the "QUIET" switch from at least blizkick and fastATA.driver for testing time. If you want to check if fastATA.driver is running you can start it after booting from a Shell. If already running it should output some information about connected devices. Last edited by daxb; 14 May 2016 at 13:47. |
||
13 May 2016, 16:11 | #9 | ||
Registered User
Join Date: May 2015
Location: Belgium
Posts: 132
|
I finally figured out the issue thanks to the feedback from @daxb and @thomas above. Thank you guys!!
I didn't do this... Whenever I booted without startup-sequence I never manually loaded the fastata.driver before editing the startup-sequence... This seems to be very crucial indeed. Not doing this corrupted the startup-sequence file in a way and stopped the startup-sequence during the workbench boot. I wonder what exactly goes wrong when writing to HD without a FastATA driver loaded... ? I now booted without startup-sequence, manually loaded the fastata.driver and edited the startup-sequence file. I've put the "C:BlizKick DEVS:custom.rom CPUCARD QUIET" as the first line, and the "C:fastATA.driver QUIET" on the second line, and now everything boots perfectly! Problem solved! Quote:
Quote:
Really happy to have find a solution to this issue, thanks everyone for the help. |
||
13 May 2016, 16:41 | #10 | ||
Registered User
Join Date: May 2015
Location: Belgium
Posts: 132
|
I finally figured out the issue thanks to the feedback from @daxb and @thomas above. Thank you guys!!
I didn't do this... Whenever I booted without startup-sequence I never manually loaded the fastata.driver before editing the startup-sequence... This seems to be very crucial indeed. Not doing this corrupted the startup-sequence file in a way and stopped the startup-sequence during the workbench boot. I wonder what exactly goes wrong when writing to HD without a FastATA driver loaded... ? I now booted without startup-sequence, manually loaded the fastata.driver and edited the startup-sequence file. I've put the "C:BlizKick DEVS:custom.rom CPUCARD QUIET" as the first line, and the "C:fastATA.driver QUIET" on the second line, and now everything boots perfectly! Problem solved! Quote:
Quote:
Really happy to have find a solution to this issue, thanks everyone for the help. |
||
13 May 2016, 19:01 | #11 | |
Registered User
Join Date: Oct 2009
Location: Germany
Posts: 3,310
|
Quote:
Edit: Removed wrong stuff. See Thomas note below. Edit: Following is only true for FastATA A1200. Not for FastATA A4000: So, for example if you boot without startup-sequence and start a game you want to play from a partition beyound 4GB. The game saves a highscore or config to HD. Then it can happen that the write access is done on boot partition instead of the game one. This can/will cause data corruption you may notice too late. Last edited by daxb; 14 May 2016 at 13:50. |
|
13 May 2016, 20:14 | #12 | |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,033
|
Quote:
Version of scsi.device does not matter. V40 is not the FastATA driver, it's Commodore's driver for the internal IDE port. It has nothing to do with FastATA. If another scsi.device is already in the system, then the FastATA driver becomes 2nd.scsi.device or 3rd.scsi.device and so on. The FastATA driver has nothing in common with the Motherboard driver except a part of the name, and they don't act on each other's hardware. You should be aware that the FastATA 4000 is a true and properly implemented expansion, not a patchwork like the FastATA 1200. Last edited by thomas; 13 May 2016 at 20:19. |
|
14 May 2016, 13:44 | #13 |
Registered User
Join Date: Oct 2009
Location: Germany
Posts: 3,310
|
Thanks for clarification Thomas! I thought FastaATA A1200 and FastATA A4000 work/behave the same or very similar. Two further questions to FastATA A4000:
Does it mean that devices at FastATA and at internal IDE port can be used both parallel? Will the FastATA initialized/recognized during hardware initialization like for example accelerator boards? |
14 May 2016, 13:55 | #14 | ||
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,033
|
Quote:
Quote:
OTOH if you remove all drives from the internal IDE port you will suffer from the 10s boot delay. |
||
14 May 2016, 17:52 | #15 |
Registered User
Join Date: Sep 2007
Location: Stockholm
Posts: 4,357
|
|
19 May 2016, 13:15 | #16 |
Repulsive
Join Date: Nov 2015
Location: stockholm Sweden
Posts: 89
|
You can even use a splitter on the internal IDE combined with fastATA4000.
In my A4000T I have two harddisks and one CD-burner on internal IDE, and then four harddisks on the FastATA4000. |
01 February 2021, 22:20 | #17 |
Registered User
Join Date: Oct 2007
Location: ManCave, Canada
Posts: 1,650
|
can any owners confirm if I can use my DOM with FastATA 4000 MK-VI? Right now its happily working in the MB IDE connector but would be great to speed it up on the FastATA if possible
|
04 February 2021, 22:27 | #18 |
Registered User
Join Date: Dec 2018
Location: Helmsdale Scotland
Age: 41
Posts: 181
|
I had a 16gb hyperdisk DOM working fine on my fastaATA4000.
|
05 February 2021, 05:51 | #19 |
Registered User
Join Date: Oct 2007
Location: ManCave, Canada
Posts: 1,650
|
|
05 February 2021, 08:54 | #20 |
Registered User
Join Date: Dec 2018
Location: Helmsdale Scotland
Age: 41
Posts: 181
|
It was about 6-7mg/s I think (sysinfo results). Unfortunately I can't test it again as the fastata went on fire when I accidently fitted it upside down.
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Fastata 4000 mkiv and mediator 4000 problems | Benfromnorway | support.Hardware | 0 | 19 September 2014 20:15 |
FastATA MK-VI 4000 | videofx | support.Hardware | 4 | 29 May 2014 17:39 |
FastATA MK-VI 4000 CF/SATA in A3000D | trixeo | support.Hardware | 3 | 07 June 2013 10:44 |
FastATA 4000 MK-III comatible with A3000? | Akiko | support.Hardware | 0 | 13 September 2012 20:49 |
Buddha Flash Gold vs. FastATA 4000 | Worfje | support.Hardware | 4 | 22 January 2005 00:31 |
|
|