barbapapa

Members
  • Posts

    20
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

barbapapa's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Great deal! I got one of these a few weeks ago at Staples for $120 and it had a ST3000DM001 inside it. Plus a handy bonus 3TB removable USB 3 dock http://ncix.com/products/?sku=76516&vpn=STCA3000101&manufacture=Seagate%20Retail&promoid=1382
  2. Thanks for this, Harpz and Joe. I too had smartctl 5.38, and upgraded to 5.40. Didn't help with my issue, but it's nice having more information about my drives.
  3. How can I get "model/serial" to show up for my USB devices on the main page? Today I finally upgraded from v4.5.6 > v4.7 > v5.0-rc5 of unRAID, so I could add a couple of 3TB drives to my array. I also updated unMenu from 1.2 (old, I know!) to 1.5. Everything seemed to go pretty smoothly, but for some reason I lost the "model/serial" information from my USB devices (under UNRAID drive and Drive Partitions - not in protected array) on my home page. Here's how it looked under 4.5.6 with unmenu 1.2 Here's how it looks under 4.7 with unmenu 1.5 When I use the command "ls -l /dev/disk/by-id", they do show up: lrwxrwxrwx 1 root root 9 2012-09-03 13:08 usb-Seagate_GoFlex_Desk_NA0ML92W-0:0 -> ../../sdc lrwxrwxrwx 1 root root 10 2012-09-03 13:08 usb-Seagate_GoFlex_Desk_NA0ML92W-0:0-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2012-09-03 13:08 usb-_Patriot_Memory_078C0DB80B0A-0:0 -> ../../sdd lrwxrwxrwx 1 root root 10 2012-09-03 13:08 usb-_Patriot_Memory_078C0DB80B0A-0:0-part1 -> ../../sdd1 so I'm not sure why the model/serial (and file system etc) is not showing up on the main page. By the way, I shouldn't be worried that the drive assignments changed, should I? Before I upgraded to 5.0-rc5, sdc was my parity drive, now it's the Seagate external drive I hooked up to USB.
  4. Thanks guys. I really really thought I had already precleared that drive. I guess I should have made sure and did "another" preclear to be sure, especially since I didn't actually need it yet. That'll learn me. Now I love that preclear script even more, now that I have experienced firsthand what happens without it!
  5. I just fouled up and added a drive that was in my machine for awhile but not in my array. I was SURE I had already precleared the drive... but apparently I hadn't; when I added the drive, Unraid showed "Clearing" next to the new disk, and now my array is offline, unraid shows "Starting, clear 2% complete...". I see no "stop", "cancel" or anything like that so I'm looking at a lot of offline time. Argh. Annoying thing is, I didn't even need this drive added yet... but I did need my array. Is there any way to cancel via the command line or something? Every other drive I've ever added to my array was precleared, so I've never seen this before and have no idea how to stop it.
  6. OK I pre-cleared this drive for 3 more cycles, here are the results: Sep 18 19:08:45 Tower preclear_disk-finish[937]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Sep 18 19:08:45 Tower preclear_disk-finish[937]: 1 Raw_Read_Error_Rate 0x002f 197 195 051 Pre-fail Always - 1536 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 4 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 180 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 3 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 2 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 111 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 10 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 21 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 49 What happened to the 17 Current Pending Sectors from my first pre-clear? I was expecting to see them under Reallocated Event Count this time around. What's the verdict, is this drive too flakey to go into the array?
  7. Still in the 2nd of 3 more cycles of pre-clear, but I'm seeing one heck of a lot of errors in my syslog now, here's a sample: Sep 17 04:57:23 Tower kernel: ata4.00: failed command: READ DMA EXT Sep 17 04:57:23 Tower kernel: ata4.00: cmd 25/00:08:c0:cf:14/00:00:94:00:00/e0 tag 0 dma 4096 in Sep 17 04:57:23 Tower kernel: res 51/40:00:c7:cf:14/40:00:94:00:00/e0 Emask 0x9 (media error) Sep 17 04:57:23 Tower kernel: ata4.00: status: { DRDY ERR } Sep 17 04:57:23 Tower kernel: ata4.00: error: { UNC } Sep 17 04:57:23 Tower kernel: ata4: hard resetting link Sep 17 04:57:24 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Sep 17 04:57:24 Tower kernel: ata4.00: configured for UDMA/133 Sep 17 04:57:24 Tower kernel: ata4: EH complete Sep 17 04:57:27 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Sep 17 04:57:27 Tower kernel: ata4.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable Sep 17 04:57:27 Tower kernel: ata4.00: failed command: READ DMA EXT Sep 17 04:57:27 Tower kernel: ata4.00: cmd 25/00:08:c0:cf:14/00:00:94:00:00/e0 tag 0 dma 4096 in Sep 17 04:57:27 Tower kernel: res 51/40:00:c7:cf:14/40:00:94:00:00/e0 Emask 0x9 (media error) Sep 17 04:57:27 Tower kernel: ata4.00: status: { DRDY ERR } Sep 17 04:57:27 Tower kernel: ata4.00: error: { UNC } Sep 17 04:57:27 Tower kernel: ata4: hard resetting link Sep 17 04:57:27 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Sep 17 04:57:27 Tower kernel: ata4.00: configured for UDMA/133 Sep 17 04:57:27 Tower kernel: ata4: EH complete Sep 17 04:57:30 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Sep 17 04:57:30 Tower kernel: ata4.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable Sep 17 04:57:30 Tower kernel: ata4.00: failed command: READ DMA EXT Sep 17 04:57:30 Tower kernel: ata4.00: cmd 25/00:08:c0:cf:14/00:00:94:00:00/e0 tag 0 dma 4096 in Sep 17 04:57:30 Tower kernel: res 51/40:00:c7:cf:14/40:00:94:00:00/e0 Emask 0x9 (media error) Sep 17 04:57:30 Tower kernel: ata4.00: status: { DRDY ERR } Sep 17 04:57:30 Tower kernel: ata4.00: error: { UNC } Sep 17 04:57:30 Tower kernel: ata4: hard resetting link Sep 17 04:57:30 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Sep 17 04:57:30 Tower kernel: ata4.00: configured for UDMA/133 Sep 17 04:57:30 Tower kernel: sd 4:0:0:0: [sdd] Unhandled sense code Sep 17 04:57:30 Tower kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x08 Sep 17 04:57:30 Tower kernel: sd 4:0:0:0: [sdd] Sense Key : 0x3 [current] [descriptor] Sep 17 04:57:30 Tower kernel: Descriptor sense data with sense descriptors (in hex): Sep 17 04:57:30 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Sep 17 04:57:30 Tower kernel: 94 14 cf c7 Sep 17 04:57:30 Tower kernel: sd 4:0:0:0: [sdd] ASC=0x11 ASCQ=0x4 Sep 17 04:57:30 Tower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 94 14 cf c0 00 00 08 00 Sep 17 04:57:30 Tower kernel: end_request: I/O error, dev sdd, sector 2484391879 Sep 17 04:57:30 Tower kernel: Buffer I/O error on device sdd, logical block 310548984 sdd is the disk I'm preclearing. I don't recall seeing all those errors during a preclear before. Bad sign?
  8. First off, thanks again to Joe for a great script! I just precleared 2 WD20EARS drives (with pins 7 and 8 jumpered). I precleared them simultaneously using separate screen sessions. They both successfully precleared, but gave me the "Offline data collection activity was suspended by an interrupting command from host" warning. I gather from reading posts in the forum about it, I shouldn't need to worry about this. I am a little worried about the Raw_Read_Error_Rate and Current_Pending_Sector values for one of the drives though: Sep 12 14:26:23 Tower preclear_disk-finish[30093]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 1 Raw_Read_Error_Rate 0x002f 197 195 051 Pre-fail Always - 291 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 4 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 32 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 3 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 2 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 19 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 17 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 Are my worries about this drive warranted?
  9. For me the reason was I'd recently wiped my system and installed Windows 7. So there are definitely reasons why even longtime unraid users might be using the forums while not being logged in. Anyways thanks for adding the note Joe, and for creating such a useful script!
  10. Hi, thanks for a great script, Joe! I used it when I was setting up my unRaid server in January. I'm adding some drives now so I thought I'd download the most recent version... and I couldn't find the download link. I felt like an idiot, I kept searching the post for the link and couldn't find it... until finally I tried logging in to the forum, and then the link appeared at the bottom of the post! It would be nice if the link showed up for guests, even if it just tells you you need to log in when you click on it, but as it is, there is no indication there is any link at all. Not your fault, obviously! Just a usability problem with the forum. Could you maybe make mention of this? Maybe at the top of the first post, say something like "Download link at the bottom of the post. Make sure you are logged in to see it" I'm sure most people here are logged in anyways, but for those who aren't, it could save a lot of time and frustration looking for the link.
  11. Those pins can be frustrating, for sure. I hated them at first but I've gotten to like them. I got a replacement heat sink because the stock one was just too loud for me. I popped off the heat sink, wiped the thermal compound off the CPU, and then plopped in the new heat sink. The new heat sink (Arctic Cooling Freezer Pro 7) went in first try, took me all of about 15-30 seconds to attach it solidly to the board, didn't have to remove the motherboard or anything, and didn't have to force any of the pins; they all clicked into place easily. Love the new heatsink. I can't even hear it, it's quieter than my case fans.
  12. Hi, thanks for a great script! I used it on a 1 TB WD10EADS yesterday and it seemed to get through it ok. It came up with one mildly worrisome error: UDMA_CRC_Error_Count : 1 Is that something worth worrying about? Jan 12 00:54:05 Tower preclear_disk-finish[1004]: SMART Attributes Data Structure revision number: 16 Jan 12 00:54:05 Tower preclear_disk-finish[1004]: Vendor Specific SMART Attributes with Thresholds: Jan 12 00:54:05 Tower preclear_disk-finish[1004]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Jan 12 00:54:05 Tower preclear_disk-finish[1004]: 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 Jan 12 00:54:05 Tower preclear_disk-finish[1004]: 3 Spin_Up_Time 0x0027 170 169 021 Pre-fail Always - 6483 Jan 12 00:54:05 Tower preclear_disk-finish[1004]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 25 Jan 12 00:54:05 Tower preclear_disk-finish[1004]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 Jan 12 00:54:05 Tower preclear_disk-finish[1004]: 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 Jan 12 00:54:05 Tower preclear_disk-finish[1004]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 12 Jan 12 00:54:05 Tower preclear_disk-finish[1004]: 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Jan 12 00:54:05 Tower preclear_disk-finish[1004]: 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Jan 12 00:54:05 Tower preclear_disk-finish[1004]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 23 Jan 12 00:54:05 Tower preclear_disk-finish[1004]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 20 Jan 12 00:54:05 Tower preclear_disk-finish[1004]: 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 25 Jan 12 00:54:05 Tower preclear_disk-finish[1004]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 Jan 12 00:54:05 Tower preclear_disk-finish[1004]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 Jan 12 00:54:05 Tower preclear_disk-finish[1004]: 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 Jan 12 00:54:05 Tower preclear_disk-finish[1004]: 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 1 Jan 12 00:54:05 Tower preclear_disk-finish[1004]: 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 Took about 11.5 hours to get through one cycle. I'm hoping the fact that it's just one UDMA CRC error that I should be OK. I'm going to do another WD10EADS shortly. Next question: I'd like to stress-test a drive that is already part of my array (2 data drives, no parity drive), but doesn't have any data on it yet. I thought about using the preclear utility on it, but if I remove it from the array, then I can't restart the array - I get the "Too many wrong/missing disks" error. Can I just use the restore function? Is there a better way to stress-test a drive that is already part of the array? Actually I wouldn't mind testing the drive that DOES have data on it as well.
  13. Have you built yours yet? If not I hope you have as much fun as I'm having so far!
  14. Thanks RobJ! This is my first build from scratch, but I have upgraded CPUs before so I knew I had to be careful there! I'll definitely be reading up on airflow and so on, especially from other users here with the same case. You're right, I did have fun, and I definitely won't hesitate to build the next one!