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.

preclear consistently failing on a samsung f4 drive

Featured Replies

so i've successfully precleared 3 western digital drives (2 EARS, 1 EADS) and had no hiccups whatsoever.

then i get to preclearing a samsung f4 drive (firmware updated) but consistently get the following error:

 

================================================================== 1.13

=                unRAID server Pre-Clear disk /dev/sdb

=              cycle 1 of 1, partition start on sector 64

= 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 - Verifying if the MBR is cleared.              DONE

=

Elapsed Time:  8:38:27

========================================================================1.13

==

== SORRY: Disk /dev/sdb MBR could NOT be precleared

==

== out4= 00000

== out5= 00000

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

dd: reading `/dev/sdb': Input/output error

0+0 records in

0+0 records out

0 bytes (0 B) copied, 0.000217369 s, 0.0 kB/s

0000000

root@Tower:/boot#

 

i've ran the preclear script on this drive 3 times now, on different sata ports and ensuring i use the -A switch.

it's pretty obvious the problem is an i/o error (they're all over the place on the syslog), but what could be the cause of this?

has anyone ran across this problem? any help would be appreciated.

error.jpg.1cc259a7d5314e6d53f962da739b7c06.jpg

  • Author

i would attach a syslog but it is GIGS big  :-\

i would attach a syslog but it is GIGS big  :-\

They compress really well.  Zip it and see how big it is.
  • Author

i decided to run a clear on the drive using hdtune.

i was able to create a problem i'm sure happened with unraid.

the disk would get "stuck" and start reallocating sectors.

ran seatools, drive was bad. oh well, rma here i come!

i decided to run a clear on the drive using hdtune.

i was able to create a problem i'm sure happened with unraid.

the disk would get "stuck" and start reallocating sectors.

ran seatools, drive was bad. oh well, rma here i come!

Glad you found the drive was defective BEFORE loading all your data on it.

Archived

This topic is now archived and is closed to further replies.

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.