What is Disk Utility parameter : 'Owners Enabled' about?

There is a parameter in the Disk Utility dialogue window , bottom left corner that says (on mine) Owners Enabled: No.  What does that signify and how, where or why is it set?

That parameter can be set manually in the getInfo window of the drive itself (in Finder, not inside Disk Utility). See if this adds any insight:
PH10670- OS X Mountain Lion: If you don’t have permission to use a disk

Similar Messages

  • Disk Utility Shows "Owners Enabled: No" Even When it *Is* Enabled

    I have an external AoE (Coraid) disk array that I have mounted to an XServe machine using OS X 10.6.8 Server.  I was having frustrating problems with file ownerships going away, until I figured out that it was due to ownership being disabled on this drive, which is the default for external drives.
    So, I used Finder | Get Info and unchecked the "Ignore ownership on this volume" checkbox.  That seems to have fixed the problem, and ownership is now preserved on this volume.  I checked with diskutil as well, as it also confirms that ownership is enabled.
    However, even after rebooting the machine, Disk Utility (the GUI) still says, "Owners Enabled: No" for this volume.  Absolutely nothing I can think to do will make Disk Utilty stop claiming that ownership is not enabled.  I even used diskutil to disable and then re-enable ownership.  Everything *seems* to be working, but this is still a concern.  Is it a bug in Disk Utility?
    The volume's filesystem, btw, is Mac OS Extended (Case-sensitive, journaled).

    Well, the volinfo.database is fine. You might check the system.log and the asl.log for any entries about diskarbitrationd but I have a feeling you won't find anything. You could double post over in the Server forum or over at MacOSXHints- has a bunch of server admins who visit there frequently.

  • How to make a bootable flash drive Disk Utility's "Owners Enabled" function

    Being as Apple does not have a discussion group for this wonderful little utility and because Apple has neglected to fix the "Post New Topic" link in the "Special Interest Area>User Tips Library", I have no choice but to post here. I think what I found is useful and I have accomplished it in a way that avoids the need of using the disheartening Terminal.
    How to create a bootable flash drive:
    Step 1: Obtain a flash drive (e.g., 8GB USB flash SanDisk), OS cd

    and because Apple has neglected to fix the "Post New Topic" link in the "Special Interest Area>User Tips Library", I have no choice but to post here.
    http://discussions.apple.com/message.jspa?messageID=10672620#10672620

  • What does Disk Utility mean by saying the back up disk cannot be unmounted?

    Disk utility has been giving me that error and I get about the same message when Time Machine attempts to do a back up as well. What does it mean?

    Hi! When you try to do a repair on a disk it "unmounts" (removes it from the desktop) (which locks the directory) so it can be repaired. Unmounting also is required for an erase. Time Machine shouldn't be trying to unmount it for a backup in fact it could write to it if it unmounts. Tom

  • What is disk utility for?

    what is the function of disk utility under application? can someone tell me how to use it?

    The hatter wrote:
    It is used to format drives, repair permission, and has some ability to repair disk errors, though most go with Disk Warrior.
    I think thats a very brief summary of what DU can do, and I'd advise you to check the OSX Help for more DU usages. I'd write that DU can also: repair start-up disk, get info on a disk or volume, create a RAID HD array, SMART-based diagnostic for HD failure, transfer or back-up data as a disk image, burn a CD or DVD, protect info on removable media, see contents on disk image, erase and secure erase a disk/volume... etc
    I don't think most Mac users head straight to DW either. I may be guessing but I reckon most simply let their Macs run and run using Leopard with no care at all for file system maintenance. Nonetheless DW is useful third-party utility for some forms of file system repair, though many only bother with it if DU or other means of OS X trouble shooting haven't sorted out the issue first.

  • What is disk utility, what is used for?

    What is disk utlity, & what it used for?

    It is used for a variety of things, including disk repair (if the data structures that keep track of data on the disk get corrupted), repair of permissions on the system files if they get messed up, erasing and partitioning disks, etc.  As Linc points out, Disk Utility's help can give you all the details.  Note that some things cannot be done to the system drive unless you start up from a different drive.
    Also, note that if you're asking because you're deleting apps that you don't use, you really shouldn't do that with the preinstalled Apple apps, even if you think you don't have a use for them.  Sometimes deleting them can have unexpected side effects, and you never know when you might need such an app.

  • What does disk utility really do ?

    I downloaded a lion 10.8 dmg from internet and wanted to make a installation portable disk.
    And when I loaded the dmg, and used the 'disk utility' to restore installation files to one of my disk partitions, it just failed. And what is real annoying is that I got my disk partitions after the partition lost. And I can't get my important files back.
    Maybe the 'disk utility' want to change the partition to be bootable and made the partition tables damaged.
    Hope someone can help me to repair the disk and make the disk utility more secure !

    varjak paw wrote:
    There is no DMG of Lion, at least not anything legal. From where did you get this file?
    Well there is a DMG of both Lion and Mt Lion. But it is included in the Lion/Mt Lion OS X Install.app package files and can be copied out.
    But that is Not the Operating System. It is the Install files for the operating system. Restoring that DMG would, supposedly, give you bootable media for installing the OS on a drive.
    To the OP I have found that the Restore feature/function in Disk Utility doesn't always work as expected. Best thing to do is use this program for creating a Dual Layer DVD or USB thumb of the Mt Lion install files. It works every time.
    Make the USB thumb as most of the, Not So, Superdrives can't really write to Dual Layer DVDs. You will be very lucky if you have a Superdrive that will actually write to Dual Layer DVDs.

  • Why is Disk Utility "Permissions" only enabled on system drive?

    Hi,
    Shouldn't Disk Utility's "Verify Permissions" and "Fix Permissions" be enabled for all mounted volumes? Including disk images? Same with "Verify Disk" and "Repair Disk".
    I'm seeing them enabled only for the system drive.
    Thank you,
    Don

    Shouldn't Disk Utility's "Verify Permissions" and "Fix Permissions" be enabled for all mounted volumes? Including disk images?
    When Apple (and some third-party) software is installed, data is written in the Receipts folder incuding file permissions. Disk Utility uses this information to verify and repair permissions. There is no such information for other files or drives.
    Same with "Verify Disk" and "Repair Disk".
    They should work for other drives.
    I'm seeing them enabled only for the system drive.
    Are you using an administrator account?

  • Owners Enabled if Off, How do I turn it On?

    Using OS 10.4.8. G4 450, with two internal drives. I cannot write to the second drive, and Disk Utility indicates "Owners Enabled Off". How do I reverse this? In an earlier post someone had suggested the following:
    "More than likely your /private/var/db/volinfo.database is corrupt. There's a bug in Tiger where two volumes will be referenced on the same line. You could try to manually edit the file. Or you can remove the file in single user mode. Then reboot. Also see vsdbutil -h"
    If this is correct could someone please walk me through step by step on how this is accomplished?
    Thanks
    Powermac G4 450   Mac OS X (10.4.8)   1.5 G ram

    By opening an App that uses it. Something like Photobooth.

  • SDHC Card not recognized in finder but shows up in disk utility.

    I have an SDHC card that I can only find in the disk utility. When I try to verify it won't. It also won't let me try to restore it.
    Info:
    Macbook Pro
    Mac OS X 10.7.4
    32 GB SDHC
    I have also tried this on a 24" iMac that is also 10.7.4 with the same problem.

    Very bad.
    If select the SDHC card in Disk Utility, what does Disk Utility have to say about it?
    Allan

  • Disk Utility - Erase Free Space-what does it really do?

    Hey Forum,
    I am using mac os 10.6.4 on my macbook and i have a doubting question for quite sometimes, what does disk utility erase free space feature really do? Does it gives you more free space? or what? I know it prevents the recovery of deleted files but i want to know what more it does and do not do? Like, now my hdd free space kept increasing and decreasing, by a few 100 mbs or 50mbs etc, so do i erase free space so to solve this problem? Ok, i do not only want to know does it solve the previous problem, but also the questions stated in the whole long paragraph i have wrote. If you know anything related to disk utility's erase free space, feel free to tell me!
    Pls help me, I need you guys' help!
    Thank you.
    Regards
    Ala.

    Erase free space simply writes zeros over the space occupied by deleted files to prevent data recovery. That's all it does. It does not give you extra disk space.
    Your disk space goes up and down a bit because the system creates temporary files and logs which take up space, such as the Safari cache. You can clear these file using a utility like Onyx (which is free)

  • How do I undo BC Partition repair in disk utility?

    Here's the summary:
    8-core MacPro2,1 running 10.6.8, Paragon NTFS for Mac, Bootcamp Win7.
    4 internal HDD drives: two 1.5TBs for data, one 1TB for MacOS, one 1.5TB for Win7 bootcamp.
    I mostly use the Mac side for music production (but rarely), and the Win side for business and everything else. Scores and scores of Win apps installed over the years. [4 monitor system], well over 500K files on the drive.
    I just backed up the data from the two data-only drives, and made a bootable clone of the MacOS drive (SuperDuper). I have never successfully been able to clone the Win7 Bootcamp NTFS drive (even with Winclone back in 2009) because of volume sizes (or something). I decided to try again, from WITHIN Windows this time (all other attempts were from the Mac OS side).
    I bought, downloaded, and installed Acronis True image from within the Win7 bootcamp system. [I obviously did not know that it was gonna modify my MBR, and I had no idea at the time that the GPT and MBR areas were somehow 'mingled' on a bootcamp drive.]
    So, when I performed the Acronis-requested reboot (my default boot is into the Bootcamp/Win7 drive), it failed to boot and requested some Windows recovery media or something. I was concerned that anything i put in the DVD drive would sabotage my priceless (in retrospect) stable/optimized Win7 bootcamp system. So, i just hard-powered down the Mac and tried to restart.
    I did the Alt/option key, and i was presented with the Mac or Win drive icons. I selected Win, and then I got a different boot error message--'no MBR found'.
    But this time i realized that Acronis had stepped where it shouldn't have, and I figured the Mac side could fix the boot problem (maybe with bootcamp assistant or something).
    If i had stopped THERE, and searched the forums i could have found how to fix THAT problem--that has been answered tons of times…
    But, instead, i went to Disk Utility and asked it to repair my Bootcamp partition (I have Paragon NTFS and it has worked for years, and so I did not have a reason to doubt Disk Utility's ability to Repair an NTFS volume--not that i have tried it before, of course).
    Disk Utility repair ran for about 10-15 minutes and said it fixed about 10-20 things.
    The drive information (in the side bar and below) still had the BOOTCAMP partition, reported that it was NTFS, said that there was 308 GB still available of the 1.5TB drive, and that it contained 1.19TB 'used'. Looked normal to me.
    I closed Disk Utility and then opened a Finder window to see if DU left any 'artifacts' of its 'fixes' on the BOOTCAMP partition, and all the files were gone! Even though DU said it had 1.19TB 'used', all of my files are gone. [I rebooted also, to verify that it was not some 'delayed reporting' issue.]
    When I enable 'hidden files' to show, what I get on the Bootcamp partition are these three entries:
    .DS_Store (16KB), .fseventsd folder (with a 1KB UUID file inside it), and a .Trashes folder with zero KB.
    At this point, I panic and assume the position of despair. There is no 'undo' key for the D/U that I can find. I do an orderly shut down of the system, physically remove the Win7 BC drive, and make/verify a sector-by-sector clone of the drive (on a Win7 laptop, using Acronis--22 hours).
    In Win7 Disk Management, the GPT partition (on the original drive) shows up and the BOOTCAMP partition shows up--with the proper size--but windows does NOT recognize the partition as being NTFS. It reports it as being RAW and 'urges' me to format it (yeah, right…).
    So, I place the sector-by-sector duplicate back into the Mac, boot up (only the Mac OS is given as an option), and am ready to 'work on' recovering the Win7 BC partition (if possible).
    I am avoiding trying to fix the booting problem, because recovery of the 1.2TB of a working system is much more critical for me.
    The clone HDD reports the same in DU, except now the GPT partition shows up as greyed-out 'disk1s1', right above the "BOOTCAMP" partition in the sidebar. [I understand from researching this that disk1s1 is somehow related to the bootloader for BC?]
    I used the demo version of Data Rescue 3 to scan for recoverable files from the drive, but it doesn't even report the .files. (I am running the deep scan now, but will take about another 9 hours to complete that).
    Has anybody got any suggestions on how to reclaim this partition and its system?
    Here are a couple of other details from diagnostic tools:
    Model Name:    Mac Pro
      Model Identifier:    MacPro2,1
      Processor Name:    Quad-Core Intel Xeon
      Processor Speed:    3 GHz
      Number Of Processors:    2
      Total Number Of Cores:    8
      L2 Cache (per processor):    8 MB
      Memory:    13 GB
      Bus Speed:    1.33 GHz
      Boot ROM Version:    MP21.007F.B06
    newmac:~ gmmx2$ sudo gpt -r show disk1
           start        size  index  contents
               0           1         PMBR
               1           1         Pri GPT header
               2          32         Pri GPT table
              34      262144      1  GPT part - E3C9E316-0B5C-4DB8-817D-F92DF00215AE
          262178        2014        
          264192      409600      2  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
          673792  2929602560      3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
      2930276352         783        
      2930277135          32         Sec GPT table
      2930277167           1         Sec GPT header
    newmac:~ gmmx2$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.0 TB     disk0
       1:                        EFI                         209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            999.9 GB   disk0s2
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.5 TB     disk1
       1:         Microsoft Reserved                         134.2 MB   disk1s1
       2:                        EFI                         209.7 MB   disk1s2
       3:       Microsoft Basic Data BOOTCAMP               1.5 TB     disk1s3
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.5 TB     disk2
       1:                        EFI                         209.7 MB   disk2s1
       2:                  Apple_HFS D3                      750.0 GB   disk2s2
       3:       Microsoft Basic Data DATA3                  749.9 GB   disk2s3
    /dev/disk3
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     FDisk_partition_scheme                        *1.5 TB     disk3
       1:               Windows_NTFS SSDSUB                 1.5 TB     disk3s1
    [Disk 1 is obviously the BC one]
    newmac:~ gmmx2$ sudo fdisk /dev/disk1
    Password:
    Disk: /dev/disk1    geometry: -5415437/4/63 [-1364690128 sectors]
    Signature: 0xAA55
             Starting       Ending
    #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
    1: EE    0   0   2 - 1023 254  63 [         1 - -1364690129] <Unknown ID>
    2: 00    0   0   0 -    0   0   0 [         0 -          0] unused     
    3: 00    0   0   0 -    0   0   0 [         0 -          0] unused     
    4: 00    0   0   0 -    0   0   0 [         0 -          0] unused     
    I cannot be the only one who has much such a catastrophic error, so I am hoping that there is something I have overlooked (being only a part-time Mac user) or there is some utility somewhere which can fix this--
    Or if you need more data, let me know...
    thank you for your time--gmm

    Additional information: I found the DU Repair log for that session, in case it helps:
    2013-01-28 04:31:00 -0700: Disk Utility started.
    2013-01-28 04:31:30 -0700: Verify and Repair volume “BOOTCAMP2013-01-28 04:31:30 -0700: Starting repair tool:
    2013-01-28 04:31:30 -0700: Verifying files...                                                            
    2013-01-28 04:31:57 -0700: Adjusting instance tags to prevent rollover on file 0x606f0.                  
    2013-01-28 04:31:57 -0700: Adjusting instance tags to prevent rollover on file 0x606f2.                  
    2013-01-28 04:31:57 -0700: Adjusting instance tags to prevent rollover on file 0x606f4.                  
    2013-01-28 04:32:01 -0700: Files verification completed.                                                 
    2013-01-28 04:32:01 -0700: Verifying meta files...                                                       
    2013-01-28 04:32:01 -0700: Meta files verification completed.                                            
    2013-01-28 04:32:01 -0700: Veryfing $AttrDef.                                                            
    2013-01-28 04:32:01 -0700: Veryfing $Boot.                                                               
    2013-01-28 04:32:01 -0700: Verifying $UpCase.                                                            
    2013-01-28 04:32:01 -0700: Correcting $UpCase data.                                                      
    2013-01-28 04:32:01 -0700: Verifying $LogFile.                                                           
    2013-01-28 04:32:01 -0700: Verifying $Volume.                                                            
    2013-01-28 04:32:02 -0700: Verifying files with EAs...                                                   
    2013-01-28 04:32:02 -0700: EAs verification completed.                                                   
    2013-01-28 04:32:02 -0700: Verifying folders...                                                          
    2013-01-28 04:41:54 -0700: Folders verification completed.                                               
    2013-01-28 04:41:54 -0700: Minor inconsistencies are detected on the volume.                             
    2013-01-28 04:41:54 -0700: Creating root directory                                                       
    2013-01-28 04:41:54 -0700: Verifying security descriptors...                                             
    2013-01-28 04:41:54 -0700: Clearing invalid security descriptor 0x25e                                    
    2013-01-28 04:41:54 -0700: Clearing invalid security descriptor 0x260                                    
    2013-01-28 04:41:54 -0700: Clearing invalid security descriptor 0x797                                    
    2013-01-28 04:41:54 -0700: Clearing invalid security descriptor 0x1538                                   
    2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SII entry 0x25e                                     
    2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SII entry 0x260                                     
    2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SII entry 0x797                                     
    2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SII entry 0x1538                                    
    2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SDH entry Id=0x797                                  
    2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SDH entry Id=0x25e                                  
    2013-01-28 04:41:55 -0700: Deleting orphan $Secure::$SDH entry Id=0x260                                  
    2013-01-28 04:41:55 -0700: Deleting orphan $Secure::$SDH entry Id=0x1538                                 
    2013-01-28 04:41:55 -0700: Verifying files security...                                                   
    2013-01-28 04:41:55 -0700: Record 0x97c contains invalid security Id (0x260)                             
    2013-01-28 04:41:55 -0700: Record 0x99b contains invalid security Id (0x260)                             
    2013-01-28 04:41:55 -0700: Record 0xb88 contains invalid security Id (0x260)                             
    2013-01-28 04:41:55 -0700: Record 0xb91 contains invalid security Id (0x260)                             
    2013-01-28 04:41:55 -0700: Record 0xb92 contains invalid security Id (0x260)                             
    2013-01-28 04:41:55 -0700: Record 0x5633 contains invalid security Id (0x260)                            
    2013-01-28 04:41:55 -0700: Record 0x5635 contains invalid security Id (0x260)                            
    2013-01-28 04:41:55 -0700: Record 0x5637 contains invalid security Id (0x260)                            
    2013-01-28 04:41:57 -0700: Record 0xe1d4 contains invalid security Id (0x25e)                            
    2013-01-28 04:41:57 -0700: Record 0xe1d5 contains invalid security Id (0x25e)                            
    2013-01-28 04:41:57 -0700: Record 0xe1d6 contains invalid security Id (0x260)                            
    2013-01-28 04:41:58 -0700: Record 0x111c9 contains invalid security Id (0x260)                           
    2013-01-28 04:41:58 -0700: Record 0x111ca contains invalid security Id (0x260)                           
    2013-01-28 04:41:58 -0700: Record 0x111cb contains invalid security Id (0x260)                           
    2013-01-28 04:41:58 -0700: Record 0x111dc contains invalid security Id (0x260)                           
    2013-01-28 04:41:58 -0700: Record 0x11285 contains invalid security Id (0x260)                           
    2013-01-28 04:41:58 -0700: Record 0x11297 contains invalid security Id (0x260)                           
    2013-01-28 04:41:58 -0700: Record 0x113c4 contains invalid security Id (0x260)                           
    2013-01-28 04:41:58 -0700: Record 0x113c5 contains invalid security Id (0x260)                           
    2013-01-28 04:41:58 -0700: Record 0x12528 contains invalid security Id (0x260)                           
    2013-01-28 04:42:00 -0700: Record 0x1cfe2 contains invalid security Id (0x260)                           
    2013-01-28 04:42:00 -0700: Record 0x1dce1 contains invalid security Id (0x260)                           
    2013-01-28 04:42:00 -0700: Record 0x1f6a8 contains invalid security Id (0x260)                           
    2013-01-28 04:42:00 -0700: Record 0x1f6a9 contains invalid security Id (0x260)                           
    2013-01-28 04:42:00 -0700: Record 0x1f6c4 contains invalid security Id (0x260)                           
    2013-01-28 04:42:00 -0700: Record 0x21d57 contains invalid security Id (0x797)                           
    2013-01-28 04:42:03 -0700: Record 0x3220d contains invalid security Id (0x260)                           
    2013-01-28 04:42:06 -0700: Record 0x4bc2a contains invalid security Id (0x260)                           
    2013-01-28 04:42:10 -0700: Record 0x64ff9 contains invalid security Id (0x1538)                          
    2013-01-28 04:42:11 -0700: Can't read $SDS                                                               
    2013-01-28 04:42:12 -0700: Security verification completed                                               
    2013-01-28 04:42:12 -0700: Verifying $MFT.                                                               
    2013-01-28 04:42:12 -0700: Verifying $MFTMirr.                                                           
    2013-01-28 04:42:12 -0700: Verifying $Bitmap.                                                            
    2013-01-28 04:42:18 -0700: Volume repair complete.
    2013-01-28 04:42:18 -0700: Updating boot support partitions for the volume as required.
    2013-01-28 04:42:18 -0700: Repair tool completed: 2013-01-28 04:42:18 -0700:
    2013-01-28 04:42:18 -0700:

  • How do you change 'Owners Enabled' to "No" on an installed Hard drive?

    I recently installed a third drive in my Mac pro and after adjusting permissions the users on the machine can read and write their own files, but not anyone else's. I noticed that within Disk Utility, the parameter 'Owners Enabled' is set to 'Yes' so I assume I need it set to 'No' so that anyone can do anything to any file on that drive. Trouble is I don't know how to do it. Thanks in advance for the help! Much appreciated.

    You're welcome! And thank you for the !
    Happy holidays!

  • Disk Utility errors: No such file -or- No space left on device (50GB+ free)

    I am trying to make an image out of a _NTFS formatted_ parition, using around 4,5GB of data, of a freshly installed Windozs. It's for debugging tons of machines I have been given (to debug..) and I need an image done. Note that debating if using an image as a solution is good or not is not the point of this thread.
    When I try to make a new image out of the parition (clicking "New Image"), using the defaults settings, I enter my admin pass, then I'm being shown "No space left on device". Wierd. The device I am writing the image onto has 51GB left, and the Trash is emptied.
    I tried changing the image format to all the possible types in Disk Utility, but I get the same error: No space left on device.
    I then changed the device, this time I used a volume with 10GB free on it. Then, I only managed to get a standard DMG compressed image, where I need a "DVD/CD master" one. I'm still confused, because no other image type worked.
    Then I tried making a new image (not from a disk or volume, empty) and then just copy data to it (I'm sure it's really not the way to go, but still). After creating the empty image (I opted for an 8GB, DVD burnable style, "DVD/CD master"), I got the wierd error: No such file (straigth after the image creation, in Disk Utility).
    More info about volumes and stuff:
    Data to be imaged:
    A single partition on a volume (connected with IDE to Mac Pro, but I don't see why it would matter)
    Where I can save it:
    I got a big bunch of volumes right here, internally.
    I tried one with 50GB free, but failed. Another one, on another disk, with 10GB, but failed.
    Also, this error comes often in Disk Utility and other unix OS I think, and mostly for no real known reason (in OS X), as most issues I found were still unresolved.
    Thanks for any help

    Hey,
    Im having the same exact problem.
    Toast even says it has a medium error with this drive.
    I cant burn with toast and it wont play other DVD-R movies
    that I have burnt on other systems.
    What is the fix?

  • Disk Utility Showing "No Slices" on Hard drive test ?

    What does Disk Utility mean when it states "No Slices" available when verifying or repairing a HDD ?
    There appears to be zero information about this, including on Google.
    Does it signify that the HDD is dead or beyond recovery ?
    Does anyone know about this vague statement that Disk Utility throws up ?

    Apologies for not getting back sooner (health issues). I ended up using the original internal drive as an external drive via a usb connection and drive box. Thank you for response. I am still having issues with Toshiba drive and will pose another question.

Maybe you are looking for