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


Recommended Posts

Hi,

 

I hope that you can help.

 

I have two WD 2TB EARS drive without jumper and I am running 4.7 UnRaid. I have tried to run the preclear utility a few times now and wither it locks up after several hours or it will effect the performance of the server to such an extent I have quit it (ie I have been watching a few films whilst the Preclear is running without a problem then suddenly the video comes to a halt or very nearly, killing the preclear script allows the server to work fine again.)

 

Should I be able to run the script on a working server?

 

Thanks

 

Ridley

yes. It can be run on a working server. You might be running out of memory for all you are trying to do.

 

Did you look in the system log for the cause?  It could be almost anything.  Remember the preclear script will exercise your server, if it is using a marginal power supply, it might be affected.  On my older server the vibration from the disk being heavily accessed caused a poor quality power splitter to lose connection with a drive.  If your disk is sharing a channel with another, and you are running cache_dirs, it could easily be possible for you to run into disk contention issue.

 

You can use the following options to limit the resources the preclear script will use:

      -w size  = write block size in bytes

      -r size  = read block size in bytes

      -b count = number of blocks to read at a time

The default "write block size" is 2048k

The default "read block size" is set by the "units" returned by the fdisk command. Depending on the drive it could be as small as 32k and as large as 8meg.

The default "number of blocks to read at a time" is 200.

 

Joe L.

Link to comment

Does the disk respond at all?

 

What happens if you type

fdisk -l /dev/sdX

 

What happens when you type

smartctl -d ata -a /dev/sdX

 

What happens if you type:

smartctl -a /dev/sdX

 

what happens if you power cycle and try the above commands once more?

 

EARS drives have a habit of locking up and not responding until after a power cycle.

 

Joe L.

Link to comment

I power cycled before I read your post and now all drives are working.  I'm seeing this same issue on two different client builds.  Every time I've seen the issue, the following has been true:

 

- The drives have been 2 TB WD EARS.  One pair I'm preclearing from sector 63 with jumpers on, the other pair I'm preclearing from sector 64 with no jumpers (and using the -A option in preclear).  I also generally use the -n option in preclear to skip the preread as all of these drives have passed preclear multiple times before, I'm only using them to test the drive bays and disk controllers.

 

- The drives have been connected to a Supermicro AOC-SASLP-MV8 card using forward breakout cables.  I've never once seen this issue crop up on the motherboard SATA ports or the SIL3132 controller cards I use.

 

As the drives are working I'm going to let them finish this round of preclear.  If/when I see the issue again, I'll certainly give your commands a try and report the results.  So it sounds like this is an issue with WD EARS drives specifically?

Link to comment

So it sounds like this is an issue with WD EARS drives specifically?

yes.  They lock up.

 

most frequently it is after a jumper change and the lock up is detected in a subsequent pre-clear.  Did you change jumper settings on the EARS drive that locked up just prior to the pre-clear that gave the error?

Link to comment

How much RAM do you have?  Does your server successfully pass memtest for 24 hours or more?  That sounds like it could be a RAM issue to me.  Also, can you successfully preclear one disk at a time instead of both at once?

 

The system uses a 2.8Ghz Celeron CPU, 1GB RAM. Yes it does, or did when I last tried it, pass the memtest.

 

I have attached a syslog, the errors at the end of the log (or rather what unmenu reports as errors) are what occurred as soon as I started, again, the preclear on one drive.

 

Ridley

syslog-2011-02-15.zip

Link to comment

Nope, no jumper changes on any of the drives.  The one set were jumpered as soon as I removed them from the packaging, and the second set have never seen a jumper.

 

There generally seems to be a problem with EARS and unraid. i have noticed that many-many times in the forums. i, personally, had problems with 2 EARS drives (fresh from the box and jumpered). they would get stuck always at the same point of preclear. i tried unjumpering, i performed extensive smart and factory tests, i even tried SpinRite and they showed no errors. But they lock in unraid (at least in preclear).

Obviously, i did not want to risk it so i RMA'd them....

Link to comment

Does the disk respond at all?

 

What happens if you type

fdisk -l /dev/sdX

 

What happens when you type

smartctl -d ata -a /dev/sdX

 

What happens if you type:

smartctl -a /dev/sdX

 

what happens if you power cycle and try the above commands once more?

 

EARS drives have a habit of locking up and not responding until after a power cycle.

 

Joe L.

 

Here's the responses to those commands:

 

cGQOx.png

 

By the way, this time the first drive (SDB) is locking up like normal, but the second drive (SDC) isn't showing up at all.  Preclear says that it isn't a valid block device.  SDA is the flash drive.

 

If this is just a case of bad drives, that's no big deal, I'll just RMA them.  However, what perplexes me is that these same two drives have passed at least 10 passes of preclear on other drive slots in the same server.  There are only four drive slots on which these drives lock up - all of which are connected to one of the ports on a SASLP card via a forward breakout cable.  I wonder if the breakout cable might be bad?  I'm pretty sure I tested it before, but I might have to test it again just to be sure.

 

Well shit...I just power cycled and now both drives are working in two of these suspect 4 drive bays.  My main concern is this - is it safe to ship these drives with the server to the client?  Or should I hang onto them, RMA them and ship some other drives with the server?  I happen to have two spares that should do nicely.

Link to comment

I think I messed something up, I was in the middle of a preclear, I closed the terminal by acsident and then I re tried and this is the terminal display,

 

 

root@Tower:/boot# preclear_disk.sh /dev/sdc

Pre-Clear unRAID Disk /dev/sdc

################################################################## 1.6

 

Error: preclear_disk unable to continue.

smartctl is unable to run on /dev/sdc with the -d ata option.

smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build)

Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

 

=== START OF INFORMATION SECTION ===

Model Family:    Seagate Barracuda 7200.10 family

Device Model:    ST3160815AS

Serial Number:    6RA04W5L

Firmware Version: 3.AAC

User Capacity:    160,041,885,696 bytes

Device is:        In smartctl database [for details use: -P show]

ATA Version is:  7

ATA Standard is:  Exact ATA specification draft version not indicated

Local Time is:    Sat Feb 19 01:49:04 2011 EST

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

 

Error SMART Status command failed

Please get assistance from http://smartmontools.sourceforge.net/

Register values returned from SMART Status command are:

ST =0x40

ERR=0x00

NS =0x00

SC =0xc0

CL =0x9d

CH =0xa1

SEL=0x40

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.$

 

 

What do I do?

Link to comment

I think I messed something up, I was in the middle of a preclear, I closed the terminal by acsident and then I re tried and this is the terminal display,

 

 

root@Tower:/boot# preclear_disk.sh /dev/sdc

Pre-Clear unRAID Disk /dev/sdc

################################################################## 1.6

 

Error: preclear_disk unable to continue.

smartctl is unable to run on /dev/sdc with the -d ata option.

smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build)

Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

 

=== START OF INFORMATION SECTION ===

Model Family:     Seagate Barracuda 7200.10 family

Device Model:     ST3160815AS

Serial Number:    6RA04W5L

Firmware Version: 3.AAC

User Capacity:    160,041,885,696 bytes

Device is:        In smartctl database [for details use: -P show]

ATA Version is:   7

ATA Standard is:  Exact ATA specification draft version not indicated

Local Time is:    Sat Feb 19 01:49:04 2011 EST

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

 

Error SMART Status command failed

Please get assistance from http://smartmontools.sourceforge.net/

Register values returned from SMART Status command are:

ST =0x40

ERR=0x00

NS =0x00

SC =0xc0

CL =0x9d

CH =0xa1

SEL=0x40

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.$

 

 

What do I do?

You might need to power cycle the disk.  If a disk will not run the SMART report, I would not want it in my server.  It might not have anything to do with the pre-clear script itself.  (It just uses smartctl to read the disk temperature as it progresses.)

 

On the command line, try

smartctl -d ata -a /dev/sdc

If it still fails, try removing power, re-applying power, and then try the smartctl command once more.

 

if the command still fails you might have had a disk fail, or a cable work its way loose.

 

Link to comment

root@Tower:/boot# smartctl -d ata -a /dev/sdc
smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.10 family
Device Model:     ST3160815AS
Serial Number:    6RA04W5L
Firmware Version: 3.AAC
User Capacity:    160,041,885,696 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Sat Feb 19 09:13:02 2011 EST
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:  (0x82) Offline data collection activity
                                        was completed without error.
                                        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:                 ( 430) 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:        (  54) minutes.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   114   097   006    Pre-fail  Always       -       60364721
  3 Spin_Up_Time            0x0003   098   098   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       70
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   077   060   030    Pre-fail  Always       -       55248323
  9 Power_On_Hours          0x0032   088   088   000    Old_age   Always       -       10643
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       104
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   070   055   045    Old_age   Always       -       30 (Lifetime Min/Max 24/33)
194 Temperature_Celsius     0x0022   030   045   000    Old_age   Always       -       30 (0 17 0 0)
195 Hardware_ECC_Recovered  0x001a   078   071   000    Old_age   Always       -       182015860
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0
202 Data_Address_Mark_Errs  0x0032   100   253   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     10638         -

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.

 

Smart report seems fine but still fails the preclear script

Link to comment

root@Tower:/boot# smartctl -d ata -a /dev/sdc
smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.10 family
Device Model:     ST3160815AS
Serial Number:    6RA04W5L
Firmware Version: 3.AAC
User Capacity:    160,041,885,696 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Sat Feb 19 09:13:02 2011 EST
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:  (0x82) Offline data collection activity
                                       was completed without error.
                                       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:                 ( 430) 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:        (  54) minutes.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
 1 Raw_Read_Error_Rate     0x000f   114   097   006    Pre-fail  Always       -       60364721
 3 Spin_Up_Time            0x0003   098   098   000    Pre-fail  Always       -       0
 4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       70
 5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
 7 Seek_Error_Rate         0x000f   077   060   030    Pre-fail  Always       -       55248323
 9 Power_On_Hours          0x0032   088   088   000    Old_age   Always       -       10643
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       104
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   070   055   045    Old_age   Always       -       30 (Lifetime Min/Max 24/33)
194 Temperature_Celsius     0x0022   030   045   000    Old_age   Always       -       30 (0 17 0 0)
195 Hardware_ECC_Recovered  0x001a   078   071   000    Old_age   Always       -       182015860
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0
202 Data_Address_Mark_Errs  0x0032   100   253   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     10638         -

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.

 

Smart report seems fine but still fails the preclear script

What version of the preclear script are you using?  I see in your prior post it was 1.6. 

 

I know I had a typo in an earlier version that might have resulted in the type of error you are experiencing.

 

What version of unRAID?

 

You can always try the "-D" option to the preclear script.

 

Joe L.

Link to comment

root@Tower:/boot# preclear_disk.sh -D /dev/sdc
Pre-Clear unRAID Disk /dev/sdc
################################################################## 1.6

Error: preclear_disk unable to continue.
smartctl is unable to run on /dev/sdc with the  option.
smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.10 family
Device Model:     ST3160815AS
Serial Number:    6RA04W5L
Firmware Version: 3.AAC
User Capacity:    160,041,885,696 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Sat Feb 19 09:26:55 2011 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Error SMART Status command failed
Please get assistance from http://smartmontools.sourceforge.net/
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.$

 

I am running 4.7. I have tried restarting twice, I am not sure if that is a full power cycle. Thanks for all your help Joe you are very quick :)

Link to comment

root@Tower:/boot# preclear_disk.sh -D /dev/sdc
Pre-Clear unRAID Disk /dev/sdc
################################################################## 1.6

Error: preclear_disk unable to continue.
smartctl is unable to run on /dev/sdc with the  option.
smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.10 family
Device Model:     ST3160815AS
Serial Number:    6RA04W5L
Firmware Version: 3.AAC
User Capacity:    160,041,885,696 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Sat Feb 19 09:26:55 2011 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Error SMART Status command failed
Please get assistance from http://smartmontools.sourceforge.net/
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.$

 

I am running 4.7. I have tried restarting twice, I am not sure if that is a full power cycle. Thanks for all your help Joe you are very quick :)

Power cycle means removing power, with the power switch... not just rebooting.

 

Link to comment

damn just tried a full power cycle, still no go on the drive

 

here is the syslog looks like it is throwing a bunch of errors when I try to run the script.

 

Feb 19 09:54:04 Tower in.telnetd[5285]: connect from 192.168.1.110 (192.168.1.110) (Routine)
Feb 19 09:54:08 Tower login[5286]: ROOT LOGIN  on `pts/0' from `192.168.1.110' (Logins)
Feb 19 09:54:27 Tower ata_id[5386]: HDIO_GET_IDENTITY failed for '/dev/block/8:32'  (Minor Issues)
Feb 19 09:54:27 Tower kernel:  sdc: sdc1 (Drive related)
Feb 19 09:54:27 Tower kernel: ------------[ cut here ]------------
Feb 19 09:54:27 Tower kernel: WARNING: at drivers/ata/libata-core.c:5186 ata_qc_issue+0x10b/0x308() (Minor Issues)
Feb 19 09:54:27 Tower kernel: Hardware name: TA785 A2+
Feb 19 09:54:27 Tower kernel: Modules linked in: tun md_mod xor ide_gd_mod atiixp ahci r8169 mvsas libsas scst scsi_transport_sas (Drive related)
Feb 19 09:54:27 Tower kernel: Pid: 5395, comm: smartctl Not tainted 2.6.32.9-unRAID #8 (Errors)
Feb 19 09:54:27 Tower kernel: Call Trace: (Errors)
Feb 19 09:54:27 Tower kernel:  [<c102449e>] warn_slowpath_common+0x60/0x77 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c10244c2>] warn_slowpath_null+0xd/0x10 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11b624d>] ata_qc_issue+0x10b/0x308 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11ac0ba>] ? scsi_init_sgtable+0x5b/0x76 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11ba260>] ata_scsi_translate+0xd1/0xff (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11a816c>] ? scsi_done+0x0/0xd (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11a816c>] ? scsi_done+0x0/0xd (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11baa40>] ata_sas_queuecmd+0x120/0x1d7 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11bc6df>] ? ata_scsi_pass_thru+0x0/0x21d (Errors)
Feb 19 09:54:27 Tower kernel:  [<f843f69a>] sas_queuecommand+0x65/0x20d [libsas] (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11a816c>] ? scsi_done+0x0/0xd (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11a82c0>] scsi_dispatch_cmd+0x147/0x181 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11ace4d>] scsi_request_fn+0x351/0x376 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11269a8>] __generic_unplug_device+0x26/0x29 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c112934a>] blk_execute_rq_nowait+0x56/0x73 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11293dc>] blk_execute_rq+0x75/0x91 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11292cc>] ? blk_end_sync_rq+0x0/0x28 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11295fa>] ? blk_recount_segments+0x16/0x24 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11250c6>] ? blk_rq_bio_prep+0x47/0x78 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11ac58a>] scsi_execute+0xbf/0x113 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11bb6d0>] ata_cmd_ioctl+0xf8/0x1ba (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11bb940>] ata_sas_scsi_ioctl+0x1ae/0x1e8 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11334a5>] ? radix_tree_lookup_slot+0xd/0xf (Errors)
Feb 19 09:54:27 Tower kernel:  [<c1048a7f>] ? find_get_page+0x1d/0x79 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c104a179>] ? filemap_fault+0xb8/0x305 (Errors)
Feb 19 09:54:27 Tower kernel:  [<f843f33d>] sas_ioctl+0x36/0x43 [libsas] (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11a94c8>] scsi_ioctl+0x299/0x2ad (Errors)
Feb 19 09:54:27 Tower kernel:  [<f843f307>] ? sas_ioctl+0x0/0x43 [libsas] (Errors)
Feb 19 09:54:27 Tower kernel:  [<c11b326d>] sd_ioctl+0x80/0x8c (Errors)
Feb 19 09:54:27 Tower kernel:  [<c112a420>] __blkdev_driver_ioctl+0x50/0x62 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c112ad1c>] blkdev_ioctl+0x8b0/0x8dc (Errors)
Feb 19 09:54:27 Tower kernel:  [<c1131e2d>] ? kobject_get+0x12/0x17 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c112b0f8>] ? get_disk+0x4a/0x61 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c101b028>] ? kmap_atomic+0x14/0x16 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c104cbfe>] ? get_page_from_freelist+0x2e4/0x344 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c104cd4f>] ? __alloc_pages_nodemask+0xdb/0x42f (Errors)
Feb 19 09:54:27 Tower kernel:  [<c104f1e3>] ? lru_cache_add_lru+0x22/0x24 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c105fe77>] ? page_add_new_anon_rmap+0x33/0x40 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c108b6c6>] block_ioctl+0x2a/0x32 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c108b69c>] ? block_ioctl+0x0/0x32 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c10769d5>] vfs_ioctl+0x22/0x67 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c1076f33>] do_vfs_ioctl+0x478/0x4ac (Errors)
Feb 19 09:54:27 Tower kernel:  [<c105c983>] ? expand_downwards+0x109/0x136 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c1076f93>] sys_ioctl+0x2c/0x45 (Errors)
Feb 19 09:54:27 Tower kernel:  [<c1002935>] syscall_call+0x7/0xb (Errors)
Feb 19 09:54:27 Tower kernel: ---[ end trace d6049db1ddcfbea3 ]---

 

Link to comment

ok, I know it was dumb but I decided to try reformatting it by just adding it to the array. I added it, re formatted it, the removed it, (I forgot that I would have to rebuild parity after but whatever) then I tried the script and it is working. I am still not sure what happened but it is working now, thank you for all your work Joe.

Link to comment

I am not sure if this has been asked before - or even if it is a stupid question... But can multiple disks be pre-cleared on the same machine at the same time - i.e concurrently?

I am building a new box with 8x new Hitachi drives and wondered if I could save time by running pre-clear on more than one drive at the same time.

 

Thank you

K

Link to comment

Just a question. I received 2 new 2T EARS drives today, and I have a FW updated F4 preclearing now.

 

For some reason screen is not working on my install. Is it OK to just open multiple terminal windows, telnet to UnRAID and run the preclear script from all of them at the same time. I understand you can do that with screen, but not sure if normal terminal (Mac OS X) is OK.

 

Thanks.

Link to comment

screen does not play nice with OS X terminal if I remember correctly.  Download and use iTerm (free, do a google search).  So long as screen is installed properly on the unRAID box it should work just fine.

 

 

You can open multiple telnet connections and do it that way do you have to disable all sleep functionality on your Mac or the telnet connection will be lost and the preclear script will stop.

Link to comment

screen does not play nice with OS X terminal if I remember correctly.  Download and use iTerm (free, do a google search).  So long as screen is installed properly on the unRAID box it should work just fine.

 

 

You can open multiple telnet connections and do it that way do you have to disable all sleep functionality on your Mac or the telnet connection will be lost and the preclear script will stop.

 

Thanks. I have iTerm already, I just didn't think to try screen with it. I installed it (screen) with the UnMenu package manager so I assume the install should be fine. Good to know about the sleep thing, too.

Link to comment

screen does not play nice with OS X terminal if I remember correctly.  Download and use iTerm (free, do a google search).  So long as screen is installed properly on the unRAID box it should work just fine.

 

 

You can open multiple telnet connections and do it that way do you have to disable all sleep functionality on your Mac or the telnet connection will be lost and the preclear script will stop.

I think it will if you first set the terminal type to xterm like this:

 

TERM=xterm

export TERM

 

Then invoke screen and it probably will be fine.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.