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 Error

Featured Replies

Ok.  So I started Preclear on 4 of my 5 drives.

 

The fifth drive states the following error:

 

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 return from SMART Status command are:
ST =0x40
ERR=0x00
NS =0x04
SC =0xf0
CL =0x5f
CH =0x70
SEL=0x40
A mandatory SMART command failed: exiting.  To continue, add one or more '-T permissive' options.$
Do you wish to continue?
(Answer Yes to continue. Capital 'Y', lower case 'es'):

 

Any help would be greatly appreciated.

 

Edit:  This is the only drive on my SFF-8087 controller cards.  The other 4 drives on attached directly to my mobo.

Try re-seating the SATA cable first.  Then run a SMART report and post the results here.

  • Author

I have checked the cable connections.

 

What is the command to run a SMART report?

Silicon image controller?

 

Does it do the same thing every time? I've seen sil cards cause that once and then work fine.  ???

I have checked the cable connections.

 

What is the command to run a SMART report?

 

smartctl -a /dev/sdx

 

where sdx is the offending drive

  • Author

Silicon image controller?

 

Does it do the same thing every time? I've seen sil cards cause that once and then work fine.  ???

 

I have tried it 3 times and the same result happens.

  • Author

I have checked the cable connections.

 

What is the command to run a SMART report?

 

smartctl -a /dev/sdx

 

where sdx is the offending drive

 

That command returned:

 

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.

I'm in the same boat.  I precleared a Hitachi drive today and it went fine.  Not I'm trying to preclear a Samsung drive in the same bay and get the same error as the OP.

  • Author

I got the SMART test running.

 

smartctl -tlong /dev/sdb

 

208 Minutes later and we'll be done.

I just used the -D option on preclear and let it run anyway.  It appears to be going.  Weird thing was that it said there was a FAT16 partition on the disk.  I have never seen that before.  It was supposed to be a new Samsung F4EG from New Egg.  I did reflash it with JP1 firmware, so maybe that created a FAT16 partition.

 

I was using 1.11 of preclear.

  • Author

I decided to run the short test first.

 

smartctl -tshort /dev/sdb

 

2 Minutes later and we'll be done.

  • Author

The short smartctl test completed without error.

 

I will go ahead and start the long test now.

  • Author

The long test completed without error.

 

As PeterB said it here I went ahead and started the preclear anyways as it was a compatibility issue.

 

There appears to be some incompatibility between some HBAs (LSI SAS2008-based?) and the method which preclear and unMENU use to obtain SMART data and temperatures.  Simple smartctl commands, from the command line, appear to work okay.  Hopefully, Joe will be able to address this problem soon.

 

In the meantime we just have to live with it - the preclear will still work, but you don't get any SMART reports.

As PeterB said it here I went ahead and started the preclear anyways as it was a compatibility issue.

 

... and as I've posted in another thread, I discovered that preclear has its own option to eliminate the problem:

 

run the preclear with the '-D' option (eg 'preclear_disk.sh -D /dev/sdx'), and all will be well.

  • Author

AHH.  What does the -D option do exactly?  How would I incorporate the -A option for starting at 64?

 

I did not do the -D option, will this be a problem?  So far so good w/ just /boot/preclear_disk.sh -A /dev/sdb

AHH.  What does the -D option do exactly?  How would I incorporate the -A option for starting at 64?

 

one after the other (i.e. preclear_disk.sh -A -D /dev/sdX)

  • Author

Thanks.

AHH.  What does the -D option do exactly?

 

The '-D' supresses the use of the '-d ata' on all the smartctl commands which preclear issues.

 

I did not do the -D option, will this be a problem?  So far so good w/ just /boot/preclear_disk.sh -A /dev/sdb

 

At best, you will simply get error messages everytime preclear issues a smartctl command.  At worst, you won't get any SMART data reported.  However, the disk will still be cleared perfectly well.

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.