Tag Info

Hot answers tagged

8

Yes, it definitely looks like a hardware fault. I have had multiple Barracuda ES / ES.2 drives go..including 12 out of 16 across two servers. I don't think the smartmontools is sufficient for warranty replacement. Go to Seagate's website and download their SeaTools bootable CD. When/if it determines the drive has a fault, it will give you a warranty code. ...


5

The output of: diff -u <(lynx -dump http://www.seagate.com/www/en-au/products/external/expansion/expansion_portable/) <(lynx -dump http://www.seagate.com/www/en-au/products/external/external-hard-drive/portable-hard-drive/) tells it all: -Seagate® Expansion™ Portable Drives +FreeAgent® GoFlex™ Ultra–portable Drive -A basic drive that goes wherever ...


4

No. You're buggered. Either: Get a disk of the same model as the one you have, formatted the same (sometimes OEM disks can have a slightly different format to ones with generic firmware) Get a 146GB disk and be prepared to waste half of the capacity. Get a disk with the array manufacturer's firmware, which will be set up so it can act as a drop in ...


3

This won't help you now, but in the past I've taken to leaving around 500~700Mb leeway at the end RAID sets, where we haven't been able to procure enough spares of the same model and the HBA won't accept drives of a larger size. It's less of an issue nowadays - we only tend to run into it when using the max configurations in blades.


3

From the Toms Hardware article: Part numbers for the affected models of Barracuda drives and their respective firmware revisions are as follows: “Affected part number: 9JU138-300, 336 with firmware revisions SD15, SD17, or SD18.” It also mentions there's a firmware fix available to treat the problem if you run into it


3

Much like on Linux this data may be in your dmesg output (depending on your disk controller: a hardware RAID controller may not pass the firmware data through for an array). If it's not you can install dmidecode from ports (sysutils/dmidecode) - that should get you what you need. ipmitool is also an option, but probably less likely to get you the data ...


3

According to the data sheets the sustained data rate for the Cheetah is 73-125 MB/s and for the Savvio 151 to 202. So while data rates of 640 MB/s for four Savvio disks seem to be reasonably within the specs, 1,3 GB/s for 4 Cheetahs obviously are not. You are likely facing a situation where caching effects (probably controller-side) are contorting the ...


3

I've had this a few times recently with a similar Seagate ST3000DM001-1CH166 firmware CC24. You don't need Seatools, just run a long smart test: smartctl -t long /dev/sdc Then if smarctl shows no error you're OK for now: SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) ...


2

Your drive overheated at some point in the past. 190 Airflow_Temperature_Cel 0x0022 061 038 045 Old_age Always In_the_past 39 (0 4 43 37 0) Unfortunately it's not possible to be 100% sure of the exact temperature that it reached, only that it was quite a bit beyond the vendor's defined threshold. Though it's most likely that the normalized ...


2

Every Seagate drive I've ever seen reports bizarre raw values for those two fields. One thing you can do is the same thing the utility (and drive) does internally: check the normalized value against the threshold value. When the value drops to the threshold, the attribute will report as failing (or failed). Another thing you can do is never buy another ...


2

HP buy their disks from the usual suspects (seagate, WD, Hitachi etc.) but in almost every case they put their own firmware on them. Physically they'll fit if you have the mount for the drive - that's the tricky bit as they don't sell 'blanks'. After that it's down to whether or not the actual code on your disk controllers is happy to work with non-HP disks ...


2

The Seagate 1.5 TB have a long, sordid history of drive corruption and hardware defects. Seagate 1.5TB Drives Randomly Freezing http://www.tomshardware.com/news/seagate-barracuda-1.5TB-freezing,6558.html Updated: Seagate 1TB Drives Biting The Dust http://www.tomshardware.com/news/seagate-7200.11-failing,6844.html Seagate customers swamped by ...


1

i'm using 4 drives from problematic series, i just did update of firmware from seagate and so far have no problems. at least according to vendor problem can be fixed by that.


1

The SAS and SATA backplanes are a universal standard (if either HP or Seagate decided to change it, nothing would ever work in their devices), so there's no doubt about whether or not it will physically fit. It will fit. Unfortunately I can only give a fuzzy answer on the 2nd point - it should accept it, but I can't guarantee it.


1

You really can't do anything. Even if you could claim unused sectors to do this, it would be a very bad idea. Unused sectors are used to replace failed sectors so using them right away would strongly increase the risk of data loss and decrease the life of your hard drive.


1

The others are correct, nothing you can do (except rebuild or get larger disks)


1

We went with bitlocker for our laptops because we couldn't get a good answer to this very question from Wave, and we thought the same scenarios was likely to be non-vendor specific.


1

For your first question, yes, drives that you get back from such a "repair" both are not the exact drive you sent in, but also are not brand new. They are almost always "remanufactured" or "recertified". I once (years ago) called in on a drive I had just bought, and the vendor I purchased it from refused to do a replacement. So I called the manufacturer, ...


1

what I do is check the read hwecc and seek error rates. I also check to make sure relocated or pending sectors arent present. after I get the # of the first 3 I do a bunch of copying to and from the drive then check the # again. if they have not greatly gone up I keep an eye on the drive. If they shoot up I call the vender and see what has to be done to ...


1

The manual for ST32000641AS (alternative link) says that the drive has 3,907,029,168 guaranteed sectors, while the specifications for WD2003FYYS (alternative link) say it has 3,907,029,168 sectors. Therefore the drives have the same capacity.


1

Sounds alot like the dns for the iscsi device is now expired. That explains the ip only access. Try putting the names in the c:\windows\system32\drivers\etc\hosts file. Format is: name ip, like: theiscsidevice 1.2.3.4 Try to ping by name, it should then start working


1

Updating the firmware from 1.46 to 1.49 resolved this issue.


1

You can start a patrol read on all drives and when it finishes check the controller eventlog for events 0x005d (patrol read corrected medium error - type is warning), 0x005f (patrol read uncorrectable error - type is fatal) and 0x0061 (patrol read puncturing bad block - type is fatal). Create a virtual disk using all disks, which raidlevel you choose ...


1

Current Pending Sector is just that, the number of locations the disk knows about that needs to be reallocated but haven't reallocated yet since the disk has no source for the data to be reallocated. Once you write into that location the disk will automatically reallocate the area to another place and write the new data in the new place and the current ...


1

The disks will be backwards compatible with earlier generation SAS. So the speed would just downshift to 3Gbps. However, since your server and PERC controller are old, it may make sense to find some period-correct SAS disks. Either way, the 2TB disk capacity is also supported. That is the maximum for the controller.


1

The 30 TB is the gross disk space, six 5 TB disks. In addition to the JBOD and common RAID levels, SimplyRAID sounds like a software solution that allows you to make maximum use of different sized disks while still maintaining a certain amount of redundancy, allowing you to lose 1 or 2 disks without losing your data. SimplyRAID single security with ...


1

The DELL PERC H730 is based on the LSI 3108 Chipset, and since this chipset supports disks larger than 2TB and SAS3 communications I can't see reasons for this controller won't work with those Seagate NL-SAS 4TB discs. What you should consider is the cabling used on this card, since SAS3 cards uses the new SFF8643 connector.



Only top voted, non community-wiki answers of a minimum length are eligible