Jump to content

Telnet conn to preclear lost-what action should I take to complete preclear


Camel

Recommended Posts

I started a telnet session to start preclear, I lost the connection and have the connection to the tower back up now. I have precleared before and I know it will take about 24 hrs. Should I wait a couple of days and just restart the tower?

 

Or can I use the unRaid (myMain) to watch the reads/writes and/or will it show me a completed preclear? The reads are continuing upward at this point. I have never used myMain to watch this before and do not know what to expect. I am using preclear 1.6 and have UnRaid 4.7.

 

Thanks very much for any info about this,

Camel

Link to comment

Check out the screen utility (available in unMenu's packages http://lime-technology.com/forum/index.php?topic=5568.msg51814#msg51814) or do your preclears from the console. You could also nohup the job but the only feedback would be the reports in /boot/preclear_reports.

 

Also, you should update to a more recent version. It's up to 1.13, 7 or so releases newer.

 

With the number of OOB drive failures lately I'm uncomfortable adding drives that haven't passed a minimum of two preclears.

Link to comment

Thanks for the info!

 

For some strange reason, unless the connection was not interrupted as I thought, my terminal telnet sessions are running again with updating screens.

 

I should mention I am preclearing on three 2T drives at the same time. I realize this will take some time, especially with little memory.

 

I have unMENU 1.3 installed (which is fantastic), can I do a preclear form unMENU? I am missing that if so, please advise if that is possible. Otherwise I will update my preclear to the newest version and run it again. It is great to know that some folks run it twice. I thought it was a sure thing after running once.

 

One other problem I have though;

I cannot log onto the main menu and when I try to log in on :89 it gives me a 500 internal error. I still have a console though and the preclears are running through terminal. Any ideas? Should I start a different thread for this issue. Obviously I will let the preclear run before I restart but are there any commands available to run on console to troubleshoot the gui?

 

Thanks again,

Camel

 

 

Just as I finished this reply one of my telnet sessions dropped (I did not close it-dam). Will I be able to start this process over with this particular drive after stopping mid stream?

 

I am having a feeling that since I lost the gui and one telnet session that I will lose everything else eventually... having to start over. Would it be best to do the preclear from console? I am not familiar with 'screen' and would like to preclear three 2T drives at the same time (or may that be the problem?);

 

 

unRAID server Pre-Clear disk /dev/sdd

=               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

=  **** This will take a while... you can follow progress below:

=

=

Disk Temperature: 28C, Elapsed Time:  17:28:39

40577+21 records in

40577+21 records out

85121597440 bytes (85 GB) copied, 5154.91 s, 16.5 MB/s

Wrote  85,121,597,440  bytes out of  2,000,398,934,016  bytes (4% Done)

Connection closed by foreign host.

 

 

 

 

 

Another went down differently, not sure what this means;

 

 

=                unRAID server Pre-Clear disk /dev/sde

=              cycle 1 of 1, partition start on sector 64

= Disk Pre-Read in progress: 27% complete

= ( 554,383,872,000  bytes of  2,000,398,934,016  read )

 

 

=

Disk Temperature: 30C, Elapsed Time:  17:55:13

./preclear_disk.sh: line 1109: 23891 Killed                  dd if=$1 of=/dev/null count=1 bs=$units skip=$skip_b >/dev/null 2>&1

./preclear_disk.sh: line 1109: 23892 Killed                  dd if=$1 of=/dev/null count=1 bs=$units iflag=direct >/dev/null 2>&1

./preclear_disk.sh: line 1109: 23893 Killed                  dd if=$1 of=/dev/null count=1 bs=$units skip=$skip_b2 >/dev/null 2>&1

./preclear_disk.sh: line 1109: 23894 Killed                  dd if=$1 of=/dev/null count=1 bs=$units skip=$blocks iflag=direct >/dev/null 2>&1

./preclear_disk.sh: line 1109: 23895 Killed                  dd if=$1 of=/dev/null count=1 bs=$units skip=$skip_b3 >/dev/null 2>&1

Connection closed by foreign host.

 

Link to comment

Ok, got v1.13

 

All three sessions were incomplete using 1.6 though on one disk the process almost finished. And it is this disk that I now see this upon doing preclear;

 

 

Pre-Clear unRAID Disk /dev/sdf

################################################################## 1.13

Device Model:    ST2000DL003-9VT166

Serial Number:    5YD1LTKB

Firmware Version: CC32

User Capacity:    2,000,398,934,016 bytes

 

Disk /dev/sdf: 2000.3 GB, 2000398934016 bytes

255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors

Units = sectors of 1 * 512 = 512 bytes

Disk identifier: 0x00000000

 

  Device Boot      Start        End      Blocks  Id  System

/dev/sdf1              64  3907029167  1953514552    0  Empty

Partition 1 does not end on cylinder boundary.

########################################################################

invoked as  ./preclear_disk.sh -A /dev/sdf

########################################################################

(-A option elected, partition will start on sector 64)

Are you absolutely sure you want to clear this drive?

(Answer Yes to continue. Capital 'Y', lower case 'es'): Yes

 

 

 

 

Why am I now seeing sdf '1' ? Will the preclear remove this 'partition'?

 

 

 

Thanks for all the great direction and help,

Camel

Link to comment

Ok, got v1.13

 

All three sessions were incomplete using 1.6 though on one disk the process almost finished. And it is this disk that I now see this upon doing preclear;

 

 

Pre-Clear unRAID Disk /dev/sdf

################################################################## 1.13

Device Model:     ST2000DL003-9VT166

Serial Number:    5YD1LTKB

Firmware Version: CC32

User Capacity:    2,000,398,934,016 bytes

 

Disk /dev/sdf: 2000.3 GB, 2000398934016 bytes

255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors

Units = sectors of 1 * 512 = 512 bytes

Disk identifier: 0x00000000

 

   Device Boot      Start         End      Blocks   Id  System

/dev/sdf1              64  3907029167  1953514552    0  Empty

Partition 1 does not end on cylinder boundary.

########################################################################

invoked as  ./preclear_disk.sh -A /dev/sdf

########################################################################

(-A option elected, partition will start on sector 64)

Are you absolutely sure you want to clear this drive?

(Answer Yes to continue. Capital 'Y', lower case 'es'): Yes

 

 

 

 

Why am I now seeing sdf '1' ? Will the preclear remove this 'partition'?

 

 

 

Thanks for all the great direction and help,

Camel

 

Once the disk is zeroed, preclear adds a "preclear signature" to the disk.  The preclear signature includes creating the disk partition you are seeing.  This is 100% normal.  If you rerun preclear, the partition is removed as a result of writing zeros to the disk, and then is recreated as I just explained.

 

Note that once the zeroing phase of the preclear completes, the disk IS precleared.  The post read validation does not have to complete (although it should to let it verify the disk has precleared successfully).  If the post read validation fails, the preclear signature is altered so it is no longer valid.  If your preclears didn't finish, but were in th post read, they should show the preclear signature.  I think there is a new preclear option to just run the post-read verify (you'll have to check), which would save you some time.

Link to comment

Thanks for all the replies!

 

I am still having problems,

 

I keep getting this connection closed by foreign host;

 

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

=                unRAID server Pre-Clear disk /dev/sdd

=              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

=  **** This will take a while... you can follow progress below:

 

=

Disk Temperature: 31C, Elapsed Time:  13:44:36

23388+15 records in

23388+15 records out

49065172992 bytes (49 GB) copied, 2550.45 s, 19.2 MB/s

Wrote  49,065,172,992  bytes out of  2,000,398,934,016  bytes (2% Done)

Connection closed by foreign host.

 

 

 

And I lose my gui (main and unMENU) but still have my console running with no problem. I have one disk still copying zeros via telnet but I suspect the same thing will happen to this disk but closer to the end of the preclear process for the third drive I am doing, as I posted the results before;

 

 

 

=                unRAID server Pre-Clear disk /dev/sde

=              cycle 1 of 1, partition start on sector 64

= Disk Pre-Read in progress: 27% complete

= ( 554,383,872,000  bytes of  2,000,398,934,016  read )

 

 

=

Disk Temperature: 30C, Elapsed Time:  17:55:13

./preclear_disk.sh: line 1109: 23891 Killed                  dd if=$1 of=/dev/null count=1 bs=$units skip=$skip_b >/dev/null 2>&1

./preclear_disk.sh: line 1109: 23892 Killed                  dd if=$1 of=/dev/null count=1 bs=$units iflag=direct >/dev/null 2>&1

./preclear_disk.sh: line 1109: 23893 Killed                  dd if=$1 of=/dev/null count=1 bs=$units skip=$skip_b2 >/dev/null 2>&1

./preclear_disk.sh: line 1109: 23894 Killed                  dd if=$1 of=/dev/null count=1 bs=$units skip=$blocks iflag=direct >/dev/null 2>&1

./preclear_disk.sh: line 1109: 23895 Killed                  dd if=$1 of=/dev/null count=1 bs=$units skip=$skip_b3 >/dev/null 2>&1

Connection closed by foreign host.

 

 

 

 

 

I want to preclear three drives at the same time but maybe I should try one at a time. I am wondering if this is a issue with just having 512 memory. I would not think so but I do not know what else to think and I would hate to do one drive at a time.

 

My other though is, can I setup another machine or laptop to run the preclear script? I have adapters I can attach any drive to any machine. Then I could do one disk at a time on each separate machine.

 

Appreciate any thoughts, clues, or ideas.

 

All the best,

Camel

Link to comment

Ah,

 

Booting off another machine with the flash, great idea. I will try that.

 

My last disk did finish;

 

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

=                unRAID server Pre-Clear disk /dev/sdf

=               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

= Post-Read in progress: 31% complete.  

(  of  2,000,398,934,016  bytes read )

Elapsed Time:  23:28:56

./preclear_disk.sh: line 1087: 0+()%(243201) : syntax error: operand expected (error token is ")%(243201) ")

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

==  ST2000DL003-9VT166    5YD1LTKB

== Disk /dev/sdf has been successfully precleared

== with a starting sector of 64

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

** Changed attributes in files: /tmp/smart_start_sdf  /tmp/smart_finish_sdf

               ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

     Raw_Read_Error_Rate =   114     111            6        ok          60419416

        Spin_Retry_Count =   100     100           97        near_thresh 0

       Unknown_Attribute =   100     100           99        near_thresh 0

 Airflow_Temperature_Cel =    66      68           45        near_thresh 34

     Temperature_Celsius =    34      32            0        ok          34

  Hardware_ECC_Recovered =    36      30            0        ok          60419416

No SMART attributes are FAILING_NOW

 

0 sectors were pending re-allocation before the start of the preclear.

0 sectors were pending re-allocation after pre-read in cycle 1 of 1.

0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.

0 sectors are pending re-allocation at the end of the preclear,

   the number of sectors pending re-allocation did not change.

0 sectors had been re-allocated before the start of the preclear.

0 sectors are re-allocated at the end of the preclear,

   the number of sectors re-allocated did not change.

 

 

This is acceptable...?

 

 

Thanks very much for all the help. If the issue is memory I shall take things a bit slower or spread out the "work" but I hope this will not be an issue down the road if I plan on streaming. At this point I just want simple backup jobs, TM, Rsync, and some file shares.

 

 

All the best,

Camel

 

 

Woops-sorry.

 

Tried to run again before restarting the tower and a failed attempt with this;

 

 

/boot# preclear_disk.sh -A /dev/sde

 

Pre-Clear unRAID Disk /dev/sde

################################################################## 1.13

Device Model:    WDC WD20EARS-00MVWB0

Serial Number:    WD-WCAZA2249478

Firmware Version: 51.0AB51

User Capacity:    2,000,398,934,016 bytes

 

Disk /dev/sde: 2000.3 GB, 2000398934016 bytes

255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors

Units = sectors of 1 * 512 = 512 bytes

Disk identifier: 0x00000000

 

Disk /dev/sde doesn't contain a valid partition table

 

 

 

I guess I will restart and try these one by one.

 

Link to comment

Hate to drag this on but I am learning at the same time.

 

One issue of reading what I think is a successful preclear since it states so but with error token and a question about my preclear on the console.

 

First, this is my successful preclear done via telnet. I guess the post read did not finish, is that related the error token? And can I consider this a successful preclear?

 

 

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

=                unRAID server Pre-Clear disk /dev/sdf

=               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

= Post-Read in progress: 31% complete.  

(  of  2,000,398,934,016  bytes read )

Elapsed Time:  23:28:56

./preclear_disk.sh: line 1087: 0+()%(243201) : syntax error: operand expected (error token is ")%(243201) ")

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

==  ST2000DL003-9VT166    5YD1LTKB

== Disk /dev/sdf has been successfully precleared

         

         EDIT: I did a test on this disk so regardless of the post read I assume I can now use this, could someone just verify that? And is there any sense in doing just a post-read?;

 

Pre-Clear unRAID Disk /dev/sdf

################################################################## 1.13

Device Model:     ST2000DL003-9VT166

Serial Number:    5YD1LTKB

Firmware Version: CC32

User Capacity:    2,000,398,934,016 bytes

 

Disk /dev/sdf: 2000.3 GB, 2000398934016 bytes

255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors

Units = sectors of 1 * 512 = 512 bytes

Disk identifier: 0x00000000

 

  Device Boot      Start         End      Blocks   Id  System

/dev/sdf1              64  3907029167  1953514552    0  Empty

Partition 1 does not end on cylinder boundary.

########################################################################

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

==

== DISK /dev/sdf IS PRECLEARED with a starting sector of 64

==

 

 

Secondly,

 

I am preclearing a disk that would not complete using telnet -

 

Device Model:     WDC WD20EARS-00MVWB0

Serial Number:    WD-WCAZA2249478

Firmware Version: 51.0AB51

User Capacity:    2,000,398,934,016 bytes

 

Disk /dev/sde: 2000.3 GB, 2000398934016 bytes

255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors

Units = sectors of 1 * 512 = 512 bytes

Disk identifier: 0x00000000

 

 

I am on the console this time 'round. I know reads take a long time but this is reading at 3.1 MB/s according to the console. When I was clearing via telnet, a number never came up and again was very slow to read. I know that another previous preclear via telnet with my ST drive was reading around 28 MB/s.

 

 

So is this a direct issue with the drive and at least I am getting a read speed running it on console? At this rate I think it may take weeks to finish.

Is there a way to check drive speeds prior to preclear?

Should I start this preclear over with different parameters?

 

This is a brand new drive. I am grateful that these tests are helpful in weeding out bad drives and I appreciate that.

 

However, I will be pis*ed if this drive is bad. I remember a couple of procedures when all else fails with some drives, like up-ing the voltage, strategically dropping them, even placing them in the freezer. I guess that amounts to desperation. I shall check my wiring and move things about. I thing I will also try to change the sata cable over to another port to see if there is issue with the controller.

 

Any help and direction or experience with these issues are greatly appreciated.

 

Best,

Camel

 

By the way, Is there a correct procedure for killing the preclear process midstream? I don't think I will let this preclear continue reading @ 2.7MB/s. All I know is to shutdown from the menu and if I cannot access the UNmenu then I have to kill the power which I hate to do. I guess installing screens would be a good thing...

 

 

 

Link to comment

Archived

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

×
×
  • Create New...