Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Preclear Fail

ArdNsc
in General Support

Featured Replies

I want to replace a disk in my array and got myself a new 20TB Toshiba drive. However, the preclear failed in the first step (pre-read) after around 12hrs. Report attached. What does this indicate and what should I do?

Sep 17 23:13:41 preclear_disk_8572A0KNF4MJ_951720: Preclear Disk Version: 1.0.31

Sep 17 23:13:41 preclear_disk_8572A0KNF4MJ_951720: Disk size: 20000588955648

Sep 17 23:13:41 preclear_disk_8572A0KNF4MJ_951720: Disk blocks: 4882956288

Sep 17 23:13:41 preclear_disk_8572A0KNF4MJ_951720: Blocks (512 bytes): 39063650304

Sep 17 23:13:41 preclear_disk_8572A0KNF4MJ_951720: Block size: 4096

Sep 17 23:13:41 preclear_disk_8572A0KNF4MJ_951720: Start sector: 0

Sep 17 23:13:43 preclear_disk_8572A0KNF4MJ_951720: Pre-read: pre-read verification started 1 of 5 retries...

Sep 18 04:15:46 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: progress - 25% read @ 267 MB/s

Sep 18 09:45:29 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: progress - 50% read @ 238 MB/s

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: elapsed time - 11:49:59

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd command failed, exit code [1].

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 5291955+1 records out

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 11098034278400 bytes (11 TB, 10 TiB) copied, 42599.1 s, 261 MB/s

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: dd: error reading '/dev/sda': Input/output error

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 5291955+1 records in

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 5291955+1 records out

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 11098034278400 bytes (11 TB, 10 TiB) copied, 42599.1 s, 261 MB/s

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: dd: error reading '/dev/sda': Input/output error

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 5291955+1 records in

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 5291955+1 records out

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 11098034278400 bytes (11 TB, 10 TiB) copied, 42599.1 s, 261 MB/s

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: dd: error reading '/dev/sda': Input/output error

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 5291955+1 records in

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 5291955+1 records out

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 11098034278400 bytes (11 TB, 10 TiB) copied, 42599.1 s, 261 MB/s

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: dd: error reading '/dev/sda': Input/output error

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 5291955+1 records in

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 5291955+1 records out

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 11098034278400 bytes (11 TB, 10 TiB) copied, 42599.1 s, 261 MB/s

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: dd: error reading '/dev/sda': Input/output error

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 5291955+1 records in

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 5291955+1 records out

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 11098034278400 bytes (11 TB, 10 TiB) copied, 42599.1 s, 261 MB/s

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: dd: error reading '/dev/sda': Input/output error

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 5291955+1 records in

Sep 18 11:03:45 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 5291955+1 records out

Sep 18 11:03:46 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 11098034278400 bytes (11 TB, 10 TiB) copied, 42599.1 s, 261 MB/s

Sep 18 11:03:46 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: dd: /dev/sda: cannot seek: Invalid argument

Sep 18 11:03:46 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 5291955+1 records in

Sep 18 11:03:46 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 5291955+1 records out

Sep 18 11:03:46 preclear_disk_8572A0KNF4MJ_951720: Pre-Read: dd output: 11098034278400 bytes (11 TB, 10 TiB) copied, 42599.1 s, 261 MB/s

Sep 18 11:03:46 preclear_disk_8572A0KNF4MJ_951720: Pre-read: pre-read verification failed!

Sep 18 11:03:48 preclear_disk_8572A0KNF4MJ_951720: S.M.A.R.T.: Error:

Sep 18 11:03:48 preclear_disk_8572A0KNF4MJ_951720: S.M.A.R.T.:

Sep 18 11:03:48 preclear_disk_8572A0KNF4MJ_951720: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS

Sep 18 11:03:48 preclear_disk_8572A0KNF4MJ_951720: S.M.A.R.T.: Reallocated_Sector_Ct 0 -

Sep 18 11:03:48 preclear_disk_8572A0KNF4MJ_951720: S.M.A.R.T.: Power_On_Hours 0 -

Sep 18 11:03:48 preclear_disk_8572A0KNF4MJ_951720: S.M.A.R.T.: Temperature_Celsius 22 -

Sep 18 11:03:48 preclear_disk_8572A0KNF4MJ_951720: S.M.A.R.T.: Reallocated_Event_Count 0 -

Sep 18 11:03:48 preclear_disk_8572A0KNF4MJ_951720: S.M.A.R.T.: Current_Pending_Sector 0 -

Sep 18 11:03:48 preclear_disk_8572A0KNF4MJ_951720: S.M.A.R.T.: Offline_Uncorrectable 0 -

Sep 18 11:03:48 preclear_disk_8572A0KNF4MJ_951720: S.M.A.R.T.: UDMA_CRC_Error_Count 0 -

Sep 18 11:03:48 preclear_disk_8572A0KNF4MJ_951720: S.M.A.R.T.:

Sep 18 11:03:49 preclear_disk_8572A0KNF4MJ_951720: error encountered, exiting ...

preclear_disk_8572A0KNF4MJ_951720.txt

  • Quote
    • Community Expert

    That indicates a read error, but it would be good to also see the syslog, I assume it's connected via USB?

  • Quote
    • Author

    Thanks for the hint. Yes. Syslog indicates an USB disconnect at the time.

    Sep 18 11:03:42 * kernel: usb 2-5: USB disconnect, device number 3

    Sep 18 11:03:42 * kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=1s

    Sep 18 11:03:42 * kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x88 88 00 00 00 00 05 0b fb 32 08 00 00 08 00 00 00

    Sep 18 11:03:42 * kernel: I/O error, dev sda, sector 21675848200 op 0x0:(READ) flags 0x84700 phys_seg 256 prio class 3

    Sep 18 11:03:42 * kernel: device offline error, dev sda, sector 21675848200 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3

    Sep 18 11:03:42 * kernel: Buffer I/O error on dev sda, logical block 2709481025, async page read

    Sep 18 11:03:42 * kernel: device offline error, dev sda, sector 21675850248 op 0x0:(READ) flags 0x80700 phys_seg 256 prio class 3

    Sep 18 11:03:42 * kernel: device offline error, dev sda, sector 21675848200 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3

    Sep 18 11:03:42 * kernel: Buffer I/O error on dev sda, logical block 2709481025, async page read

    Sep 18 11:03:42 * kernel: device offline error, dev sda, sector 21675851776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3

    Sep 18 11:03:42 * kernel: Buffer I/O error on dev sda, logical block 2709481472, async page read

    Sep 18 11:03:42 * kernel: device offline error, dev sda, sector 21675855352 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 3

    Sep 18 11:03:42 * kernel: device offline error, dev sda, sector 21675855352 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3

    Sep 18 11:03:42 * kernel: Buffer I/O error on dev sda, logical block 2709481919, async page read

    Sep 18 11:03:42 * kernel: device offline error, dev sda, sector 21675858928 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 3

    Sep 18 11:03:42 * kernel: device offline error, dev sda, sector 21675858928 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3

    Sep 18 11:03:42 * kernel: Buffer I/O error on dev sda, logical block 2709482366, async page read

    Sep 18 11:03:42 * kernel: device offline error, dev sda, sector 21675862504 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 3

    Sep 18 11:03:42 * kernel: Buffer I/O error on dev sda, logical block 2709482813, async page read

    Sep 18 11:03:42 * kernel: Buffer I/O error on dev sda, logical block 2709483260, async page read

    Sep 18 11:03:42 * kernel: Buffer I/O error on dev sda, logical block 2709483707, async page read

    Sep 18 11:03:42 * kernel: Buffer I/O error on dev sda, logical block 2709484154, async page read

    Sep 18 11:03:42 * kernel: Buffer I/O error on dev sda, logical block 2709484601, async page read

    Sep 18 11:03:42 * kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache

    Sep 18 11:03:42 * kernel: sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK

    Sep 18 11:03:43 * emhttpd: offline: TOSHIBA_MG10ACA20TE_8572A0KNF4MJ (sda) 512 39063650304

    Sep 18 11:03:52 * kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

    Sep 18 11:03:58 * kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

    Sep 18 11:03:58 * kernel: usb 2-5: device not accepting address 4, error -62

    Sep 18 11:03:58 * kernel: usb 2-5: new SuperSpeed USB device number 5 using xhci_hcd

    Sep 18 11:03:58 * kernel: usb-storage 2-5:1.0: USB Mass Storage device detected

    Sep 18 11:03:58 * kernel: usb-storage 2-5:1.0: Quirks match for vid 174c pid 55aa: 400000

    Sep 18 11:03:58 * kernel: scsi host0: usb-storage 2-5:1.0

    Sep 18 11:03:59 * kernel: scsi 0:0:0:0: Direct-Access ASMT 2105 0 PQ: 0 ANSI: 6

    Sep 18 11:03:59 * kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0

    Sep 18 11:03:59 * kernel: sd 0:0:0:0: [sda] Spinning up disk...

    Sep 18 11:04:07 * kernel: ........ready

    Sep 18 11:04:07 * kernel: sd 0:0:0:0: [sda] 39063650304 512-byte logical blocks: (20.0 TB/18.2 TiB)

    Sep 18 11:04:07 * kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks

    Sep 18 11:04:07 * kernel: sd 0:0:0:0: [sda] Write Protect is off

    Sep 18 11:04:07 * kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00

    Sep 18 11:04:07 * kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

    Sep 18 11:04:07 * kernel: sd 0:0:0:0: [sda] Attached SCSI disk

    Sep 18 11:04:09 * emhttpd: online: TOSHIBA_MG10ACA20TE_8572A0KNF4MJ (sda) 512 39063650304

    Sep 18 11:04:09 * emhttpd: read SMART /dev/sda

    I cleared many disks successful with that usb dock in the past. I am running the preclear again now. If this also fails I will try a different usb-to-sata dockingstation. (Later the disk will be connected via sata internally obviously.)

    Edited by ArdNsc

  • Quote
    • Community Expert
    1 minute ago, ArdNsc said:

    Syslog indicates an USB disconnect at the time.

    That was the problem; USB tends to drop devices a lot.

  • Quote
    • Author
    5 hours ago, JorgeB said:

    USB tends to drop devices a lot.

    It is somehow strange, because I never had that problem with that USB dock in the past. It cleared several huge disks flawlessly. Only recently it started dropping disks, also unassigned devices I use for backups. Is there anything that I can do to make the USB connection more reliable? And by the way, is this an unraid specific problem? Do get devices dropped regularly but other OSes do handle that somehow different? (I also had huge problems in the past when trying to utilize a usb ethernet controller with unraid. It also tended to drop out randomly which killed the network connection in a way a hard reset was the only option back then.) Is there anything that can be done on the user side besides avoiding anything usb-related when using unraid?

    Regarding my current problem I can only replace the array disk and rebuild the array without doing a long pre-clear check with the new drive. (No more free internal slots). Even with dual parity that makes me a little bit worried.

  • Quote
    • Community Expert
    5 minutes ago, ArdNsc said:

    Is there anything that I can do to make the USB connection more reliable?

    You can try a different USB port, ideally on a different controller, or if it's using the newer UASP driver, it may be more stable with the old one. Post the output from lsusb -vt with a disk in the dock.

    6 minutes ago, ArdNsc said:

    is this an unraid specific problem?

    Nope, there are USB bridges that are better than others, but in general, USB is bad at error handling.

    7 minutes ago, ArdNsc said:

    Regarding my current problem I can only replace the array disk and rebuild the array without doing a long pre-clear check with the new drive. (No more free internal slots). Even with dual parity that makes me a little bit worried.

    You can also run an extended SMART test on the disk, it does a full surface scan internally, without transferring any data, so USB should not matter in that case, unless it still drops with an idle disk.

  • Quote
    • Author
    24 minutes ago, JorgeB said:

    Post the output from lsusb -vt with a disk in the dock

    /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M

    ID 1d6b:0002 Linux Foundation 2.0 root hub

    |__ Port 006: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M

    ID 051d:0002 American Power Conversion Uninterruptible Power Supply

    |__ Port 008: Dev 003, If 0, Class=Mass Storage, Driver=usb-storage, 480M

    ID 0781:5571 SanDisk Corp. Cruzer Fit

    /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/10p, 10000M

    ID 1d6b:0003 Linux Foundation 3.0 root hub

    |__ Port 005: Dev 005, If 0, Class=Mass Storage, Driver=usb-storage, 5000M

    ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge

    /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M

    ID 1d6b:0002 Linux Foundation 2.0 root hub

    /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M

    ID 1d6b:0003 Linux Foundation 3.0 root hub

  • Quote
    • Community Expert
    4 minutes ago, ArdNsc said:

    |__ Port 005: Dev 005, If 0, Class=Mass Storage, Driver=usb-storage, 5000M

    ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge

    I assume it's this one, and if so it's using the old usb-storage drive, but there's nothing using UASP, so it's not that.

  • Quote

    • 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...
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.