jbuszkie

Members
 View Profile  See their activity

  • Posts

    693

  • Joined

  • Last visited

 Content Type 

Posts posted by jbuszkie

    ICY DOCK MB455SPF-B 5 in 3 $102 AR (thru 8/31) FS - Is this a good deal??

    in Good Deals!

    Posted

    No.

     

    It's a massive piece of crap.

     

    (Ok I'm exaggerating...)

     

    But seriously - I wish I went for the supermicro first.  I now have both, and the supermicro (while only populated with one drive so far), is SOOOOO much better to me.  (Specifically the horrible arrangement of the Icy Dock power connectors...)

     

     

    But is it a good price for that massive piece of crap? :D

     

    I've glanced through the thread above..  I'm not decided on that vs supermicro.. or just the norco case.. but that's another thread

     

     

    Norco 4020 (or 4220 or 4224) Vs. standard case w/ 5in3 cages...

    in Hardware

    Posted

    10-12 in the next year or two...  In the past I've been upgrading my server by replacing smaller drives with bigger ones.  But now my smallest drive is 1TB.  the rest are 1.5T and 2T's.  so I don't think I'll be upsizing the 1.5's and 2's anytime soon.  The 1T I'll probably replace as I believe that's my last non green drive. So..  I'll probably have to add disks in lieu of upsizing.  I imagine I'll upgrade the parity to a 3TB when I replace the 1TB.

     

    Jim

    Norco 4020 (or 4220 or 4224) Vs. standard case w/ 5in3 cages...

    in Hardware

    Posted

    I'm running out of room in my server and I need to think about upgrading my case.

    I currently have 8 drives in my antec sonata with 4 of them in a 4 in 3 coolmaster cage.

    I want/need to add more drives!

     

    I'm toying with the idea of getting a Norco 20 or 24 drive box.  I'm also

    looking into getting a regular tower with several 5 in 3 cages.

     

    It almost seems like the Norco could be cheaper after I calculate the cost

    of the 5 in 3 cages which seem to be about $100+ each!

     

    Why wouldn't I just get the Norco?

     

    Norco:

     

    Pros:

      Cost

     

    Cons:

      Size?

      Noise?

    Tower:

     

    Pros:

      Quieter

      Incrementally up-gradable?

      Smaller

     

     

    Cons:

      Cost.

     

    Right now the server sits in the basement.  I do watch TV in the basement occasionally.  Some day it will have it's own tiny closet

    I can't see myself needing 20 or 24 drives in the near future! 10-12 seems more likely..

     

    ???

     

    Thanks for your opinions...

     

    Jim

     

    Re: preclear_disk.sh - a new utility to burn-in and pre-clear disks for quick add

    in User Customizations

    Posted

    Were you running it using the "screen" program?  If yes..  The just reconnect to it..  But it sounds like you were jsut telneted into it... in which

    case...  you have to start over...

     

    Screen will run in the background and you can connect to the session or disconnect as many times as you want and the session is

    still there...

     

    I have had this happen before so I always run using screen!

     

    Jim

    Preclear.sh results - Questions about your results? Post them here.

    in User Customizations

    Posted

    Joe,

     

    I'm trying to preclear 4 2T samsung drives.

    3 are chugging along but one failed right after zeroing.

     

    I grabbed the first smart report as the drive, now, is un responsive.

     

    There are some errors reported.

     

     

     

    I'll try power cycling once the other drives finish (about 2 hours or so) and see if the drive comes back.. and grab another SMART report... but my guess is this drive might be a dud!

    Do you concur?

    I'm guessing it could just as easily be a loose/bad cable to the drive.  But do not touch them now...  Only do that after stopping the array cleanly and then powering down.  (It could be either the power or data cable, or, if in a drive tray, it might not be seated well in the connectors.)

     

    Joe L.

     

    Crud!  The last drive, after power cycling, passed the preclear test..  but there are some more errors.  My guess is I should RMA this drive.

    There are 28 ATA Errors.  There were 15 before the 2nd preclear attempt.  Here is an excerpt.  Full smart report attached.

    SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   051    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0026   252   252   000    Old_age   Always       -       0
  3 Spin_Up_Time            0x0023   067   066   025    Pre-fail  Always       -       10113
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       4
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   252   252   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       4
181 Unknown_Attribute       0x0022   252   252   000    Old_age   Always       -       0
191 G-Sense_Error_Rate      0x0022   252   252   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   252   252   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   100   100   000    Old_age   Always       -       31
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       0
223 Load_Retry_Count        0x0032   252   252   000    Old_age   Always       -       0
225 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       4

SMART Error Log Version: 1
ATA Error Count: 28 (device log contains only the most recent five errors) <--------------------------------------
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 28 occurred at disk power-on lifetime: 50 hours (2 days + 2 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 00 00 4f c2 00  Error: ABRT

     

    ???

    What do you think?  I moved the drive to a different cable and power cord for the 2nd pre-clear try.. So it's not a cabling issue..

     

    Thanks,

     

    Jim

    smart_start3805.txt

    smart_start3805.txt

    Preclear.sh results - Questions about your results? Post them here.

    in User Customizations

    Posted

    Ok.. I'll try the reseat and switch the cables around...  The drives are being cleared in a separate machine.  so it's not my main UnRaid

    machine.

     

    Interestingly..  Even on this separate machine I'm seeing much slower reads on the post read.  I still am baffled by this.

    I'm getting about 40MB/s calculated while the test says 84MB/s

    Post Read in progress on /dev/sda: 75% complete.
(  1,501,936,128,000  of  2,000,398,934,016  bytes read )at 84.3 MB/s
Disk Temperature: 35C,
Using Block size of  8,225,280  Bytes
Next report at 100%
Calculated Read Speed: 40 MB/s
Elapsed Time of current cycle: 10:15:27
Total Elapsed time: 22:31:51

    All three remaining drives exhibit this...  The pre-read and the zeroing all were fast... 

    Pre Read finished on /dev/sdc
(  2,000,388,096,000  of  2,000,398,934,016  bytes read)
Pre Read Elapsed Time: 6:15:27
Total Elapsed Time: 6:15:32
Disk Temperature: -->41<--C,
Using Block size of  8,225,280  Bytes
Calculated Read Speed - 88 MB/s


    Zeroing Disk /dev/sdc Done.
Zeroing Elapsed Time: 5:55:17
Total Elapsed Time: 12:10:52
Disk Temperature: -->42<--C,
Calculated Write Speed: 93 MB/s

     

     

     

    Preclear.sh results - Questions about your results? Post them here.

    in User Customizations

    Posted

    Joe,

     

    I'm trying to preclear 4 2T samsung drives.

    3 are chugging along but one failed right after zeroing.

     

    I grabbed the first smart report as the drive, now, is un responsive.

     

    There are some errors reported.

     

    SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   051    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0026   252   252   000    Old_age   Always       -       0
  3 Spin_Up_Time            0x0023   066   066   025    Pre-fail  Always       -       10438
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       2
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       4
10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   252   252   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       2
181 Unknown_Attribute       0x0022   252   252   000    Old_age   Always       -       0
191 G-Sense_Error_Rate      0x0022   252   252   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   252   252   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   100   100   000    Old_age   Always       -       7
200 Multi_Zone_Error_Rate   0x002a   252   252   000    Old_age   Always       -       0
223 Load_Retry_Count        0x0032   252   252   000    Old_age   Always       -       0
225 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       2

SMART Error Log Version: 1
ATA Error Count: 7 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 7 occurred at disk power-on lifetime: 3 hours (0 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 00 00 4f c2 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d0 01 00 4f c2 00 08      00:00:13.498  SMART READ DATA
  b0 d0 01 00 4f c2 00 08      00:00:13.498  SMART READ DATA
  b0 da 00 00 4f c2 00 08      00:00:13.498  SMART RETURN STATUS
  b0 da 00 00 4f c2 00 08      00:00:13.497  SMART RETURN STATUS
  ec 00 00 00 00 00 00 08      00:00:13.497  IDENTIFY DEVICE

Error 6 occurred at disk power-on lifetime: 3 hours (0 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 00 00 4f c2 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d1 01 01 4f c2 00 08      00:00:10.913  SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
  b0 d0 01 00 4f c2 00 08      00:00:10.913  SMART READ DATA
  b0 da 00 00 4f c2 00 08      00:00:10.912  SMART RETURN STATUS
  b0 da 00 00 4f c2 00 08      00:00:10.912  SMART RETURN STATUS
  ec 00 00 00 00 00 00 08      00:00:10.912  IDENTIFY DEVICE

Error 5 occurred at disk power-on lifetime: 2 hours (0 days + 2 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 00 00 4f c2 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d0 01 00 4f c2 00 08      00:00:08.413  SMART READ DATA
  b0 d0 01 00 4f c2 00 08      00:00:08.413  SMART READ DATA
  b0 da 00 00 4f c2 00 08      00:00:08.413  SMART RETURN STATUS
  b0 da 00 00 4f c2 00 08      00:00:08.412  SMART RETURN STATUS
  ec 00 00 00 00 00 00 08      00:00:08.412  IDENTIFY DEVICE

Error 4 occurred at disk power-on lifetime: 1 hours (0 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 00 00 00 00 00

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 00 08      00:00:07.044  IDENTIFY DEVICE
  60 d1 00 18 ea e6 40 08      00:00:07.044  READ FPDMA QUEUED
  60 d1 00 18 e9 e6 40 08      00:00:07.044  READ FPDMA QUEUED
  60 d1 00 18 e8 e6 40 08      00:00:07.044  READ FPDMA QUEUED
  60 d1 00 18 e7 e6 40 08      00:00:07.044  READ FPDMA QUEUED

Error 3 occurred at disk power-on lifetime: 1 hours (0 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 00 00 4f c2 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d1 01 01 4f c2 00 08      00:00:06.651  SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
  b0 d0 01 00 4f c2 00 08      00:00:06.650  SMART READ DATA
  b0 da 00 00 4f c2 00 08      00:00:06.650  SMART RETURN STATUS
  b0 da 00 00 4f c2 00 08      00:00:06.649  SMART RETURN STATUS
  ec 00 00 00 00 00 00 08      00:00:06.649  IDENTIFY DEVICE

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective Self-Test Log Data Structure Revision Number (0) should be 1
SMART Selective self-test log data structure revision number 0
Warning: ATA Specification requires selective self-test log data structure revision number = 1
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Completed [00% left] (0-65535)
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

     

    I'll try power cycling once the other drives finish (about 2 hours or so) and see if the drive comes back.. and grab another SMART report... but my guess is this drive might be a dud!

    Do you concur?

    Remove Drive Without Losing Parity question...

    in unRAID Server 4.4 [No new topics]

    Posted

    I was following this thread

     

    http://lime-technology.com/forum/index.php?topic=2591.msg20919#msg20919

     

    To remove the old drive from the system.

     

    However.. I go to the point where I was about to hit the restore button...  But there is no restore button anymore.

    It's only giving me the option to start

    Start will disable the missing disk and then bring the array on-line. The disk's data will be available, but the array will be unprotected; install a new disk as soon as possible.

     

    What do I do?