Trocafish

Q: Mavericks corrupts external hard drive

My WD MyBook studio 2TB (fw800) suddenly shows up empty on my desktop after a Mavericks upfrade on my mid 2009 mbp.

 

Disk Drill is now scanning the WD, and the files are there, about 1,4 TB of it...

 

How do I get the disc structure back?

 

I have no Mountain Lion OS-mac to test the WD in..

 

I had a bootable Mountain Lion on the WD, could that be the problem?

 

In Disk Drill MyBook has four units; EFI(200Mb), MyBook(1,8Tb), Unallocated 128Mb and Lost partition (200Mb)

iOS 7, Ipad mini + ios7

Posted on Oct 24, 2013 1:08 AM

Close

Q: Mavericks corrupts external hard drive

  • All replies
  • Helpful answers

first Previous Page 63 of 99 last Next
  • by mikkibarry,

    mikkibarry mikkibarry Dec 11, 2013 8:14 PM in response to Jasmine Green
    Level 1 (4 points)
    Dec 11, 2013 8:14 PM in response to Jasmine Green

    Thanks.  It's getting better than that now.  I can't reinstall Mavericks on the Mini even after wiping it clean yet again in target mode.  I can select the drive, click through the shrinkwrap agreement, hit install, and nothing happens.  Nothing at all.  The disk again tests out ok.  This time, I'm trying to take screen shots of everything. 

     

    Console says:

    12/11/13 11:13:22.405 PM Finder[186]: CGSCopyDisplayUUID: Invalid display 0x2b28580d

    12/11/13 11:13:22.702 PM Install OS X Mavericks[15473]: Using your own bundle identifier as an NSUserDefaults suite name does not make sense and will not work. Break on _NSUserDefaults_Log_Nonsensical_Suites to find this

    12/11/13 11:13:22.819 PM Install OS X Mavericks[15473]: objc[15473]: Class KeychainMasterHandler is implemented in both /System/Library/PrivateFrameworks/SoftwareUpdate.framework/Versions/A/SoftwareU pdate and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.819 PM Install OS X Mavericks[15473]: objc[15473]: Class PKFolderArchiveSignature is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/PackageKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.819 PM Install OS X Mavericks[15473]: objc[15473]: Class PUKDiskPickerCell is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Frameworks/PackageUIKit. framework/Versions/A/PackageUIKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.819 PM Install OS X Mavericks[15473]: objc[15473]: Class PUKDiskPickerView is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Frameworks/PackageUIKit. framework/Versions/A/PackageUIKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.819 PM Install OS X Mavericks[15473]: objc[15473]: Class _PUKDiskPickerViewOutlineDataSourceAndDelegate is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Frameworks/PackageUIKit. framework/Versions/A/PackageUIKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.819 PM Install OS X Mavericks[15473]: objc[15473]: Class PUKDiskPickerAccessibilityElement is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Frameworks/PackageUIKit. framework/Versions/A/PackageUIKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.819 PM Install OS X Mavericks[15473]: objc[15473]: Class PUKDiskPickerCellAccessibilityElement is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Frameworks/PackageUIKit. framework/Versions/A/PackageUIKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.819 PM Install OS X Mavericks[15473]: objc[15473]: Class PUKDiskPickerGroupAccessibilityElement is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Frameworks/PackageUIKit. framework/Versions/A/PackageUIKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.820 PM Install OS X Mavericks[15473]: objc[15473]: Class PUKDiskPickerHorizontalView is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Frameworks/PackageUIKit. framework/Versions/A/PackageUIKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.820 PM Install OS X Mavericks[15473]: objc[15473]: Class _PUKDiskPickerViewHorizontalDataSourceAndDelegate is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Frameworks/PackageUIKit. framework/Versions/A/PackageUIKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.820 PM Install OS X Mavericks[15473]: objc[15473]: Class PUKHorizontalScrollBar is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Frameworks/PackageUIKit. framework/Versions/A/PackageUIKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.820 PM Install OS X Mavericks[15473]: objc[15473]: Class PUKUniversalPopover is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Frameworks/PackageUIKit. framework/Versions/A/PackageUIKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.820 PM Install OS X Mavericks[15473]: objc[15473]: Class PUKDiskPickerHorizontalCell is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Frameworks/PackageUIKit. framework/Versions/A/PackageUIKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.820 PM Install OS X Mavericks[15473]: objc[15473]: Class PUKPopoverTextController is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Frameworks/PackageUIKit. framework/Versions/A/PackageUIKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.820 PM Install OS X Mavericks[15473]: objc[15473]: Class PUKDiskPickerHorizontalCellAccessibilityElement is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Frameworks/PackageUIKit. framework/Versions/A/PackageUIKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.820 PM Install OS X Mavericks[15473]: objc[15473]: Class PUKDiskPickerHorizontalAccessibilityElement is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Frameworks/PackageUIKit. framework/Versions/A/PackageUIKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.820 PM Install OS X Mavericks[15473]: objc[15473]: Class PUKDiskPickerHorizontalGroupAccessibilityElement is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Frameworks/PackageUIKit. framework/Versions/A/PackageUIKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:22.820 PM Install OS X Mavericks[15473]: objc[15473]: Class PUKDiskPickerHorizontalMatrix is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Frameworks/PackageUIKit. framework/Versions/A/PackageUIKit and /Volumes/Broken *** Mini/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA. One of the two will be used. Which one is undefined.

    12/11/13 11:13:23.769 PM Microsoft Word[91833]: clip: empty path.

    12/11/13 11:13:34.213 PM nobody[15483]: audit warning: closefile /var/audit/20131212040708.20131212041334

    12/11/13 11:13:34.213 PM nobody[15482]: audit warning: allsoft

    12/11/13 11:13:34.213 PM nobody[15484]: audit warning: soft /var/audit

     

    Any ideas?

  • by R C-R,

    R C-R R C-R Dec 11, 2013 8:23 PM in response to PlotinusVeritas
    Level 6 (17,685 points)
    Dec 11, 2013 8:23 PM in response to PlotinusVeritas

    PlotinusVeritas wrote:

    Additionally, as per your earlier comment: "Apparently, the problematic software was the WD Smartware package"       In going thru the WD Smartware documention (below) I find no specific mention of Smartware's capacity for partitioning / reformatting.    Do you have the link for this?

     

    WD Smartware documentation:

    http://www.wdc.com/wdproducts/library/UM/ENG/4779-705057.pdf

    You have linked to the user manual for the 2.0.x version of the WD SmartWare Software for Windows. This is not even the same software that Mac users could install & use, nor is it in any way relevant to the system level components the WD SmartWare package for Macs installs.

     

    But again, it is the executable files in the Mac version of the WD SmartWare installer package that WD changed. These component files contain the only references to the "MyBook" volume name. The reformat cannot come from any other source. Clearly, this was not an intended function of the software; that's the bug the new version was released to eliminate.

     

    You are confusing several different things, some of them not even relevant to any version of OS X.

  • by GetRealBro,

    GetRealBro GetRealBro Dec 11, 2013 8:29 PM in response to GetRealBro
    Level 1 (21 points)
    Dec 11, 2013 8:29 PM in response to GetRealBro

    Background…

    I’m running a clean install of Mavericks on my MBP. The external Seagate 3T was partitioned using Apple’s Disk Utility (GUID partition map with a single Mac OS Extended (Journaled) partition). I’ve already posted the EtreCheck listing — my MBP was/is 3rd party drive software free.

     

    Here’s the picture….

    Diskutility issues.jpg

    And this is it’s  story…

    At 9:57:30 I unmounted the Seagate 3T (with a little whinging about events that arrived after the unmount request)

    At 9:59:33 I attempted to mount the Seagate 3T

    By 9:59:33 the standard fsck_hfs run declared the FILESYSTEM DIIRTY

    At 9:59:33 a 2nd, much longer, fsck_hfs run kicked off

    At 10:01.05 since the drive had not yet mounted, I asked Disk Utility to repair the Seagate 3T*

     

    Disk utility immediately discovered that the Seagate 3T was “busy” and promptly began offering completely bogus information/advice… “Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.”

     

    At 10:07:35 the long  fsck_hfs run completed (approx. 8 min after it started) and announced that “The volume Seagate 3T appears to be OK.” As you can see the Seagate 3T had mounted.  And I might add, Disk Utility’s reports of the data problems on the Seagate 3T were NON-EXISTENT.

     

    The point is that with a clean install of Mavericks, ZERO WD software on my MBP and a disk that had been formatted with Disk Utility. Apple’s very own Mavericks' Disk Utility was so STUPID that it could not even read it’s own log and realize that it was not able to repair the disk because it was BUSY — not damaged. And as a result, Disk Utility went on to provide very dire warnings and completely incorrect advice as to what to do next.

     

    So if Apple’s Mavericks Disk Utility can’t get it right, it is time to quit holding Apple/Mavericks completely blameless.

     

    —GetRealBro

     

    * I didn't bother with verifying the drive because I already knew what would happen. I had run this test several times before with the same results. The only difference this time was that I had the appropriate windows positioned for a photo op.

  • by estApple,

    estApple estApple Dec 11, 2013 8:33 PM in response to GetRealBro
    Level 1 (0 points)
    Dec 11, 2013 8:33 PM in response to GetRealBro

    I am sorry that I have not followed your posts closely. So just a quick comment. Would it possible that you have a damaged disk? Can you try  another disk and see what would happen?

  • by PlotinusVeritas,

    PlotinusVeritas PlotinusVeritas Dec 11, 2013 8:50 PM in response to R C-R
    Level 6 (14,806 points)
    Dec 11, 2013 8:50 PM in response to R C-R

     

    R C-R wrote:

    You have linked to the user manual for the 2.0.x version of the WD SmartWare Software for Windows.

     

    No, if you go to the WD Mac Hardware the USER MANUAL tab to the right will take you to the same PDF file

     

    http://www.wd.com/wdproducts/wdsmartwareupdate/wdsmartware.asp?id=wdfMB_forMac&o s=mac

     

    to>

    http://www.wd.com/wdproducts/wdsmartware/um.asp

    then to>

    http://www.wdc.com/wdproducts/library/UM/ENG/4779-705057.pdf

     

     

    GetRealBro

     

    Get proofs, evidences and logic

     

    Interesting snapshot showing  Executing_fsck_hfs (version hfs-226.1.1)

     

    returning both clean and then dirty

     

     

    However:

    The interesting events in your log at         10:07:35   disk1s3: journal start/end pointers reset!

     

    This is indicative of impending HD hardware failure.

  • by Drew Reece,

    Drew Reece Drew Reece Dec 11, 2013 9:15 PM in response to GetRealBro
    Level 5 (7,659 points)
    Notebooks
    Dec 11, 2013 9:15 PM in response to GetRealBro

    I'm curious about the message that repeated 4 times before the connection, it may be irrelevant, see if it's in the history.

     

    It looks like fsevents is having trouble, which makes me wonder if that puts the disk into a bad state before the remount & subsequent fsck. It looks like it tries to reattach, sees an existing .dls, but can't write to the fseventsd directory. Then it gets the first fsck (DIRTY), so it re-runs without any conclusion? Then it appears to re-start at 10:01:05. When the final fsck finishes the journal start & end points are reset to nothing again (10:07:35).

     

    I wonder what the fsevents 'dls' is? It looks a little like the fsevents log is corrupted before the remount? I guess if the journal has saved these changes it would explain why fsck happens, but only if the journal fails to replay?

     

     

    I just stumbled over this that may help?…

    http://filexray.com/

    When looking for how to enable fsck debug logging. Can you run fsck with the -d flag on this disk?

     

    I must have mentioned this before…

    https://github.com/aburgh or a complied version (on the fugly site)

    http://mac.softpedia.com/progDownload/Disk-Arbitrator-Download-82430.html

     

    It will give you control over what mounts & if it mounts read/write etc.

     

    I think you need to figure out how to put fsck into debug mode or try manually handling the mounting to be able to take this further GetRealBro.

     

    Good work so far

  • by R C-R,

    R C-R R C-R Dec 12, 2013 3:47 AM in response to PlotinusVeritas
    Level 6 (17,685 points)
    Dec 12, 2013 3:47 AM in response to PlotinusVeritas

    PlotinusVeritas wrote:

    No, if you go to the WD Mac Hardware the USER MANUAL tab to the right will take you to the same PDF file

     

    http://www.wd.com/wdproducts/wdsmartwareupdate/wdsmartware.asp?id=wdfMB_forMac&o s=mac

     

    to>

    http://www.wd.com/wdproducts/wdsmartware/um.asp

    then to>

    http://www.wdc.com/wdproducts/library/UM/ENG/4779-705057.pdf

    Nevertheless, that PDF is for WD SmartWare Software version 2.0.x, & on page 1 of that document you will find this:

    OS compat.png

    There is no mention of OS X compatibility anywhere in the document. There are no OS X style windows shown anywhere in its screen shots, only Windows ones. The installation instructions refer to the the system tray portion of the Windows taskbar. There are references to the Window OS, & only to the Windows OS, throughout the document.

     

    Even if you somehow missed the explicit reference to the OS compatibility on page 1, I don't know how you could have failed to notice this is a manual for software that cannot possibly run on any version of OS X.

  • by GetRealBro,

    GetRealBro GetRealBro Dec 12, 2013 6:42 AM in response to GetRealBro
    Level 1 (21 points)
    Dec 12, 2013 6:42 AM in response to GetRealBro

    @estApple

     

    One of the partitions on one of my other 5 (1.5-4T) Seagates exhibited the same symptoms while I was cleaning them up. Once I retrieved the data off of it (using the Finder), I re-partitioned it. These Seagate drives were used on our iMac or my MBP (for a year or so each) for Time Machine and then stored in a file cabinet as archives.

     

    This particular Seagate 3T was purchased in Oct 2012 and has been lightly used for Time Machine on my MBP running 10.6.8 prior to Mavericks. This means that it was only attached/running a few times a week for less than an hour, but it is still possible that the disk is failing.

     

    I'm not interested in testing any of my other drives. Two are our current Time Machine drives. The others are stored as archives.

     

    @pv

     

    What transpired between the clean and dirty fsck runs was a file copy (a 4+GB iPhoto library) followed by a dismount.

     

    I have reproduced these long fsck runs many times now. The entries in the system log just prior to the long fsck runs are NOT consistent. In particular, the resetting of journal start/end pointers is not common. Note: at the time of this log/screen-capture I had not placed this Seagate 3T into Spotlight's privacy panel. Since then it has been much harder to reproduce the long fsck_hfs runs.

     

    @Drew Reece

     

    The last message that was repeated 4 times was…

    “xxxx-MacBook-Pro kernel[0]: Sandbox: mdworker(15615) deny file-read-data /Volumes/Data/Images/iPhoto Libraries/iPhoto Library 2013/Contents/PkgInfo”

     

    This is a common message when I copy an iPhoto library. Note: I keep as much data as possible OFF of my boot partition. So nearly all of my "data" is on a separate partition named Data. This is where the iPhoto library that I was copying was located.

     

    "Then it gets the first fsck (DIRTY), so it re-runs without any conclusion? Then it appears to re-start at 10:01:05. When the final fsck finishes the journal start & end points are reset to nothing again (10:07:35)."

     

    This is what the fsck_hfs log always looks like when I ask Disk Utility to verify and/or repair a disk while fsck is already running. The fsck that Disk Utility kicks off shows up in the middle of the log of the already running fsck separated by blank lines.

     

    @all

     

    As interesting as these details are, they obscure a simple fact. Regardless of what is causing these long fsck_hfs runs, Apple’s own Disk Utility fails to recognize that fsck is already running and gives out very bad advice “Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.” It is not too big a stretch for me to think that when the WD software encountered the same/similar conditions it took matters into its own hands and reformatted the disk thinking that it was not repairable. Unforgivable - yes, unthinkable - maybe not.

     

    —GetRealBro

  • by estApple,

    estApple estApple Dec 12, 2013 6:54 AM in response to GetRealBro
    Level 1 (0 points)
    Dec 12, 2013 6:54 AM in response to GetRealBro

    The startup disk in my iMac failed several months ago (a well known problem for that batch of iMac). When I ran Disk Utilities, I got the same error message. Eventually, I replaced it with a SSD.

  • by GetRealBro,

    GetRealBro GetRealBro Dec 12, 2013 7:06 AM in response to estApple
    Level 1 (21 points)
    Dec 12, 2013 7:06 AM in response to estApple

    estApple wrote:

     

    The startup disk in my iMac failed several months ago (a well known problem for that batch of iMac). When I ran Disk Utilities, I got the same error message. Eventually, I replaced it with a SSD.

    I had always trusted Disk Utility. After Mavericks, I'll be checking various system logs to see if Disk Utility got it right. The loss of innocence has been painful

     

    ---GetRealBro

  • by R C-R,

    R C-R R C-R Dec 12, 2013 8:13 AM in response to GetRealBro
    Level 6 (17,685 points)
    Dec 12, 2013 8:13 AM in response to GetRealBro

    GetRealBro wrote:

    This is what the fsck_hfs log always looks like when I ask Disk Utility to verify and/or repair a disk while fsck is already running. The fsck that Disk Utility kicks off shows up in the middle of the log of the already running fsck separated by blank lines.

    That sounds like a bug in Disk Utility in Mavericks. Since it is repeatable (right?) I suggest that you submit it to Apple using http://www.apple.com/feedback/macosx.html, or through the developer bug reporter if you have an Apple developer connection account.

  • by PlotinusVeritas,

    PlotinusVeritas PlotinusVeritas Dec 12, 2013 9:21 AM in response to GetRealBro
    Level 6 (14,806 points)
    Dec 12, 2013 9:21 AM in response to GetRealBro

     

    GetRealBro wrote:

     

    This is what the fsck_hfs log always looks like when I ask Disk Utility to verify and/or repair a disk while fsck is already running. The fsck that Disk Utility kicks off shows up in the middle of the log of the already running fsck separated by blank lines.

     

    Apple’s own Disk Utility fails to recognize that fsck is already running and gives out very bad advice......

     

    It is not too big a stretch for me to think that when the WD software encountered the same/similar conditions it took matters into its own hands and reformatted the disk thinking that it was not repairable. Unforgivable

     

    I believe you and that fits my conclusion about this issue.

     

    *Also why on earth is fsck being run on a mounted partition?

          As developers and people know doing so is a premise for disaster as Apple indicates in documentation (see below) and developers (see below comments from same)

     

       I never believed that the WD-ware was all on its own and by its own accord 'stepping up' and doing this entirely on its own, nor did it logically fit.  Mostly to blame yes, to be sure.

     

     

     

    For process of elimination can / did you recreate this on another ext. HD?

     

    Your log states:

    10:07:35   disk1s3: journal start/end pointers reset!

    This is indicative of impending HD hardware failure.

                .......However its just as, if not more believable that this was spit out from a faulty fsck check which is/was corrupt.

     

     

    developers indications on fsck on mounted volumes

    *It's well-known that you should never fsck a mounted partition. I can understand how this could easily lead to corruption if the filesystem is written to by fsck

     

    *When running the fsck command, you should always unmount the filesystem first. This will reduce the chances of any corruption occurring.

     

    *Also take care not to fsck a mounted file system, even root, as you may do more damage to the file system than you intended to correct. Fsck'ing a clean file system does nothing for you other than give you peace of mind. Usually inconsistencies are created when the system is not properly shutdown, such as a power failure or reset. 

     

     

    Apple:

    If you do run fsck, it is best if you use -n and -f flags so that it will not actually modify the volume.

        Because running fsck to repair a file system which is mounted for read/write operations can potentially cause severe data corruption or loss, the file system is normally checked while unmounted, mounted read-only, or with the system in a special maintenance mode that limits the risk of such damage

  • by Drew Reece,

    Drew Reece Drew Reece Dec 12, 2013 1:31 PM in response to PlotinusVeritas
    Level 5 (7,659 points)
    Notebooks
    Dec 12, 2013 1:31 PM in response to PlotinusVeritas

    PlotinusVeritas wrote:

    I believe you and that fits my conclusion about this issue.

     

    *Also why on earth is fsck being run on a mounted partition?

          As developers and people know doing so is a premise for disaster as Apple indicates in documentation (see below) and developers (see below comments from same)

     

       I never believed that the WD-ware was all on its own and by its own accord 'stepping up' and doing this entirely on its own, nor did it logically fit.  Mostly to blame yes, to be sure.

     

     

    Apple:

    If you do run fsck, it is best if you use -n and -f flags so that it will not actually modify the volume.

        Because running fsck to repair a file system which is mounted for read/write operations can potentially cause severe data corruption or loss, the file system is normally checked while unmounted, mounted read-only, or with the system in a special maintenance mode that limits the risk of such damage

     

    @PlotinusVeritas, how do you know that GetRealBro's partition was mounted?

     

    The first two fsck's are also run in (NO WRITE) mode which seems reasonable before mounting a disk. It's only after that returns a dirty filesystem that it begins to attempt a repair (that seems to splinter into 2 jobs).

     

     

    @GetRealBro, thanks for the extra log text, you were right to leave that out

    I wonder why it starts another fsck during the catalog repair. I agree with you I still can't see how this would effect an entire disk.

     

    I'd also consider unloading disk arbitration & manually fscking via the Terminal. It may indicate if the issue is coming from Disk Utility or the disk frameworks. You know how to do this?

     

    Also see if Disk Utilities debug menu helps… Quit it & run

    defaults write com.apple.DiskUtility DUDebugMenuEnabled 1

     

    Enable the all messages in the 'Debug > Debug Message level' & see what appears in the log.

  • by GetRealBro,

    GetRealBro GetRealBro Dec 12, 2013 3:11 PM in response to Drew Reece
    Level 1 (21 points)
    Dec 12, 2013 3:11 PM in response to Drew Reece

    Drew Reece wrote:

     

    @PlotinusVeritas, how do you know that GetRealBro's partition was mounted?

     

    The first two fsck's are also run in (NO WRITE) mode which seems reasonable before mounting a disk. It's only after that returns a dirty filesystem that it begins to attempt a repair (that seems to splinter into 2 jobs).

    Disk Utility usually dismounts a drive before it does a Verify or Repair operation (AKA fsck_hfs). But in these cases, the Seagate 3T has not yet mounted. So Disk Utility goes ahead with it's Verify or Repair fsck run despite the fact that a fsck run is already happening. In these cases Disk Utiity never mounts the disk becuse it mistakenly believes that the disk is un-repairable. The disk only mounts AFTER the long fsck_hfs run completes. That is the time of the screen shot I posted.

     

    This whole fsck dance is very repeatable once the drive fails to mount and the long fsck_hfs run kicks off. The only part that takes fiddeling/chance is getting the Seagate to fail to mount. As I've posted preivously, my test routine is to copy a large iPhoto library to the Seagate 3T and then unmount it using the Finder "eject" (ctrl click) or Disk Utility Unmount button.

     

    --GetRealBro

  • by GetRealBro,

    GetRealBro GetRealBro Dec 12, 2013 6:36 PM in response to PlotinusVeritas
    Level 1 (21 points)
    Dec 12, 2013 6:36 PM in response to PlotinusVeritas

    PlotinusVeritas wrote:

    ...

    For process of elimination can / did you recreate this on another ext. HD?

    ...

    Only one other partition, on one of the 6 Seagates I was cleaning up, failed to mount. Once I got the data off it (via the Finder) I reformatted it as Disk Utility suggested. At the time I thought I had been very lucky. That was before I realized that Disk Utility has a nasty habit of not telling the truth about the condition of drives that fail to mount. The trouble with diagnostic software like Disk Utility is that once you've caught it repeatedly fibbing on one issue, you begin wondering just exactly when you can trust it.

     

    I'm only testing with this remaining Seagate 3T drive because I have already retrieved all the data via the Finder. And I don't need this drive for awhile. FWIW I think the reason the mounting problem is so easy to recreate on this drive is because it is connected via FW800, has a relatively large single partition (3TB) and it has several large/complex directory structures: a Time Machine backup and now 13 4-12GB iPhoto libraries.

     

    Tomorrow I'll remove the drive from Spotlight's Privacy panel to see If the frequency of mounting issues returns/increases to the previous levels.That might prove interesting.

     

    ---GetRealBro

first Previous Page 63 of 99 last Next