Unmount drive...?

[ADSR]

Trying to test whith DW and TT  got ...impossible to unmount on one  partition...

What's the solution..?


Thanks

GR

[pendragon]

Sometimes a shut down (not restart) will unmount the drive. Or did you do that?

[ADSR]

Yes...i shut down last night.

Today it's the same

GR

[krissel]

Try putting the drive in the list of Spotlight privacy items so it won't be accessed. Are you running DW and TT from a disk or from another partition?

[pendragon]

Is File Sharing turned on?

Also, try booting in to Safe Boot Mode and see if that fixes things.

In Disk Utilities, is your S.M.A.R.T. status (on the unmounted volume) verified? If not, what does it say?

[Xairbusdriver]

If you are NOT running DW or TT from their disks, is the drive you are trying to unmount the boot drive? Whater it is or not, it won't be unmountable as long as anything on it is being used by the OS. It might be difficult to find out what that might be but a Restart in Safe mode (command-S) will at least keep any third party stuff from starting up. Of course, if it's the boot drive, it still can't be unmounted. You must boot from something/anything else.

[ADSR]

Was running from another partition...
Boot in safe mode, after running DU,restart and and could  run DW.
Got directory too severely etc on that partition...gonna run Super duper from another partition( DW ok.)

Thanks very much

GR

[Paddy]

Um...is this the same drive that you've been having trouble with all along? If so, I'd say it's definitely got issues and needs replacement! Don't rely on it as your primary drive.

[Xairbusdriver]

QUOTE

Was running from another partition...

I'm not sure you can "unmount" just a partition if it's on the boot drive. Sounds possible but might not be.

[ADSR]

What i got from DW...

DiskWarrior has successfully built a new directory for the disk named "2 DA OSX  internal." The new directory cannot
replace the original directory because the original directory was too severely damaged.

 Than , that following  text  not in red  but  in green....

All file and folder data was easily located.
 
Comparison of the original and replacement directories indicates that there will be no changes to the number or
contents of files and folders. All files and folders were compared and a total of 8 040 216 comparison tests were
performed.
 
Don't really understand ...is'nt it contradictory???

Thanks

GR
 


 

[tacit]

No contradiction. "All files and folders were easily located" does not necessarily mean the original directory was not badly damaged; only that DiskWarrior was able to unsnarl the damage and there were no crosslinked files. (Crosslinked files make finding file data extraordinarily difficult.)

There are many reasons a disk or partition can not be unmounted. Often, this will happen if fonts or other files are open from the volume you're trying to mount. For example, if you use a font-management program, then clone your drive and boot from the clone, your font-management program will usually try to open your fonts from the original, not the clone.

[Paddy]

Anyway - now that you've discovered that you DO have serious directory problems that DW cannot fix, you will need to erase and reinstall whatever was on this partition. If it has files that aren't backed up anywhere else, then you will need to back them up first of course. Make sure that you select just this partition to erase - I'm assuming that the rest of the partitions on this drive check out ok? You should make sure before you spend any time reinstalling on the bad partition just in case the entire drive has problems.

[ADSR]

Booting from the tested good partition... surfin whith  Firefox, got a kernel panic

Thu Apr  3 02:25:12 2008


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000040010100 PC=0x00000000002D4358
Latest crash info for cpu 0:
   Exception state (sv=0x24342500)
      PC=0x002D4358; MSR=0x00009030; DAR=0x40010100; DSISR=0x40000000; LR=0x0003CA1C; R1=0x0F8DBDB0; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
0x015F9980 0x0003CA1C 0x000A9714
         kmod scan stopped due to missing kmod page: 00000000
Proceeding back via exception chain:
   Exception state (sv=0x24342500)
      previously dumped as "Latest" state. skipping...
   Exception state (sv=0x23AE2C80)
      PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
      Backtrace:
         0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
         kmod scan stopped due to missing kmod page: 00000000
Proceeding back via exception chain:
   Exception state (sv=0x24342500)
      PC=0x002D4358; MSR=0x00009030; DAR=0x40010100; DSISR=0x40000000; LR=0x0003CA1C; R1=0x0F8DBDB0; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
0x015F9980 0x0003CA1C 0x000A9714
         kmod scan stopped due to missing kmod page: 00000000
   Exception state (sv=0x23AE2C80)
      PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)


Could you tell me where should i look to find the  culprit


Thanks


GR

[krissel]

Is this partition on the questionable drive?

What would help is if you could list the makeup of this computer to help get clear in our minds what has been replaced recently and what version of OS is running? I'm confused as to where you are in this upgrade process and can't remember what you have done along the way and what externals you are using.

We have pointed out the drive as being a possible base for these problems. If it is going bad it would be responsible for all kinds of difficulties. Once the drive is ruled out (or replaced) and you have a fresh install of the OS any further panics would lead me to suspect bad RAM.