Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: 3TB Hard drive (wd red) healthy or dead?

  1. #1
    Join Date
    Jul 2011
    Beans
    70

    3TB Hard drive (wd red) healthy or dead?

    I have a hard drive that reports 'SMART capable status BAD' at boot. But if I plug in the drive and run an extended smart test, it passed without errors see here

    I am unable to see the volumes in Gparted (after plugging them in after OS loaded) but can see them in disk utility. I have been unable to run secure-erase or any formatting operations on them. Is there a clue in that output above? These drives are brand new and were in a software raid array, so whatever happened to the first obviously broke the second (exact same problem)

    Stu
    Last edited by sdpagent; January 27th, 2013 at 08:18 PM.

  2. #2
    Join Date
    Mar 2010
    Location
    Metro-ATL; PM free zone.
    Beans
    Hidden!
    Distro
    Lubuntu 14.04 Trusty Tahr

    Re: 3TB Hard drive (wd red) healthy or dead?

    I would run Boot-Info to gather data about the drive: https://help.ubuntu.com/community/Boot-Info

    That should help diagnose the root cause.

    Always use parted or gparted with 12.04 or later releases for these large HDDs.

  3. #3
    Join Date
    Jul 2011
    Beans
    70

    Re: 3TB Hard drive (wd red) healthy or dead?

    I am running ubuntu 12.04.
    The devices are not picked up by gparted.
    These drives are just holding data. There is no boot data on them. I boot from a separate drive.

    Stu
    Last edited by sdpagent; January 27th, 2013 at 09:22 PM.

  4. #4
    Join Date
    Mar 2010
    Location
    Metro-ATL; PM free zone.
    Beans
    Hidden!
    Distro
    Lubuntu 14.04 Trusty Tahr

    Re: 3TB Hard drive (wd red) healthy or dead?

    Quote Originally Posted by sdpagent View Post
    I am running ubuntu 12.04.
    The devices are not picked up by gparted.
    These drives are just holding data. There is no boot data on them. I boot from a separate drive.
    Understood, but boot-info will dump information about the disk layout and flags too. I thought it would be helpful.

  5. #5
    Join Date
    Feb 2007
    Location
    West Hills CA
    Beans
    9,373
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: 3TB Hard drive (wd red) healthy or dead?

    Time to start looking at cables, power connections, etc. It could be the drives just need breaking in.

    If the drives are enumerated with

    Code:
    sudo fdisk -l
    Then run badblocks on each drive. Capture the output, cut and paste into a notepad.

    Code:
    sudo badblocks /dev/sde1
    If you get a lot of badblocks, then run again can mark them as bad in the filesystem:

    Code:
    sudo fsck -cc /dev/sde1
    If your drive can't run badblocks, then you really do have a bad drive. Since these drives are new, I would return them. If they are out-of-specification, they will bite you in the future.

    Do a search on your particular model number and see if others are having similar problems. Sometimes drive manufactures try to cut costs and use cheaper parts and catfood in their drives.
    -------------------------------------
    Oooh Shiny: PopularPages

    Unumquodque potest reparantur. Patientia sit virtus.

  6. #6
    Join Date
    Jun 2009
    Location
    Chicago Suburbs
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: 3TB Hard drive (wd red) healthy or dead?

    I do not know RAID, but you cannot see RAID drives in gparted as it does not handle RAID.

    Do not use gparted on RAID.
    http://www.howtoforge.com/how-to-res...-software-raid
    Don't bother with RAID 0 unless you have a specific need for speed without data redundancy, since if one drive goes out, you lose the whole array.
    http://en.wikipedia.org/wiki/RAID
    parted (3.0) completely removes filesystem creation and modification support, except for filesystem probing to determine what's in a partition.
    For info on UEFI boot install & repair - Updated Mar 2015:
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to close thread when/if answered completely.







  7. #7
    Join Date
    Jul 2011
    Beans
    70

    Re: 3TB Hard drive (wd red) healthy or dead?

    To answer a few questions
    - the drives were (as in no longer) in a sofware raid array, but mdadm does not pick them up anymore (no superblock found) and the conf file looks like its new for some reason. Very strange.

    - fdisk does not pick up the drives

    - i tried the drives in another machine (but running off of the same power (had the towers next to each other and just plugged in different sata cables into the other motherboard. I couldnt boot with the drives in that one either. (could this really be power related? I can hear the drives spin up when i plug in. They dont make a tick sound but a nice/clean sound (hard to explain). I guess I shouldn't hear them spin up at all though?

    The drives were working until I plugged in another drive a 2tb black and rebooted.

  8. #8
    Join Date
    Mar 2010
    Location
    Metro-ATL; PM free zone.
    Beans
    Hidden!
    Distro
    Lubuntu 14.04 Trusty Tahr

    Re: 3TB Hard drive (wd red) healthy or dead?

    Quote Originally Posted by sdpagent View Post
    - fdisk does not pick up the drives
    fdisk is not safe to use on drives over 2TB in size or with GPT partitioning. This applies to fdisk-based tools like cfdisk and sfdisk as well.

    Use parted or gparted going forward.

    There is something about using a HDD in RAID that changes it - at least if the HDD wasn't partitioned. That is the flag that you need to get reset. I'd use parted and write a new GPT partition to it. It isn't like you have anything to loose. Don't use MBR partitions - it doesn't support drives a little over 2TB either.

    Then I'd run spinrite (commercial software) on the HDDs to find any parts that cannot be read and give the HDD a chance to relocate any bad sectors. You can probably do this using something like ddrescue too.

    If the HDDs do not show up in the device table at all, then I'd verify that your BIOS sees them and look for MB and chipset driver updates.

    Sorry, I didn't go back and re-read prior messages to see exactly what you can and cannot see.

  9. #9
    Join Date
    Jun 2009
    Location
    Chicago Suburbs
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: 3TB Hard drive (wd red) healthy or dead?

    Hard drives retain RAID meta-data, you have to remove that for gparted to then see drive.

    Presence1960 on remove old raid setting from HD
    http://ubuntuforums.org/showthread.php?t=1325650
    sudo dmraid -E -r /dev/sda
    sudo dmraid -E -r /dev/sdb
    Also check BIOS for raid settings
    More discusion:
    http://wwww.ubuntuforums.org/showthr...38#post9274738
    For info on UEFI boot install & repair - Updated Mar 2015:
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to close thread when/if answered completely.







  10. #10
    Join Date
    Jul 2011
    Beans
    70

    Re: 3TB Hard drive (wd red) healthy or dead?

    Quote Originally Posted by TheFu View Post
    fdisk is not safe to use on drives over 2TB in size or with GPT partitioning. This applies to fdisk-based tools like cfdisk and sfdisk as well.

    Use parted or gparted going forward.

    There is something about using a HDD in RAID that changes it - at least if the HDD wasn't partitioned. That is the flag that you need to get reset. I'd use parted and write a new GPT partition to it. It isn't like you have anything to loose. Don't use MBR partitions - it doesn't support drives a little over 2TB either.

    Then I'd run spinrite (commercial software) on the HDDs to find any parts that cannot be read and give the HDD a chance to relocate any bad sectors. You can probably do this using something like ddrescue too.

    If the HDDs do not show up in the device table at all, then I'd verify that your BIOS sees them and look for MB and chipset driver updates.

    Sorry, I didn't go back and re-read prior messages to see exactly what you can and cannot see.
    I dont know if this is useful but
    - the drives were originally fine with being detected by the motherboard, so I know its not a motherboard driver issue.
    - I cant get into the bios when the drives are connected at time of boot
    - getting into the bios and then plugging in the drives, the motherboard does allow the drives to be seen, I dont know if the bios should update the list of drives when AHCI is on?

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •