Welcome, Guest. Please login or register.

Author Topic: FileSystem corruption with CF card  (Read 2515 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline paul1981

Re: FileSystem corruption with CF card
« on: April 15, 2012, 01:42:29 PM »
Quote from: darkage;688453
I've cleaned my CF card and started again.. No problems in creating 2x SFS partitions..  ie 900MB system and 6.4GB something non-bootable data partition..

Weird thing is my CF card only boots if I disable the 2nd partition from the kickstart mouse click boot menu...  Both patitions are SFS/00 and Im using KS 3.0 roms..  

Hmm Im missing something here.


You've possibly set your 6.4GB partition as bootable with a priority above that of your 1st partition.  Only the 1st partition should be marked as bootable (your 900MB one) with its boot priority set below that of the floppy drive DF0:
 

Offline paul1981

Re: FileSystem corruption with CF card
« Reply #1 on: April 16, 2012, 09:58:26 PM »
Quote from: darkage;688704
Definitely made sure 2nd partition was not flagged as bootable..  Not sure where to set the boot priority.. from memory when you partition theres a SCSI ID and within the actual a1200 boot menu theres boot priority..

Using my CF Card in IDE mode btw.  

I guess more trial and error :)


If we're talking about internal IDE then there's no SCSI ID, just priorities which you can set in hdtoolbox. But anyway, if it's just your first partition marked as bootable and it's set to a value below DF0: then it shouldn't matter.

So, have you used this tool http://aminet.net/package/disk/misc/fixhddsize to detect and set the correct hard drive parameters (C,H,S) ?

Here's what you should do:

1.Load the latest scsi.device 43.20 or above with the loadmodule command and reboot.

2.Then use the above program fixhddsize to detect the correct size of your drive. Once it detects correct size (7.5 GB is it?) make sure to save the changes (backup any important date as your partitions will be lost).

3.Load HDToolBox or http://aminet.net/package/disk/misc/hdinst or use HDInstTools and sort out your partitions, might as well set partition 1 to 1024MB. And, install SFS on the RDB. Make sure all your partitions are using SFS. Don't forget to set a sensible MaxTransfer value as well.

4.Install your OS onto your 1st partition (1GB)

5.You can either keep using the new scsi.device (slows down the IDE on my A1200) with the loadmodule command, or, get rid of that in the startup-sequence and use FRAP instead (speeds up the IDE on my 1200) http://aminet.net/package/disk/misc/frap_v1.0. (frap requires ROM in RAM 1st, so you'll need QuickROM http://aminet.net/package/util/sys/QuickROM or equivalent if not using RemAPollo or Blizkick. Your 2nd partition should then be safe to use.

That's it. OS in my case would be 3.1  - I can't advise you on anything else as I don't use anything else, but if I'm right, ClassicWB doesn't have large hard drive support enabled by default, although the latest scsi.device is in a largehdd support folder which you just copy to DEVS: and then reboot. Your large 2nd partition should then be okay (using SFS). There's a video on YouTube regarding this.

NSD isn't required because SFS will use directscsi as long as you are using the latest scsi.device or FRAP.
« Last Edit: April 16, 2012, 10:47:14 PM by paul1981 »