Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Matt_H on September 12, 2019, 07:19:54 PM
-
Here's a weird one:
I booted up my OS4.1FE partition on my 4000T to discover that all of my SFS partitions (the drive has around 7 SFS partitions and 1 FFS Intl) were set to read-only, including the OS4 partition itself. Admittedly, it's been a while since I booted OS4 on this machine but I'm pretty sure SFS was operating normally the last time I did. I don't think I've changed anything in hardware or software since then. SFS 1.279 (68K) is in the RDB. The partitions all work correctly (read/write) when I boot into OS3.9. The only way I was able to get the OS4 partition usable from OS4 again was to reformat it as FFS DOS\07 and reinstall.
Any ideas as to what might have happened?
-
*Bump*
Anyone?
-
Since the release of AmigaOS 4.1 FE SFS was set to read only, as it is not supported from AmigaOS 4 any more. I never tried to see if it would work by using the filesystem from AmigaOS 4.1 or older.
-
Since the release of AmigaOS 4.1 FE SFS was set to read only, as it is not supported from AmigaOS 4 any more.
That's true for JXFS, not SFS. SFS should work just fine.
https://wiki.amigaos.net/wiki/UserDoc:AmigaOS_File_Systems
-
@Thomas
Oh my god. You are right. It seems I am getting old and started forgetting. Sorry for that.
-
Here's a weird one:
I booted up my OS4.1FE partition on my 4000T to discover that all of my SFS partitions (the drive has around 7 SFS partitions and 1 FFS Intl) were set to read-only, including the OS4 partition itself. Admittedly, it's been a while since I booted OS4 on this machine but I'm pretty sure SFS was operating normally the last time I did. I don't think I've changed anything in hardware or software since then. SFS 1.279 (68K) is in the RDB. The partitions all work correctly (read/write) when I boot into OS3.9. The only way I was able to get the OS4 partition usable from OS4 again was to reformat it as FFS DOS\07 and reinstall.
Any ideas as to what might have happened?
If it worked under OS3.9 then perhaps your problem was OS4 and the re-install fixed that. After re-installing OS4 with FFS could you then read the remaining SFS partitions?
-
If it worked under OS3.9 then perhaps your problem was OS4 and the re-install fixed that. After re-installing OS4 with FFS could you then read the remaining SFS partitions?
Nope. The only fully usable partitions under OS4 continue to be the OS4 DOS\07 partition and a DOS\03 partition. Reinstall made no difference. :\
-
Did you allready wrote something about it on the Hyperion support forum ?
-
It will not cure the problem but i'm curious if you can unlock your partitions with the "lock" command?
if they can be made unlocked with the lock command i guess theres something in your startup that locks them.
-
If it worked under OS3.9 then perhaps your problem was OS4 and the re-install fixed that. After re-installing OS4 with FFS could you then read the remaining SFS partitions?
Nope. The only fully usable partitions under OS4 continue to be the OS4 DOS\07 partition and a DOS\03 partition. Reinstall made no difference. :\
How about try loading an older SFS version onto the RDB?
-
@ Bennymee
I'm not a member there, hence why I'm raising the question with the fine folks here :)
@ smf
Lock command was the first thing I tried. No luck :(
@ paul1981
I reverted to 1.277 with the same result, but I'm not sure it matters because OS4 loads 1.290 (I think) as a kickstart module. That's what the system reports if I do a 'version dh3:' in the shell.
-
Did you check already if it happens rather early in the boot process or later, after Workbench has been loaded?
-
@ Bennymee
I'm not a member there
You probably should be if you're running OS4.
@ paul1981
I reverted to 1.277 with the same result, but I'm not sure it matters because OS4 loads 1.290 (I think) as a kickstart module.
Yeah, OS4 uses the PPC version of a file system loaded as a Kickstart module. The only thing a 68k module in the RDB is used for is for cold booting, where the 3.1 ROM is all you've got.
(And always only put 68k versions in the RDB, PPC versions go in Kickstart only - I guess you know that, but maybe some readers didn't.)
Anyway, if you want to revert to an earlier version, you have to find an older PPC Kickstart module to put in your Kickstart dir.
Best regards,
Niels
-
Did you check already if it happens rather early in the boot process or later, after Workbench has been loaded?
Good point.
-
@ TribbleSmasher
Good idea, but I just booted OS4 with no startup-sequence and the Info command still reports SFS partitions as read-only.
@ Niels
I tried kickstart modules of 1.279 and 1.286 - still no luck.
Does the OS4 installer do anything special apart from copy files and set the specified preferences? I ask because my re-install attempt crashed partway through and I ended up copying the rest of the files by hand. Is there some sneaky script that tells the system it's "ready"? I found the one for the SObjs: softlinks, but is there something that's part of the install script that my non-Python-knowing eyes can't see?
-
Does the OS4 installer do anything special apart from copy files and set the specified preferences? I ask because my re-install attempt crashed partway through and I ended up copying the rest of the files by hand. Is there some sneaky script that tells the system it's "ready"? I found the one for the SObjs: softlinks, but is there something that's part of the install script that my non-Python-knowing eyes can't see?
I' dont know why but iirc something like that will happen if you install to a non-empty partition.