CaptainSpalding Posted March 11, 2010 Share Posted March 11, 2010 I bought a brand new Samsung Ecogreen F2 1.5Tb drive yesterday and installed it to my unraid server. I thought I would run the preclear overnight. When I updated the progress from the webgui, the drive always made a clicking noise when it updated. I went to be and woke up, thought it would be done already, but I could not connect through webgui, so I hardbooted and my Fasttrak sata controller informed that "There is something wrong with your hardware!". I was about to RMA it, but if the disc isn't (for some reason) faulty, I would have to pay for the disc-check. What could have happened? I have the HDD at work at the moment and if you guys think the HDD is a goner, I would return it on my way home and hopefully get a new one for the weekend. Thanks in advance! Link to comment
queeg Posted March 11, 2010 Share Posted March 11, 2010 Have you tried more than one sata cable? Is it getting enough power/voltage from psu? Trying it in a different machine is one way to check that out. Link to comment
CaptainSpalding Posted March 11, 2010 Author Share Posted March 11, 2010 So my other comp with Win XP could also mount the disc even that it has been formatted to reiserfs? Link to comment
Joe L. Posted March 11, 2010 Share Posted March 11, 2010 So my other comp with Win XP could also mount the disc even that it has been formatted to reiserfs? No, not without loading a reiserfs driver. But it should be able to see the disk if it is working. Link to comment
CaptainSpalding Posted March 11, 2010 Author Share Posted March 11, 2010 So my other comp with Win XP could also mount the disc even that it has been formatted to reiserfs? No, not without loading a reiserfs driver. But it should be able to see the disk if it is working. In the bios you mean? Thank you both for your answers! Link to comment
Joe L. Posted March 11, 2010 Share Posted March 11, 2010 Yes. In the BIOS, and on the disk-management function in the control panel. Don't forget, one of the major benefits of the pre-clearing process is the burn-in and ability to detect those disks prone to an early failure. It is a LOT easier to return the drive now, before it is part of your array, than after you have added it to the array. Link to comment
CaptainSpalding Posted March 11, 2010 Author Share Posted March 11, 2010 It is a LOT easier to return the drive now, before it is part of your array, than after you have added it to the array. That was my first thought too. A very good feature, just hoping it's only the hdd. Just on my way home to test if the server boots up without the new hdd. Link to comment
CaptainSpalding Posted March 11, 2010 Author Share Posted March 11, 2010 Okey, so the server boots ok, but I cannot get to it through the web-interface. It only goes to "Wait..." And the HDD seemed fine on my other comp. Link to comment
Joe L. Posted March 11, 2010 Share Posted March 11, 2010 Okey, so the server boots ok, but I cannot get to it through the web-interface. It only goes to "Wait..." And the HDD seemed fine on my other comp. If it goes to "wait" you might be able to get a syslog so we can see what is actually happening. It might just be replaying the journal contents of the drives that were taken off-line abruptly when you forced a power-off and rebooted. Just wait a few minutes and press refresh on the browser. Joe L. Link to comment
CaptainSpalding Posted March 11, 2010 Author Share Posted March 11, 2010 Now it just tries to connect, but then in a few minutes redirects to www.tower.com (lime-technology should make some deal with them ). How can I get the syslog? EDIT: Now I got a connection to unraid, when I removed the new drive and booted. But it seems one of my Seagates has failed? Link to comment
Joe L. Posted March 11, 2010 Share Posted March 11, 2010 How can I get the syslog? Instructions to capture the syslog are in the wiki under troubleshooting Link to comment
CaptainSpalding Posted March 11, 2010 Author Share Posted March 11, 2010 Now I got the new HDD to show on the array, but that Seagate from the previous screenshot is still red. Should I replace it with this new one or can you see from syslog if that really is a goner? Link to comment
CaptainSpalding Posted March 11, 2010 Author Share Posted March 11, 2010 Syslog and Thanks Joe!! syslog-2008-04-10.txt Link to comment
CaptainSpalding Posted March 12, 2010 Author Share Posted March 12, 2010 Sorry to bump. Is there any way to test if the Seagate HDD is really failed? With out taking the drive out of the server. Link to comment
purko Posted March 12, 2010 Share Posted March 12, 2010 Sorry to bump. Is there any way to test if the Seagate HDD is really failed? With out taking the drive out of the server. Yes, try run the preclear sctipt on it. If that can't pass, then the disk is of no use to you. Link to comment
CaptainSpalding Posted March 12, 2010 Author Share Posted March 12, 2010 Yes, try run the preclear sctipt on it. If that can't pass, then the disk is of no use to you. And that clears the data on the disc also? Link to comment
purko Posted March 12, 2010 Share Posted March 12, 2010 Yes, try run the preclear sctipt on it. If that can't pass, then the disk is of no use to you. And that clears the data on the disc also? Well, yeah. I thought you recovered all that data from it, and considered it a goner. Thought you asked this question out of denial, unwilling to let it go. Link to comment
Joe L. Posted March 12, 2010 Share Posted March 12, 2010 Run hdparm -tT /dev/sdX on it. If it can do basic timing, it should not be a total fail. Link to comment
CaptainSpalding Posted March 12, 2010 Author Share Posted March 12, 2010 Run hdparm -tT /dev/sdX on it. If it can do basic timing, it should not be a total fail. I ran that same script with two other drives and comparing to those this seems fine. But should I get a replacement or is this SG still "not bad enough for RMA"? I have very good quality SATA cables that I bought a couple of weeks ago, so I don't think they are the problem. Now that the server has been running a while, I have noticed that while the other HDD's have about 250 reads the parity and the "red ball" SG have about 2500-3000 reads.... I parity drive trying to recover something or is it just the hdparm? Link to comment
Joe L. Posted March 12, 2010 Share Posted March 12, 2010 Run hdparm -tT /dev/sdX on it. If it can do basic timing, it should not be a total fail. I ran that same script with two other drives and comparing to those this seems fine. But should I get a replacement or is this SG still "not bad enough for RMA"? I have very good quality SATA cables that I bought a couple of weeks ago, so I don't think they are the problem. Now that the server has been running a while, I have noticed that while the other HDD's have about 250 reads the parity and the "red ball" SG have about 2500-3000 reads.... I parity drive trying to recover something or is it just the hdparm? It probably keeps re-trying to read. Link to comment
CaptainSpalding Posted March 15, 2010 Author Share Posted March 15, 2010 Ok. Now that I have all other drives (including parity and the newly installed HDD) with green dots, except the SG in blue, do I first make a parity check and then preclear/format the SG HDD or do I first preclear and then run parity? Thank you for your time! Link to comment
CaptainSpalding Posted March 18, 2010 Author Share Posted March 18, 2010 I bought and hooked up a new hdd (WD 1.5Tb), now when I try to boot my Fasttrak sata controller says "There's something wrong with your hardware!"... I'm thinking could it be the power? I have a 630W Nexus with 1.5Tb 12 HDD's. Link to comment
Joe L. Posted March 18, 2010 Share Posted March 18, 2010 I bought and hooked up a new hdd (WD 1.5Tb), now when I try to boot my Fasttrak sata controller says "There's something wrong with your hardware!"... I'm thinking could it be the power? I have a 630W Nexus with 1.5Tb 12 HDD's. If it is a single rail power supply it should be fine... You might try using a different connector to power the disk. (or a different SATA cable) Link to comment
CaptainSpalding Posted March 18, 2010 Author Share Posted March 18, 2010 I now got it to boot to some point, but I get the message as in attached picture. Before that I got a bunch of those errno=-16 messages for ata10. Link to comment
purko Posted March 18, 2010 Share Posted March 18, 2010 Now THAT points to bad memory! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.