I've followed the instructions, and in the root directory of my flash drive I have preclear_disk.sh

 

However, in the console whenever I type the command I get "no such file or directory" or "command not found".

 

Am I typing the command incorrectly?  What exactly should I be typing?

 

Thanks

Try

 

./preclear_disk.sh

 

And see if that works better.

 

type /preclear_disk.sh

 

you might have to type "chmod +x /preclear_disk.sh" first

 

No such file on both of those suggestions unfortunately 

type "ls /" and post the results.

No such file on both of those suggestions unfortunately 

Did you download the file?

 

Did you un-zip it to your flash drive?

 

did you change directory to the flash drive before attempting to invoke the command?

 

cd /boot

 

To see if the file it there type:

ls -l /boot

 

To invoke it, type

cd /boot

preclear_disk.sh /dev/sdX

 

or use the full path to it:

 

/boot/preclear_disk.sh /dev/sdX

I'm not sure how I extract the log from the telnet session, but what I see on the screen is several words in dark blue - tmp and boot are highlighted in green, init@ is highlighted in a light blue?

No such file on both of those suggestions unfortunately 

Did you download the file?

 

Did you un-zip it to your flash drive?

 

did you change directory to the flash drive before attempting to invoke the command?

 

cd /boot

 

To see if the file it there type:

ls -l /boot

 

To invoke it, type

cd /boot

preclear_disk.sh /dev/sdX

 

or use the full path to it:

 

/boot/preclear_disk.sh /dev/sdX

 

Thanks Joe...spot on, sorted 

Anyone know if this is seriously bad news?  Did a SMART test on the drive using Seatools before putting into the unRAID.  Pre-clearing came up with this:

 

Nov 1 18:05:56 Tower preclear_disk-start[8219]: === START OF INFORMATION SECTION ===

Nov 1 18:05:56 Tower preclear_disk-start[8219]: Device Model: ST32000542AS

Nov 1 18:05:56 Tower preclear_disk-start[8219]: Serial Number: 6XW03Z6V

Nov 1 18:05:56 Tower preclear_disk-start[8219]: Firmware Version: CC35

Nov 1 18:05:56 Tower preclear_disk-start[8219]: User Capacity: 2,000,398,934,016 bytes

Nov 1 18:05:56 Tower preclear_disk-start[8219]: Device is: Not in smartctl database [for details use: -P showall]

Nov 1 18:05:56 Tower preclear_disk-start[8219]: ATA Version is: 8

Nov 1 18:05:56 Tower preclear_disk-start[8219]: ATA Standard is: ATA-8-ACS revision 4

Nov 1 18:05:56 Tower preclear_disk-start[8219]: Local Time is: Mon Nov 1 18:05:56 2010 GMT

Nov 1 18:05:56 Tower preclear_disk-start[8219]: SMART support is: Available - device has SMART capability.

Nov 1 18:05:56 Tower preclear_disk-start[8219]: SMART support is: Enabled

Nov 1 18:05:56 Tower preclear_disk-start[8219]:

Nov 1 18:05:56 Tower preclear_disk-start[8219]: Error SMART Status command failed

Nov 1 18:05:56 Tower preclear_disk-start[8219]: Please get assistance from http://smartmontools.sourceforge.net/

Nov 1 18:05:56 Tower preclear_disk-start[8219]: Register values returned from SMART Status command are:

Nov 1 18:05:56 Tower preclear_disk-start[8219]: ST =0x40

Nov 1 18:05:56 Tower preclear_disk-start[8219]: ERR=0x00

Nov 1 18:05:56 Tower preclear_disk-start[8219]: NS =0x10

Nov 1 18:05:56 Tower preclear_disk-start[8219]: SC =0xa8

Nov 1 18:05:56 Tower preclear_disk-start[8219]: CL =0x88

Nov 1 18:05:56 Tower preclear_disk-start[8219]: CH =0xe0

Nov 1 18:05:56 Tower preclear_disk-start[8219]: SEL=0x40

Nov 1 18:05:56 Tower preclear_disk-start[8219]: A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

 

This was within minutes of the pre-clearing started, now 33% complete and no further drive related lines in the syslog?

Pre-clearing on my 2TB is now in post-read - but at 57% complete this drive has now been clearing for over 20 hours!  Is that right?

 

Can I just close the telnet session or would that be a bad move?  Next time I'll just pre-clear from the main console methinks...

Pre-clearing on my 2TB is now in post-read - but at 57% complete this drive has now been clearing for over 20 hours!  Is that right?

 

Can I just close the telnet session or would that be a bad move?  Next time I'll just pre-clear from the main console methinks...

 

NO, DO NOT close the telnet session or you will loose everything that has been done so far.

 

20 hours for a 2TB drive is about normal.  I did 2 passes on a 1.5TB drive recently and it took 1.5 days or so for the 2 passes.  You are doing 1 pass on a 500GB larger disc.  Let it go, it will be fine, and you will thank yourself later.

 

 

For future reference you may want to look into "screen" there is a package to install it via unMenu and you can do some google searching on how to use it.  Once you get it installed you can start a preclear and then disconnect and be totally fine.

Pre-clearing on my 2TB is now in post-read - but at 57% complete this drive has now been clearing for over 20 hours!  Is that right?

 

Can I just close the telnet session or would that be a bad move?  Next time I'll just pre-clear from the main console methinks...

 

Closing the session would be an exceptionally bad move.

 

Yes, running from the console works.  There is also a "screen" package that allows you to keep a telnet session running in the background and reattach to it at will.  But if you're already running, it is too late to install and use screen.

 

Just be patient - your 20hours is not at all unusual.

Oh well...although I've mentioned 20 hours, at the rate it's going I'm looking at approx 40 hours for preclearing.  Plus I really need to reboot my main PC!

 

Really frustrating thing is that I'm trying to run YAMJ from my PC, but the network shares on the unRAID keep coming up as unavailable?

Pre-clearing on my 2TB is now in post-read - but at 57% complete this drive has now been clearing for over 20 hours!  Is that right?

Yes, quite normal.  Most people experience between 30 and 35 hours to clear a 2TB drive.  With multiple concurrent drives being cleared, it will take even longer.  IT looks like you are on track for about 40 hours or so with what you've got running.

 

You can stop them at any time, but you'll start back at the beginning the next time you invoke the program.