Jump to content

JackBauer

Members
 View Profile  See their activity

  • Posts

    294

  • Joined

  • Last visited

 Content Type 

Posts posted by JackBauer

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted · Edited by JackBauer

    Thank you - but Active Streams doesn't seem to pick up on shares that are outside the array?  I have a UD "share" that is actually an SMB share from another server.  Just wanting to monitor that "stream" if possible.

     

    Any ideas?  Not super-urgent...

     

    edit:  Never mind - I used a plugin to monitor my Ethernet traffic - and that's a proxy for what I wanted...

    Re: Format XFS on replacement drive / Convert from RFS to XFS (discussion only)

    in General Support

    Posted

    Ok I think this is really my last question :)

     

    I don't quite see (and can't easily find by searching due to massive amount of information on the broad subject)...  Exactly how to format the new 8TB (as XFS)...

     

    My parity is good now, new drive is not yet added.  Array is stopped.  I can add the drive, and start the array - but I want to make sure it will be XFS, and can't exactly tell when I will have the chance to set that.  (And where)

     

    I've poked around, but am really not certain where the formatting command comes in and how to configure as XFS.

     

    Thanks :)

    Re: Format XFS on replacement drive / Convert from RFS to XFS (discussion only)

    in General Support

    Posted

    5 hours ago, trurl said:

    ___________

    Scenario 1:

    In order to make parity valid without that disk you would have to go to Tools - New Config, set a new disk configuration without the disk, and resync (rebuild) parity.

     

    Then after parity is valid (with one less disk in the configuration), you could ADD the precleared disk. When you ADD a disk to an array with valid parity, unRAID will clear it unless it is already clear. This is so parity will remain valid. This is technically the only time a clear disk is required. A clear disk is all zeros so has no effect on parity.

     

    After the disk is added then unRAID will let you format it. Format is only writing an empty filesystem (just a top level directory with no folders or files in it). That write of an empty filesystem updates parity just like any other write operation, so formatting a disk that is in the array maintains parity.

     

    In the end, Scenario 1 means you have to rebuild parity, clear a disk, and format it.

     

     

    Ok so when I go to Tools:New Config...  There are four options under Retain Configuration.  I'm guessing I check parity and data (I have no cache)  Although I'm not sure as one of my data drives is missing, I'm not sure what the next step is after I click apply.

     

    I'm being extra careful here (of course).

     

    A quick search did not show me much information (at all) on the 'Retain Configuration" setting.

    Re: Format XFS on replacement drive / Convert from RFS to XFS (discussion only)

    in General Support

    Posted

    My 8TB is preclearing now, should wrap up tonight sometime I think.

     

    The 500GB is out of the array, all data was removed and files deleted.  When you say "new config"...  What do you mean exactly?

     

    My array is started, although as expected it is currently missing a disk.  Parity is valid, although Unraid says my array is unprotected...  (As it is missing a disk..  disk 5, not installed)

     

    Right now it WILL let me do a parity check and write corrections...  Even though I am missing a disk.  So that was what I was thinking I should do.  Update parity, add then add the new 8TB drive.

     

    Thanks for the help...

    Re: Format XFS on replacement drive / Convert from RFS to XFS (discussion only)

    in General Support

    Posted

    So I'm about to add an 8TB drive to my system.  (Parity is already 8TB)

     

    I had a 500GB drive I moved all the data to other drives.  I then removed that drive so I could put in the 8TB to do the pre-clear.

     

    The parity was valid before I removed the drive.  (Well I think it was, I actually checked the parity before I deleted everything and removed the drive).

     

    Before adding the 8TB to the array officially, I think I just need to update parity...  Which should essentially remove the 500GB from the array.

     

    I can then format and add (as XFS) the new 8TB?

     

     

    [Plugin] CA Fix Common Problems

    in Plugin Support

    Posted

    Settings --> Disk settings. Change the Thresholds to your wanted value.

     

    Yes I already set them to 100% - the problem is that my disks in general are at 100% capacity.  Not to the byte, but rounded up.  I guess we'll see the next time I restart the system if I get those 8 messages.

     

    Thanks...

    [Plugin] CA Fix Common Problems

    in Plugin Support

    Posted

    Thank you - unfortunately the Dynamix thread is even longer...  And Google isn't helping...  I clearly want to receive warnings for serious issues, but not that my shares are full.  One of the main benefits of unraid is long term storage, so I think a lot of people probably have disks bulging with data and add disks when they are full.

     

    Appreciate the hint in the right direction though - I'll change the settings to 100% but I fear I'll still get the warnings.

     

    (At the time I was doing something on my ipad, so the pointless messages coming up that I had a new email...  one by one...  Well it was a little distracting and was just hoping to prevent in the future)

     

    Thanks again !

    [Plugin] CA Fix Common Problems

    in Plugin Support

    Posted

    I just updated my FCP plugin, and upon reboot I got 8 friendly emails telling me I'm low on disk space on drives.

     

    I don't recall seeing those messages previously...  Any way to disable?  I mean I have a server like unraid because I intend to fill each drive and then add more...

     

    I did a quick search and couldn't find the answer with google, and 40 pages is a bit long to read through.  Any hints?

     

    Upgrading unRaid-5 to unRaid-6

    in Announcements

    Posted

    I suppose I could manually (even over the network from my main windows PC)...

     

    Edit the files manually...

     

    Create a syslinux directory, manually create the syslinux.cfg file within it...

    Delete the /config/plugins directory, etc..

     

    I just don't get it, the plugin from github seemed to execute fine.

    Upgrading unRaid-5 to unRaid-6

    in Announcements

    Posted

    Thank you RobJ.

     

    I have no syslinux folder.  I'm not angry, but frustrated b/c I was excited about taking the simple "plugin" approach to doing this, and now it's all messed up :)

     

    Incidentally I was able to get into v6 (but did not start the array) by typing:

     

    /bzimage initrd=/bzroot

     

    Based on the above, does that suggest an "easy" fix - or do I really have to start from scratch with the more complicated way of upgrading?

    Upgrading unRaid-5 to unRaid-6

    in Announcements

    Posted

    So I just ran "make_bootable".  I had to edit the batch file since syslinux.exe was now in the unRAID5 directory, but it eventually ran fine.

     

    Still no go.

     

    Get the "boot" prompt upon booting.

     

    I upgraded from unraid 5.06 release.  Not in a vm.  I previously had run the change permissions script.

     

    I'd rather not have to do a complete re-image and re-install with my license, etc.  So if anyone has any ideas of what's going on, I'm all ears :)

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

    in User Customizations

    Posted

    Thanks - I "more'd" the wrong files :)

     

    Both drives show:

     

    No SMART attributes are FAILING_NOW

     

    0 sectors were pending re-allocation before the start of the preclear.

    0 sectors were pending re-allocation after pre-read in cycle 1 of 1.

    0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.

    0 sectors are pending re-allocation at the end of the preclear,

        the number of sectors pending re-allocation did not change.

    0 sectors had been re-allocated before the start of the preclear.

    0 sectors are re-allocated at the end of the preclear,

        the number of sectors re-allocated did not change.

    ============================================================================

     

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

    in User Customizations

    Posted

    Can one of the experts comment on the attached log showing two separate pre-cleared disks?

     

    Thank you!

     

    FIRST DISK
Disk: /dev/sdi
smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     Hitachi HDS5C3030ALA630
Firmware Version: MEAOA5C0
User Capacity:    3,000,592,982,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Mon Sep  9 15:50:57 2013 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x84)	Offline data collection activity
				was suspended by an interrupting command from host.
				Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
				without error or no self-test has ever 
				been run.
Total time to complete Offline 
data collection: 		 (37267) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
				Auto Offline data collection on/off support.
				Suspend Offline collection upon new
				command.
				Offline surface scan supported.
				Self-test supported.
				No Conveyance Self-test supported.
				Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
				power-saving mode.
				Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
				General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 255) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
				SCT Error Recovery Control supported.
				SCT Feature Control supported.
				SCT Data Table supported.

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     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   054    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   139   139   024    Pre-fail  Always       -       550 (Average 451)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       12
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   020    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       44
10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       12
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       12
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       12
194 Temperature_Celsius     0x0002   193   193   000    Old_age   Always       -       31 (Min/Max 24/33)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

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 1
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    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.





SECOND DISK
Disk: /dev/sdh
smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     Hitachi HDS5C3030ALA630
Firmware Version: MEAOA5C0
User Capacity:    3,000,592,982,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Mon Sep  9 17:30:54 2013 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x84)	Offline data collection activity
				was suspended by an interrupting command from host.
				Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
				without error or no self-test has ever 
				been run.
Total time to complete Offline 
data collection: 		 (38166) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
				Auto Offline data collection on/off support.
				Suspend Offline collection upon new
				command.
				Offline surface scan supported.
				Self-test supported.
				No Conveyance Self-test supported.
				Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
				power-saving mode.
				Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
				General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 255) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
				SCT Error Recovery Control supported.
				SCT Feature Control supported.
				SCT Data Table supported.

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     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   054    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   143   143   024    Pre-fail  Always       -       538 (Average 441)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       12
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   020    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       46
10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       12
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       13
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       13
194 Temperature_Celsius     0x0002   193   193   000    Old_age   Always       -       31 (Min/Max 24/33)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

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 1
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    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.

root@Tower:/boot/preclear_reports#

    webGui on github

    in Announcements

    Posted

    Haven't read this entire thread, but have a couple thoughts on the "new" GUI...

     

    I like it overall, but:

     

    1)  I do not care for the waste of space with the bottom frame, with the copyright info on it.  That's just me, but that info could be shown in available space at the top.

    2)  The top frame, that doesn't move when you scroll...  Should probably have the headers for the columns for temperature, size, etc...

     

     

    The 5X3 Cage review - Norco, SuperMicro, iStarUSA and Icy Dock

    in Hardware

    Posted

    I just installed my Supermicro 5in3.

     

    The only bad part about the design is that it takes up the full square space of three 5 1/4 slots.  The tabs that I left in place (every third set) on my Antec 1200 case  to allow the 5in3's to slide in on top of, well, the Supermicro 5in3 was not happy with them there.  (of course the tabs in the "middle" of the 5in3 were already removed)

     

    Anyway - I wish it was a bit less long, but other than that it is a good design.  Well at least compared to the crappy Icy Dock.  Man - everyone should stay the hell away from that thing.  I HATE that 5in3 now.  It is the most expensive one, and the HORRIBLE cabling design is really annoying me.

     

    I say that because of course after installing my Supermicro beneath it, even though the cables were still connected, they must have been "jarred" enough to lose connectivity...  Even though the lights lit up, two of the five HD's reported as "missing".  I shut down, pushed in all cables, and for the heck of it re-seated all HD's.  Then those two HD's came back.

     

    Considering this happened before with one hard drive, just randomly, after the computer had been untouched for months...  Well, again, I regret ever buying that piece of junk.

     

    Ok I'll stop ranting now.

     

    (Full disclosure - there is no HD yet in my Supermicro, just preparing it for when I order a HD when the next sale comes...  So theoretically the Supermicro may be DOA and crap too and I just don't know it yet :)  )

    The 5X3 Cage review - Norco, SuperMicro, iStarUSA and Icy Dock

    in Hardware

    Posted

    Just want to add my thoughts.

     

    I have one Icy Dock 5in3, and I'm thinking of moving to the Supermicro for my next set of drive trays in my server.

     

    I personally think the Icy Dock sucks in two areas:

     

    1)  My fan was ridiculously loud to me.  I removed it, my Antec 1200 has enough airflow, so I'm good there.

    2)  The REALLY HORRIBLE design of the power inputs.  Unbelievable.  What a major PITA to install, with the tension on the cables from "jumpering" between the three power inputs, I have had a power problem or two.

     

    I love consistency so it annoys the heck out of me that I will likely have a server without a consistent look.  But I just cannot stand the thought of living through maybe 3 more 5in3's with the problems my Icy Dock has.

     

    I realize that I may have just got a bad fan, so perhaps #1 I shouldn't even mention.  But really the power inputs to this thing suck.

     

    I need to purchase a new 5in3 soon so I'll probably re-read this amazing thread before I settle on which one I'll buy.

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

    in User Customizations

    Posted

    I'm going to start reading through the 30 pages of comments here trying to understand my results.

     

    While doing so, in case someone wants to review the differences in my two new seagate 5900 Black Friday drives, I would be happy to listen.  (Both were upgraded to CE35 firmware prior to being installed in the unraid server)

     

    Thanks folks :)

     

     

    sda:

    Dec  5 04:02:13 Tower preclear_disk-diff[5090]: S.M.A.R.T. error count differences detected after pre-clear 

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: note, some 'raw' values may change, but not be an indication of a problem

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: 54c54

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: <   1 Raw_Read_Error_Rate     0x000f   100   100   006    Pre-fail  Always       -       56892

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: ---

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: >   1 Raw_Read_Error_Rate     0x000f   116   099   006    Pre-fail  Always       -       223497429

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: 58c58

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: <   7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       148

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: ---

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: >   7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       192141

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: 64c64

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: < 188 Command_Timeout         0x0032   100   253   000    Old_age   Always       -       0

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: ---

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: > 188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: 66,67c66,67

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: < 190 Airflow_Temperature_Cel 0x0022   070   068   045    Old_age   Always       -       30 (Lifetime Min/Max 28/30)

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: < 195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: ---

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: > 190 Airflow_Temperature_Cel 0x0022   067   064   045    Old_age   Always       -       33 (Lifetime Min/Max 28/36)

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: > 195 Hardware_ECC_Recovered  0x001a   048   039   000    Old_age   Always       

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: 70,73c70,73

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: < 199 UDMA_CRC_Error_Count    0x003e   200   253   000    Old_age   Always       -       0

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: < 240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       3998614552630

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: < 241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       8

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: < 242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       14705

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: ---

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: > 199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: > 240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       164535902142547

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: > 241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       3906080672

Dec  5 04:02:13 Tower preclear_disk-diff[5090]: > 242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       3669296420

     

    sdb:

     

    Dec  5 03:40:01 Tower preclear_disk-diff[4172]: S.M.A.R.T. error count differences detected after pre-clear 

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: note, some 'raw' values may change, but not be an indication of a problem

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: 54c54

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: <   1 Raw_Read_Error_Rate     0x000f   100   100   006    Pre-fail  Always       -       59966

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: ---

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: >   1 Raw_Read_Error_Rate     0x000f   120   099   006    Pre-fail  Always       -       242755498

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: 58c58

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: <   7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       147

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: ---

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: >   7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       187276

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: 64c64

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: < 188 Command_Timeout         0x0032   100   253   000    Old_age   Always       -       0

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: ---

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: > 188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: 66,67c66,67

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: < 190 Airflow_Temperature_Cel 0x0022   070   069   045    Old_age   Always       -       30 (Lifetime Min/Max 28/30)

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: < 195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: ---

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: > 190 Airflow_Temperature_Cel 0x0022   067   064   045    Old_age   Always       -       33 (Lifetime Min/Max 28/36)

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: > 195 Hardware_ECC_Recovered  0x001a   053   040   000    Old_age   Always       

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: 70,73c70,73

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: < 199 UDMA_CRC_Error_Count    0x003e   200   253   000    Old_age   Always       -       0

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: < 240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       79701708111925

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: < 241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       8

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: < 242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       14999

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: ---

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: > 199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: > 240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       125340030599250

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: > 241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       3906116822

Dec  5 03:40:01 Tower preclear_disk-diff[4172]: > 242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       3713874269

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

    in User Customizations

    Posted

    I just ran the pre-clear script on the two brand new seagate 5900 rpm drives from the newegg BF sale.

     

    My preclear logs have six tables of what I think is SMART data.

     

    Showing read error rates and seek error rates.  I'm kinda worried actually because the numbers aren't tiny or anything, and they are brand new drives.

     

    If I post the log can someone advise me what to do?

     

    Thanks :)

     

     

×
×
  • Create New...