Discs and drives: best approaches? some specifics...
Posted: Tue Jan 29, 2019 2:02 pm
Hi,
I realise I am unclear about the best way to check for and fix any disk errors that might be found in the SS emulated world.
I have been using Edwards ready built 64bit SS based MacOS9 and moved my databases in there from ChubbyBunny where they had been for some years.
I was looking into the sparse bundle and backups of my MacOS9 configuration and noticed there seemed to be some errors, maybe, in the bundle. Working on backups I tried various things to investigate and maybe fix.
First major choice was to do it from within OS9 using a number of Apple or 3rd party tools I have used over the centuries (starting in 19xx). Well I started in host MacOS 10.11 since this is where I want to copy and preserve my data and figure I have the latest tools especially if I end up need AFPS etc in the mix (where i am also making moves towards moving to Mojave if I can assure myself on a few points first...)
I had been moving a fair bit of files around in the OS9 virtual system drive, and it seemed a good idea to look at empty trash and maybe "hdiutil compact" the host sparse image at
/Applications/MacOS9/Mac\ OS\ 9.app/Contents/Resources/Files/MacOS.sheepvm/MacOS9.sparsebundle
(FIRST MAKING SURE SS/MACOS 9 WAS CORRECTLY EXITED)
I got a first worry with the response:
Starting to compact…
Reclaiming free space…
hdiutil: compact failed - internal error
SS/ OS9 still runs up OK... a bit of research leads me to try
hdiutil attach -nomount -noverify -noautofsck <the MacOS9.sparsebundle>
that produced:
/dev/rdisk4s2: fsck_hfs started at Tue Jan 29 12:49:22 2019
/dev/rdisk4s2: /dev/rdisk4s2: ** /dev/rdisk4s2 (NO WRITE)
/dev/rdisk4s2: Executing fsck_hfs (version hfs-305.10.1).
QUICKCHECK ONLY; FILESYSTEM CLEAN
/dev/rdisk4s2: fsck_hfs completed at Tue Jan 29 12:49:22 2019
Not much else going on so run up ElCap's Disk Utility, see the container drive, see the active MacOS9 volume within it and so run Repair/Check on that:
/dev/rdisk4s2: fsck_hfs started at Tue Jan 29 12:52:39 2019
/dev/rdisk4s2: /dev/rdisk4s2: Executing fsck_hfs (version hfs-305.10.1).
/dev/rdisk4s2: ** Checking non-journaled HFS Plus Volume.
/dev/rdisk4s2: The volume name is MacOS9
/dev/rdisk4s2: ** Checking extents overflow file.
/dev/rdisk4s2: ** Checking catalog file.
/dev/rdisk4s2: Invalid BSD file type
/dev/rdisk4s2: Invalid BSD file type
/dev/rdisk4s2: Invalid BSD file type
/dev/rdisk4s2: Invalid BSD file type
/dev/rdisk4s2: Invalid BSD file type
/dev/rdisk4s2: Invalid BSD file type
/dev/rdisk4s2: Invalid BSD file type
/dev/rdisk4s2: Invalid BSD file type
/dev/rdisk4s2: ** Checking multi-linked files.
/dev/rdisk4s2: ** Checking catalog hierarchy.
/dev/rdisk4s2: ** Checking volume bitmap.
/dev/rdisk4s2: ** Checking volume information.
/dev/rdisk4s2: ** Repairing volume.
/dev/rdisk4s2: ** Rechecking volume.
/dev/rdisk4s2: ** Checking non-journaled HFS Plus Volume.
/dev/rdisk4s2: The volume name is MacOS9
/dev/rdisk4s2: ** Checking extents overflow file.
/dev/rdisk4s2: ** Checking catalog file.
/dev/rdisk4s2: ** Checking multi-linked files.
/dev/rdisk4s2: ** Checking catalog hierarchy.
/dev/rdisk4s2: ** Checking volume bitmap.
/dev/rdisk4s2: ** Checking volume information.
/dev/rdisk4s2: ** The volume MacOS9 was repaired successfully.
/dev/rdisk4s2: fsck_hfs completed at Tue Jan 29 12:52:39 2019
Sounds OK but now that copy will not start-up fully, flashing floppy icon and must force quit.
SO MY QUESTIONS?
What is the "best way" to delete files and tidy up / back up the config?
What are the ways and consequences of the various ways of looking at the disk drive?
In the event of corruption / data loss etc what is the best way to move forward?
Thanks for your time and hope this helps more than just myself!
I realise I am unclear about the best way to check for and fix any disk errors that might be found in the SS emulated world.
I have been using Edwards ready built 64bit SS based MacOS9 and moved my databases in there from ChubbyBunny where they had been for some years.
I was looking into the sparse bundle and backups of my MacOS9 configuration and noticed there seemed to be some errors, maybe, in the bundle. Working on backups I tried various things to investigate and maybe fix.
First major choice was to do it from within OS9 using a number of Apple or 3rd party tools I have used over the centuries (starting in 19xx). Well I started in host MacOS 10.11 since this is where I want to copy and preserve my data and figure I have the latest tools especially if I end up need AFPS etc in the mix (where i am also making moves towards moving to Mojave if I can assure myself on a few points first...)
I had been moving a fair bit of files around in the OS9 virtual system drive, and it seemed a good idea to look at empty trash and maybe "hdiutil compact" the host sparse image at
/Applications/MacOS9/Mac\ OS\ 9.app/Contents/Resources/Files/MacOS.sheepvm/MacOS9.sparsebundle
(FIRST MAKING SURE SS/MACOS 9 WAS CORRECTLY EXITED)
I got a first worry with the response:
Starting to compact…
Reclaiming free space…
hdiutil: compact failed - internal error
SS/ OS9 still runs up OK... a bit of research leads me to try
hdiutil attach -nomount -noverify -noautofsck <the MacOS9.sparsebundle>
that produced:
/dev/rdisk4s2: fsck_hfs started at Tue Jan 29 12:49:22 2019
/dev/rdisk4s2: /dev/rdisk4s2: ** /dev/rdisk4s2 (NO WRITE)
/dev/rdisk4s2: Executing fsck_hfs (version hfs-305.10.1).
QUICKCHECK ONLY; FILESYSTEM CLEAN
/dev/rdisk4s2: fsck_hfs completed at Tue Jan 29 12:49:22 2019
Not much else going on so run up ElCap's Disk Utility, see the container drive, see the active MacOS9 volume within it and so run Repair/Check on that:
/dev/rdisk4s2: fsck_hfs started at Tue Jan 29 12:52:39 2019
/dev/rdisk4s2: /dev/rdisk4s2: Executing fsck_hfs (version hfs-305.10.1).
/dev/rdisk4s2: ** Checking non-journaled HFS Plus Volume.
/dev/rdisk4s2: The volume name is MacOS9
/dev/rdisk4s2: ** Checking extents overflow file.
/dev/rdisk4s2: ** Checking catalog file.
/dev/rdisk4s2: Invalid BSD file type
/dev/rdisk4s2: Invalid BSD file type
/dev/rdisk4s2: Invalid BSD file type
/dev/rdisk4s2: Invalid BSD file type
/dev/rdisk4s2: Invalid BSD file type
/dev/rdisk4s2: Invalid BSD file type
/dev/rdisk4s2: Invalid BSD file type
/dev/rdisk4s2: Invalid BSD file type
/dev/rdisk4s2: ** Checking multi-linked files.
/dev/rdisk4s2: ** Checking catalog hierarchy.
/dev/rdisk4s2: ** Checking volume bitmap.
/dev/rdisk4s2: ** Checking volume information.
/dev/rdisk4s2: ** Repairing volume.
/dev/rdisk4s2: ** Rechecking volume.
/dev/rdisk4s2: ** Checking non-journaled HFS Plus Volume.
/dev/rdisk4s2: The volume name is MacOS9
/dev/rdisk4s2: ** Checking extents overflow file.
/dev/rdisk4s2: ** Checking catalog file.
/dev/rdisk4s2: ** Checking multi-linked files.
/dev/rdisk4s2: ** Checking catalog hierarchy.
/dev/rdisk4s2: ** Checking volume bitmap.
/dev/rdisk4s2: ** Checking volume information.
/dev/rdisk4s2: ** The volume MacOS9 was repaired successfully.
/dev/rdisk4s2: fsck_hfs completed at Tue Jan 29 12:52:39 2019
Sounds OK but now that copy will not start-up fully, flashing floppy icon and must force quit.
SO MY QUESTIONS?
What is the "best way" to delete files and tidy up / back up the config?
What are the ways and consequences of the various ways of looking at the disk drive?
In the event of corruption / data loss etc what is the best way to move forward?
Thanks for your time and hope this helps more than just myself!