Hello everybody, I found out that it was a problem in the catalog after all - it makes absolutely no difference whether I set kHFSVolumeUnmountedBit or clear it in my case.
What surprises is that the error wasn't even in the root index node but at a lower level index node - I'm surprised that the system hung instead of giving me an error dialog as was the case with HFS... but anyway... I'm glad this didn't happen before with HFS too otherwise I would have had a tough time locating the errors.
Btw this also solves the problem I referred to in my email of 11.04 to the list so nobody needs to take a look at my image (not that someone wanted to anyway :-)
Regards, Nandini
----- Original Message ----- From: Entwicklung To: hfs-user@lists.mars.org Cc: studentdev@lists.apple.com Sent: Thursday, April 18, 2002 8:55 AM Subject: [hfs-user] HFS+ volumes : kHFSVolumeUnmountedBit
Hello Listers, The HFS+ tech. notes say that the 'Volume attributes' field in the volume header has to have Bit 8 set to 1 if the volume was correctly flushed when it was mounted or ejected the last time. It also mentions that if this is not done it could take an annoyingly long time for the ROM-based consistency check (on Mac OS 7.6 and higher) for boot volumes.
1) My volume is not a boot volume. 2) I have cleared this bit - set it to 0 3) Inspite of 1) and 2) a smaller HFS+ volume with only one index node = root gets mounted pretty fast. 4) A larger HFS+ volume (2 levels of index nodes) doesn't get mounted at all... my iMac with MacOS 9 just hangs altogether..... I have to remove my CD by force and restart.
I assumed this couldn't be an error in the catalog but has something to do with the Volume Header since I would have expected to see an error dialog instead. Besides this seems to be HFS+ specific since I never encountered this kind of problem with HFS.
Does anyone know what this could be due to ? Any suggestions/comments would be greatly appreciated.
Regards, Nandini Hengen