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


Recommended Posts

Hi Joe,

 

I restarted the machine but copied the log first.

 

There doesn't seem to be much in there?

 

Booted up and started the preclear went off to work.  Got back, logged in again and crash by the looks of it?

 

Jun  2 07:24:43 Ridcully in.telnetd[6260]: connect from 192.168.0.100 (192.168.0.100)
Jun  2 07:24:48 Ridcully login[6261]: ROOT LOGIN  on '/dev/pts/0' from '192.168.0.100'
Jun  2 07:25:52 Ridcully in.telnetd[7029]: connect from 192.168.0.100 (192.168.0.100)
Jun  2 07:25:57 Ridcully login[7030]: ROOT LOGIN  on '/dev/pts/0' from '192.168.0.100'
Jun  2 07:26:22 Ridcully kernel: NTFS driver 2.1.29 [Flags: R/W MODULE].
Jun  2 07:26:34 Ridcully kernel:  sdg: unknown partition table
Jun  2 07:27:04 Ridcully in.telnetd[7592]: connect from 192.168.0.100 (192.168.0.100)
Jun  2 07:27:09 Ridcully login[7593]: ROOT LOGIN  on '/dev/pts/0' from '192.168.0.100'
Jun  2 13:09:32 Ridcully kernel: mdcmd (35): spindown 1
Jun  2 13:09:33 Ridcully kernel: mdcmd (36): spindown 2
Jun  2 14:21:46 Ridcully kernel: md: sync done. time=25215sec
Jun  2 14:21:46 Ridcully kernel: md: recovery thread sync completion status: 0
Jun  2 15:21:53 Ridcully kernel: mdcmd (37): spindown 0
Jun  2 15:21:54 Ridcully kernel: mdcmd (38): spindown 3
Jun  2 16:33:25 Ridcully in.telnetd[24394]: connect from 192.168.0.100 (192.168.0.100)
Jun  2 16:33:29 Ridcully login[24395]: ROOT LOGIN  on '/dev/pts/0' from '192.168.0.100'

 

 

syslog.txt

Link to comment

Looks like a crash of emhttp to me too:

Jun  2 07:22:00 Ridcully emhttp: unRAID System Management Utility version 5.0-beta6a

Jun  2 07:22:00 Ridcully emhttp: Copyright © 2005-2011, Lime Technology, LLC

Jun  2 07:22:00 Ridcully emhttp: Pro key detected, GUID: 1B1C-0B29-0096-F5B0E2401223

Jun  2 07:22:00 Ridcully emhttp: get_config_idx: fopen /boot/config/flash.cfg: No such file or directory - assigning defaults

Jun  2 07:22:00 Ridcully emhttp: diskSpinupGroupMask.0 not found

Jun  2 07:22:00 Ridcully kernel: emhttp[6119]: segfault at 0 ip b75ba96c sp bfeb2880 error 4 in libc-2.11.1.so[b758a000+15c000]

 

Send an e-mail to lime-tech to report it.  ([email protected])

 

Joe L.

Link to comment

My preclears finished successfully on 3 new 2TB drives using Preclear_disk.sh v1.11 and the latest unmenu additions to be able to see the results of preclear via MyMain. I stopped the array added the 3 disks to the array and formatted them. All is well. When I went back to MyMain page the preclear results are still there.

 

Is this by design?

 

Do they fall out eventually?

 

or is the idea for it to live with the drive for its life?

 

Where are the (assuming here) files that MyMain is reading to display in a browser? Any other info would be appreciated.

Link to comment

My preclears finished successfully on 3 new 2TB drives using Preclear_disk.sh v1.11 and the latest unmenu additions to be able to see the results of preclear via MyMain. I stopped the array added the 3 disks to the array and formatted them. All is well. When I went back to MyMain page the preclear results are still there.

 

Is this by design?

 

Do they fall out eventually?

 

or is the idea for it to live with the drive for its life?

 

Where are the (assuming here) files that MyMain is reading to display in a browser? Any other info would be appreciated.

I think if you hover your mouse pointer over those "results" lines in myMain you'll get a clue how to keep them from showing in the future.

 

 

Link to comment

Hi again Joe,

 

I changed SATA ports on that HDD and it completed this time but with an error...

 

2cpz2oo.jpg

 

===========================================================================
=                unRAID server Pre-Clear disk /dev/sdf
=                       cycle 1 of 1
= Disk Pre-Clear-Read completed                                 DONE
= Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
= Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
= Step 5 of 10 - Clearing MBR code area                         DONE
= Step 6 of 10 - Setting MBR signature bytes                    DONE
= Step 7 of 10 - Setting partition 1 to precleared state        DONE
= Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
= Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
= Step 10 of 10 - Testing if the clear has been successful.     DONE
=
Disk Temperature: 32C, Elapsed Time:  12:19:26
============================================================================
==
== SORRY: Disk /dev/sdf MBR could NOT be precleared
==
== out4= 00092
== out5= 00092
============================================================================
1+0 records in
1+0 records out
0000000 0000 0000 0000 0000 0000 0000 0000 0000
512 bytes (512 B) copied*
0000700 0000 0000 0000 003f 0000 8871 e8e0 0000
, 0.0245598 s, 20.8 kB/s
0000720 0000 0000 0000 0000 0000 0000 0000 0000
*
0000760 0000 0000 0000 0000 0000 0000 0000 5c5c
0001000

 

I did a smart report too but it seems Ok?

 

root@Ridcully:~# smartctl -a /dev/sdf
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 HDS5C3020ALA632
Serial Number:    ML0220F30VB0JD
Firmware Version: ML6OA580
User Capacity:    2,000,398,934,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:    Sat Jun  4 09:01:40 2011 BST
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:  (0x85) Offline data collection activity
                                        was aborted by an interrupting command from host.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 249) Self-test routine in progress...
                                        90% of test remaining.
Total time to complete Offline
data collection:                 (23815) 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   134   134   054    Pre-fail  Offline      -       100
  3 Spin_Up_Time            0x0007   167   167   024    Pre-fail  Always       -       359 (Average 298)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       10
  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   146   146   020    Pre-fail  Offline      -       29
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       58
10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       10
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       10
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       10
194 Temperature_Celsius     0x0002   193   193   000    Old_age   Always       -       31 (Min/Max 22/34)
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
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%        34         -

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.

 

...I've also managed to break my USB stick moving my server around but that's seperate issue... :P

Link to comment

Hi again Joe,

 

I changed SATA ports on that HDD and it completed this time but with an error...

 

2cpz2oo.jpg

 

===========================================================================
=                unRAID server Pre-Clear disk /dev/sdf
=                       cycle 1 of 1
= Disk Pre-Clear-Read completed                                 DONE
= Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
= Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
= Step 5 of 10 - Clearing MBR code area                         DONE
= Step 6 of 10 - Setting MBR signature bytes                    DONE
= Step 7 of 10 - Setting partition 1 to precleared state        DONE
= Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
= Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
= Step 10 of 10 - Testing if the clear has been successful.     DONE
=
Disk Temperature: 32C, Elapsed Time:  12:19:26
============================================================================
==
== SORRY: Disk /dev/sdf MBR could NOT be precleared
==
== out4= 00092
== out5= 00092
============================================================================
1+0 records in
1+0 records out
0000000 0000 0000 0000 0000 0000 0000 0000 0000
512 bytes (512 B) copied*
0000700 0000 0000 0000 003f 0000 8871 e8e0 0000
, 0.0245598 s, 20.8 kB/s
0000720 0000 0000 0000 0000 0000 0000 0000 0000
*
0000760 0000 0000 0000 0000 0000 0000 0000 5c5c
0001000

 

I did a smart report too but it seems Ok?

 

root@Ridcully:~# smartctl -a /dev/sdf
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 HDS5C3020ALA632
Serial Number:    ML0220F30VB0JD
Firmware Version: ML6OA580
User Capacity:    2,000,398,934,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:    Sat Jun  4 09:01:40 2011 BST
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:  (0x85) Offline data collection activity
                                       was aborted by an interrupting command from host.
                                       Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 249) Self-test routine in progress...
                                       90% of test remaining.
Total time to complete Offline
data collection:                 (23815) 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   134   134   054    Pre-fail  Offline      -       100
 3 Spin_Up_Time            0x0007   167   167   024    Pre-fail  Always       -       359 (Average 298)
 4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       10
 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   146   146   020    Pre-fail  Offline      -       29
 9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       58
10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       10
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       10
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       10
194 Temperature_Celsius     0x0002   193   193   000    Old_age   Always       -       31 (Min/Max 22/34)
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
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%        34         -

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.

 

...I've also managed to break my USB stick moving my server around but that's seperate issue... :P

You are using a very old version of the preclear script.   It has an issue when used with newer version of unRAID because of the way the shell in the newer unRAID interperts numbers in its "echo" statement.  

 

To see the current version type:

preclear_disk.sh -v

 

You can probably fix in a few seconds the issue on that disk caused by running the old version of the preclear script by running:

echo -ne "\0252" | dd bs=1 count=1 seek=511 of=/dev/sdf

echo -ne "\0125" | dd bs=1 count=1 seek=510 of=/dev/sdf

 

Then, test if it is marked as precleared by typing:

preclear-disk.sh -t /dev/sdf

 

Download the current version and use it for all future clearing of disks.  I'll bet you are 8 or 10 versions out-of-date. 

(The current version is 1.11)

 

 

Link to comment

Ah... I know what I've done. The first run was on the new version. When I changed the sata port I also snapped my USB stick in two. I then went back to a backup I had but I forgot to upgrade the preclear script again.

 

Many thanks Joe, once I get my key sorted for the replacement USB stick I'll be back up and running!

Link to comment
  • 3 weeks later...

I started a preclear (latest version of the script and beta) a couple days ago on a 1.5TB drive on an external USB dock.  It was going fine, but then the script (or perhaps my putty session) seems to have stopped updating.  The activity light on the dock is still flashing valiantly, but I have no idea what the status is, as I believe it should be done by now.

 

What do I do?

Link to comment

I started a preclear (latest version of the script and beta) a couple days ago on a 1.5TB drive on an external USB dock.  It was going fine, but then the script (or perhaps my putty session) seems to have stopped updating.  The activity light on the dock is still flashing valiantly, but I have no idea what the status is, as I believe it should be done by now.

 

What do I do?

Log in using a different putty session.  Check out your syslog.  Otherwise nobody will know what is happening.

communications over USB are very slow. It might still be running.  Did you invoke it under "screen"?  If not, when the putty session drops, the process will terminate (but that would not explain the blinking lights)

Link to comment

Can I fetch the log from the Web UI?  Because that shows nothing more than the movers activity.  I am pretty sure the putty window did not crash, because it's still open and I can send keystrokes to it.  It just seems like the script 'forgot' to continue updating the progress.

 

The light is still blinking.  I will go look up now how to fetch the log from a new putty session.

 

UPDATE:  Yes, the system log in a new putty session shows nothing more than the log in the WEB UI.  Just mover info...

Link to comment

Can I fetch the log from the Web UI?  Because that shows nothing more than the movers activity.  I am pretty sure the putty window did not crash, because it's still open and I can send keystrokes to it.  It just seems like the script 'forgot' to continue updating the progress.

 

The light is still blinking.  I will go look up now how to fetch the log from a new putty session.

 

UPDATE:  Yes, the system log in a new putty session shows nothing more than the log in the WEB UI.  Just mover info...

if you type

top

in that putty window, do you see the preclear processes?

Link to comment

Hmm... I'm not sure what processes those are, exactly, but I don't see anything that says preclear.  There are 117 running though and they don't all fit in the window, how would I search for it?

it would be processes at the top of the list and most likely be "dd if=XXXXXXX"

 

Joe L.

Link to comment

There is one taking 100% CPU called dd...

 

top - 09:20:26 up 5 days, 16:55,  2 users,  load average: 1.82, 1.94, 2.00
Tasks: 116 total,   3 running, 113 sleeping,   0 stopped,   0 zombie
Cpu(s): 15.9%us, 18.0%sy,  0.0%ni, 56.2%id,  9.5%wa,  0.0%hi,  0.3%si,  0.0%st
Mem:   4072980k total,  3957936k used,   115044k free,   123652k buffers
Swap:        0k total,        0k used,        0k free,  3499048k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
32208 root      20   0 10348 8872  644 R  100  0.2   3521:25 dd
32209 root      20   0  2248  624  464 S   49  0.0   1647:58 sed
22002 root      20   0 76532 6152  608 S    3  0.2 121:43.78 shfs
6875 nobody    20   0 20944 6452 5240 S    2  0.2   3:07.45 smbd
21704 root      20   0     0    0    0 S    2  0.0 144:45.24 unraidd
  141 root      20   0     0    0    0 D    1  0.0  12:26.39 sync_supers
  450 root      20   0     0    0    0 S    0  0.0  12:09.90 kswapd0
1415 root      20   0 56940 1876 1148 S    0  0.0   3:47.79 emhttp
16944 root      20   0     0    0    0 S    0  0.0   0:30.27 flush-9:13
    1 root      20   0   828  280  240 S    0  0.0   0:04.81 init

 

 

Link to comment

There is one taking 100% CPU called dd...

 

top - 09:20:26 up 5 days, 16:55,  2 users,  load average: 1.82, 1.94, 2.00
Tasks: 116 total,   3 running, 113 sleeping,   0 stopped,   0 zombie
Cpu(s): 15.9%us, 18.0%sy,  0.0%ni, 56.2%id,  9.5%wa,  0.0%hi,  0.3%si,  0.0%st
Mem:   4072980k total,  3957936k used,   115044k free,   123652k buffers
Swap:        0k total,        0k used,        0k free,  3499048k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
32208 root      20   0 10348 8872  644 R  100  0.2   3521:25 dd
32209 root      20   0  2248  624  464 S   49  0.0   1647:58 sed
22002 root      20   0 76532 6152  608 S    3  0.2 121:43.78 shfs
6875 nobody    20   0 20944 6452 5240 S    2  0.2   3:07.45 smbd
21704 root      20   0     0    0    0 S    2  0.0 144:45.24 unraidd
  141 root      20   0     0    0    0 D    1  0.0  12:26.39 sync_supers
  450 root      20   0     0    0    0 S    0  0.0  12:09.90 kswapd0
1415 root      20   0 56940 1876 1148 S    0  0.0   3:47.79 emhttp
16944 root      20   0     0    0    0 S    0  0.0   0:30.27 flush-9:13
    1 root      20   0   828  280  240 S    0  0.0   0:04.81 init

 

 

100% of a cpu seems odd, as it would normally be waiting on the disk I/O.

Time to post a zipped copy of your syslog.  Odds are the disk being written issued some kind of error.

 

Joe L.

Link to comment

It appears  as if the USB drive and the network interface were both reset at some point.

 

I'm asuming the drive being cleared is /dev/sdf.

 

The errors are here:

Jun 19 22:34:44 Cooper kernel: usb 1-1.4: reset high speed USB device using ehci_hcd and address 5

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf] Unhandled error code

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf]  Result: hostbyte=0x07 driverbyte=0x00

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf] CDB: cdb[0]=0x28: 28 00 34 be 22 d8 00 00 f0 00

Jun 19 22:34:45 Cooper kernel: end_request: I/O error, dev sdf, sector 884875992

Jun 19 22:34:45 Cooper kernel: Buffer I/O error on device sdf, logical block 884875992

Jun 19 22:34:45 Cooper kernel: Buffer I/O error on device sdf, logical block 884875993

Jun 19 22:34:45 Cooper kernel: Buffer I/O error on device sdf, logical block 884875994

Jun 19 22:34:45 Cooper kernel: Buffer I/O error on device sdf, logical block 884875995

Jun 19 22:34:45 Cooper kernel: Buffer I/O error on device sdf, logical block 884875996

Jun 19 22:34:45 Cooper kernel: Buffer I/O error on device sdf, logical block 884875997

Jun 19 22:34:45 Cooper kernel: Buffer I/O error on device sdf, logical block 884875998

Jun 19 22:34:45 Cooper kernel: Buffer I/O error on device sdf, logical block 884875999

Jun 19 22:34:45 Cooper kernel: Buffer I/O error on device sdf, logical block 884876000

Jun 19 22:34:45 Cooper kernel: Buffer I/O error on device sdf, logical block 884876001

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf] Unhandled error code

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf]  Result: hostbyte=0x07 driverbyte=0x00

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf] CDB: cdb[0]=0x28: 28 00 34 be 23 c8 00 00 10 00

Jun 19 22:34:45 Cooper kernel: end_request: I/O error, dev sdf, sector 884876232

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf] Unhandled error code

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf]  Result: hostbyte=0x07 driverbyte=0x00

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf] CDB: cdb[0]=0x28: 28 00 34 be 23 d8 00 00 f0 00

Jun 19 22:34:45 Cooper kernel: end_request: I/O error, dev sdf, sector 884876248

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf] Unhandled error code

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf]  Result: hostbyte=0x07 driverbyte=0x00

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf] CDB: cdb[0]=0x28: 28 00 34 be 24 c8 00 00 10 00

Jun 19 22:34:45 Cooper kernel: end_request: I/O error, dev sdf, sector 884876488

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf] Unhandled error code

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf]  Result: hostbyte=0x07 driverbyte=0x00

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf] CDB: cdb[0]=0x28: 28 00 34 be 22 d8 00 00 08 00

Jun 19 22:34:45 Cooper kernel: end_request: I/O error, dev sdf, sector 884875992

Jun 19 22:34:45 Cooper kernel: usb 1-1.4: USB disconnect, address 5

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf] Unhandled error code

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf]  Result: hostbyte=0x07 driverbyte=0x00

Jun 19 22:34:45 Cooper kernel: sd 10:0:0:0: [sdf] CDB: cdb[0]=0x28: 28 00 34 be 22 d8 00 00 08 00

Jun 19 22:34:45 Cooper kernel: end_request: I/O error, dev sdf, sector 884875992

Jun 19 22:34:45 Cooper kernel: usb 1-1.4: new high speed USB device using ehci_hcd and address 6

Jun 19 22:35:00 Cooper kernel: usb 1-1.4: device descriptor read/64, error -110

Jun 19 22:35:16 Cooper kernel: usb 1-1.4: device descriptor read/64, error -110

Jun 19 22:35:16 Cooper kernel: usb 1-1.4: new high speed USB device using ehci_hcd and address 7

Jun 19 22:35:31 Cooper kernel: usb 1-1.4: device descriptor read/64, error -110

Jun 19 22:35:46 Cooper kernel: usb 1-1.4: device descriptor read/64, error -110

Jun 19 22:35:46 Cooper kernel: usb 1-1.4: new high speed USB device using ehci_hcd and address 8

Jun 19 22:35:51 Cooper kernel: usb 1-1.4: device descriptor read/8, error -110

Jun 19 22:35:56 Cooper kernel: usb 1-1.4: device descriptor read/8, error -110

Jun 19 22:35:57 Cooper kernel: usb 1-1.4: new high speed USB device using ehci_hcd and address 9

Jun 19 22:36:02 Cooper kernel: usb 1-1.4: device descriptor read/8, error -110

Jun 19 22:36:07 Cooper kernel: usb 1-1.4: device descriptor read/8, error -110

Jun 19 22:36:07 Cooper kernel: hub 1-1:1.0: unable to enumerate USB device on port 4

Jun 19 23:35:22 Cooper kernel: e1000e: eth0 NIC Link is Down

Jun 19 23:35:22 Cooper dhcpcd[1271]: eth0: carrier lost

Jun 19 23:35:34 Cooper dhcpcd[1271]: eth0: carrier acquired

Jun 19 23:35:34 Cooper dhcpcd[1271]: eth0: rebinding lease of 192.168.1.2

Jun 19 23:35:35 Cooper kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Jun 19 23:35:35 Cooper dhcpcd[1271]: eth0: acknowledged 192.168.1.2 from 192.168.1.1

Jun 19 23:35:35 Cooper dhcpcd[1271]: eth0: checking for 192.168.1.2

Jun 19 23:35:40 Cooper dhcpcd[1271]: eth0: leased 192.168.1.2 for 86400 seconds

 

I doubt if that disk is responding to anything at this point.

Link to comment

Hmm... yeah you're right it is /dev/sdf.  I was messing with the router a while ago, but didn't realize that would mess up the preclear.  But that does make sense considering the putty session.  Should I restart the server to kill the process?

 

The only reason I am doing this via USB is because all the slots are full in my case.  Is there a better way to do it?

Link to comment

Hmm... yeah you're right it is /dev/sdf.  I was messing with the router a while ago, but didn't realize that would mess up the preclear.  But that does make sense considering the putty session.  Should I restart the server to kill the process?

 

The only reason I am doing this via USB is because all the slots are full in my case.  Is there a better way to do it?

kill 32208

will probably terminate the "dd" process.

A "Control-C" in the putty window where you started it might work.

 

Joe L.

Link to comment

Apologies if this has already been asked and answered - couldn't find it.

 

If I've started a preclear session via a DOS window telnet on my Windows PC, can I shutdown the PC and then restart the PC later and get back into the same preclear session? And if so, will the preclear still have been running on the unRAID server (so I would see the progress made)? Or does the preclearing stop when the telnet session ends?

Link to comment

Apologies if this has already been asked and answered - couldn't find it.

 

If I've started a preclear session via a DOS window telnet on my Windows PC, can I shutdown the PC and then restart the PC later and get back into the same preclear session? And if so, will the preclear still have been running on the unRAID server (so I would see the progress made)? Or does the preclearing stop when the telnet session ends?

No it will kill it with the telnet session. Google "unraid screen with preclear"

http://www.lime-technology.com/wiki/index.php?title=Configuration_Tutorial

Go to the 6.1 section "Preclearing With Screen" has all the answers for you, I reference it all the time because I forget the keystrokes myself.

Link to comment

No it will kill it with the telnet session. Google "unraid screen with preclear"

http://www.lime-technology.com/wiki/index.php?title=Configuration_Tutorial

Go to the 6.1 section "Preclearing With Screen" has all the answers for you, I reference it all the time because I forget the keystrokes myself.

 

Thanks, I never knew about Screen. Just to confirm my reading of the Screen documentation: if I install Screen and run preclear via Screen, I CAN quit the Screen telnet session and the preclear will still be running. I can also then shut down the PC and re-attach to Screen (and the still running preclear session) after I restart the PC. Is my understanding correct?

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.