Preclear plugin

gfjardim

By gfjardim
in Plugin Support

Recommended Posts

Recommended

Posted by Squid,

Due to various continual issues with this plugin, it has now been marked as being incompatible with Unraid versions 6.9.0+   It is highly advised to uninstall this plugin (and Statistics Sender if installed) and switch to the Unassigned Devices Preclear plugin (or Binhex-Preclear if you prefer a command line interface)  
Recommended by Squid
  • Thanks
  • Like

10 reactions

Go to this post
tr0910 Community Regular

tr0910

Posted
Posted

Yep, figured that already. Could you start a Varify All the Disk and tell if it failed again?

 

I may have already done that.  Not sure if this is what you mean?? 

 

2 days ago I set all 3 disks to do a complete preclear again.

 

The disk that did the full preclear initially did another full preclear including a post read verify as JoeL's script would have done.

 

Disk 2 replicated the previous preclear as follows

 

############################################################################################################################
#                                                                                                                          #
#                                        unRAID Server Pre-Clear of disk /dev/sdp                                          #
#                                       Cycle 1 of 1, partition start on sector 64.                                        #
#                                                                                                                          #
#                                                                                                                          #
#   Step 1 of 5 - Pre-read verification:                                                    [6:42:18 @ 82 MB/s] SUCCESS    #
#   Step 2 of 5 - Zeroing the disk:                                                         [6:33:30 @ 84 MB/s] SUCCESS    #
#   Step 3 of 5 - Writing unRAID's Preclear signature:                                                          SUCCESS    #
#   Step 4 of 5 - Verifying unRAID's Preclear signature:                                                        SUCCESS    #
#   Step 5 of 5 - Post-Read verification:                                                      [0:00:00 @ MB/s] SUCCESS    #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
############################################################################################################################
#                                Cycle elapsed time: 13:15:57 | Total elapsed time: 13:16:00                               #
############################################################################################################################


############################################################################################################################
#                                                                                                                          #
#                                                   S.M.A.R.T. Status                                                      #
#                                                                                                                          #
#                                                                                                                          #
#   ATTRIBUTE                      INITIAL    CYCLE 1    STATUS                                                            #
#   5-Reallocated_Sector_Ct        0          0          -                                                                 #
#   9-Power_On_Hours               11432      11445      Up 13                                                             #
#   194-Temperature_Celsius        30         34         Up 4                                                              #
#   196-Reallocated_Event_Count    0          0          -                                                                 #
#   197-Current_Pending_Sector     0          0          -                                                                 #
#   198-Offline_Uncorrectable      0          0          -                                                                 #
#   199-UDMA_CRC_Error_Count       0          0          -                                                                 #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
############################################################################################################################
#   SMART overall-health self-assessment test result: PASSED                                                               #
############################################################################################################################


--> ATTENTION: Please take a look into the SMART report above for drive health issues.

--> RESULT: Preclear finished succesfully.


root@Server1:/usr/local/emhttp#

 

The 3rd disk only confirmed that the disk was already precleared as follows.

 

############################################################################################################################
#                                                                                                                          #
#                                unRAID Server: verifying Preclear State of '/dev/sdq' .                                   #
#                                 Verifying disk '/dev/sdq' for unRAID's Preclear State.                                   #
#                                                                                                                          #
#                                                                                                                          #
#   Step 1 of 2 - Verifying unRAID's Preclear MBR:                                                              SUCCESS    #
#   Step 2 of 2 - Verifying if disk is zeroed:                                               5:04:49 @ 164 MB/s SUCCESS    #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#   ** Time elapsed: 5:04:49 | Current speed: 164 MB/s | Average speed: 164 MB/s                                           #
#                                                                                                                          #
############################################################################################################################
#                                               Total elapsed time: 5:05:02                                                #
############################################################################################################################

--> RESULT: SUCCESS! Disk /dev/sdq has been verified precleared!


root@Server1:/usr/local/emhttp#

 

Is this user error or an actual bug?  I would have expected 3 full preclears like this...

 

############################################################################################################################
#                                                                                                                          #
#                                        unRAID Server Pre-Clear of disk /dev/sdo                                          #
#                                       Cycle 1 of 1, partition start on sector 64.                                        #
#                                                                                                                          #
#                                                                                                                          #
#   Step 1 of 5 - Pre-read verification:                                                   [7:05:27 @ 117 MB/s] SUCCESS    #
#   Step 2 of 5 - Zeroing the disk:                                                        [6:58:00 @ 119 MB/s] SUCCESS    #
#   Step 3 of 5 - Writing unRAID's Preclear signature:                                                          SUCCESS    #
#   Step 4 of 5 - Verifying unRAID's Preclear signature:                                                        SUCCESS    #
#   Step 5 of 5 - Post-Read verification:                                                  [7:05:24 @ 117 MB/s] SUCCESS    #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
############################################################################################################################
#                                Cycle elapsed time: 21:08:57 | Total elapsed time: 21:08:57                               #
############################################################################################################################


############################################################################################################################
#                                                                                                                          #
#                                                   S.M.A.R.T. Status                                                      #
#                                                                                                                          #
#                                                                                                                          #
#   ATTRIBUTE                      INITIAL    CYCLE 1    STATUS                                                            #
#   5-Reallocated_Sector_Ct        0          0          -                                                                 #
#   9-Power_On_Hours               8525       8546       Up 21                                                             #
#   183-Runtime_Bad_Block          0          0          -                                                                 #
#   184-End-to-End_Error           0          0          -                                                                 #
#   187-Reported_Uncorrect         0          0          -                                                                 #
#   190-Airflow_Temperature_Cel    36         38         Up 2      ->Failed in Past<-                                      #
#   197-Current_Pending_Sector     0          0          -                                                                 #
#   198-Offline_Uncorrectable      0          0          -                                                                 #
#   199-UDMA_CRC_Error_Count       0          0          -                                                                 #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
############################################################################################################################
#   SMART overall-health self-assessment test result: PASSED                                                               #
############################################################################################################################


--> ATTENTION: Please take a look into the SMART report above for drive health issues.

--> RESULT: Preclear finished succesfully.


root@Server1:/usr/local/emhttp#

Link to comment
  • Replies 3.1k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

gfjardim
gfjardim

Hi guys, this is a simple plugin that allows users to clear their disks before add them to the array.   The main characteristics of this plugin are: Modularity: can be used standalon

Squid
Squid

Due to various continual issues with this plugin, it has now been marked as being incompatible with Unraid versions 6.9.0+   It is highly advised to uninstall this plugin (and Statistics Sen

CHBMB
CHBMB

I think Thanks should be directed at all those members that have been dealing with the mess the last few months. @dlandon and @Squid have been working behind the scenes to try and clean up, and o

Posted Images

gfjardim Rising Star

gfjardim

Posted
  • Author
Posted

Yep, figured that already. Could you start a Varify All the Disk and tell if it failed again?

 

I may have already done that.  Not sure if this is what you mean?? 

 

2 days ago I set all 3 disks to do a complete preclear again.

 

The disk that did the full preclear initially did another full preclear including a post read verify as JoeL's script would have done.

 

Disk 2 replicated the previous preclear as follows

 

 

Could you please look into your syslog for Out Of Memory occurrences?

Link to comment
tr0910 Community Regular

tr0910

Posted
Posted

Could you please look into your syslog for Out Of Memory occurrences?

 

Diagnostics attached.  Lots of sense.key nonsense.  Unsure what matters in this syslog.  Perhaps some hardware errors will be noticed by someone else. (@turl or @robj)

 

(FYI this is a Xeon 1220 Sandybridge on a Supermicro X9SCM with 20GB Ram and the affected devices are all connected to an IBM1015 via a Norco 4224 chassis.)

server1-diagnostics-20161031-1101.zip

Link to comment
gfjardim Rising Star

gfjardim

Posted
  • Author
Posted

Could you please look into your syslog for Out Of Memory occurrences?

 

Diagnostics attached.  Lots of sense.key nonsense.  Unsure what matters in this syslog.  Perhaps some hardware errors will be noticed by someone else. (@turl or @robj)

 

(FYI this is a Xeon 1220 Sandybridge on a Supermicro X9SCM with 20GB Ram and the affected devices are all connected to an IBM1015 via a Norco 4224 chassis.)

 

I've updated the script to output some debug info. Could you please update and run another instance of Clear on /dev/sdp?

Link to comment
tr0910 Community Regular

tr0910

Posted
Posted

Updated, but didn't reboot.

 

Running now, both on sdp and sdq.  (since both gave unexpected results)

 

Note: sdn was also running a preclear on a failing disk, so that could be causing issues.  I've aborted it and restarted as well.  So we should get results from it too.

 

Finished post read on sdq, and sdp is midway through the post read, so I declare a success.  Here is the preclear log:

 

preclear_disk_sdp: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdp
preclear_disk_sdp: Pre-Read: dd if=/dev/sdp of=/dev/null bs=2097152  iflag=direct
preclear_disk_sdq: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdq
preclear_disk_sdq: Pre-Read: dd if=/dev/sdq of=/dev/null bs=2097152  iflag=direct
preclear_disk_sdn: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdn
preclear_disk_sdn: Pre-Read: dd if=/dev/sdn of=/dev/null bs=2097152  iflag=direct
preclear_disk_sdq: Zeroing: dd if=/dev/zero of=/dev/sdq bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct
preclear_disk_sdq: Zeroing: dd pid [5201]
preclear_disk_sdp: Zeroing: dd if=/dev/zero of=/dev/sdp bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct
preclear_disk_sdp: Zeroing: dd pid [25915]
preclear_disk_sdq: Post-Read: dd if=/dev/sdq bs=512 count=4096 skip=1 iflag=direct
preclear_disk_sdq: Post-Read: dd pid [24376]
preclear_disk_sdq: Post-Read: dd if=/dev/sdq bs=2097152  skip=1 iflag=direct 2>/tmp/.preclear/sdq/dd_output | cmp - /dev/zero &>/tmp/.preclear/sdq/cmp_out 
preclear_disk_sdq: Post-Read: dd pid [24412]
preclear_disk_sdp: Post-Read: dd if=/dev/sdp bs=512 count=4096 skip=1 iflag=direct
preclear_disk_sdp: Post-Read: dd pid [11119]
preclear_disk_sdp: Post-Read: dd if=/dev/sdp bs=2097152  skip=1 iflag=direct 2>/tmp/.preclear/sdp/dd_output | cmp - /dev/zero &>/tmp/.preclear/sdp/cmp_out 
preclear_disk_sdp: Post-Read: dd pid [11224]
preclear_disk_sdq:

Link to comment
Spritzup Contributor

Spritzup

Posted
Posted

Did you try reading the first post in the thread?

 

/facepalm... I actually did read the first post (and a few pages afterwards), but apparently lack of sleep is starting to catch up to me.

 

Apologies for wasting peoples time, and thank you for making me go back and reread the post again.

 

~Spritz

Link to comment
optiman Collaborator

optiman

Posted
Posted

Hello guys,

 

Just got a new HGST 6tb drive that I'm about to Preclear.  I have version 2016.10.31.  I'm current with Unraid too, 6.2.3.

 

1.  I select Start Preclear, I only see one Script option now, says gfjardim - 0.8 beta.  Is that the correct and latest and  greatest Script?

 

2.  I only have two options, Skip PreRead and Skip Post-Read.  I leave both off (NO), assuming this is the best.  I thought somebody posted that we should see a Check box that says Fast Option, or  Fast Post??  Or with the recent script updates, we don't need that option anymore because the newly updated script is faster without any of that?

 

3.  Not sure if this is related to my hardware or not, but I wanted to report a issue with the Main and Dashboard screens where the PreClear status is not displayed.    Let me explain how this happens.  I add a new hard drive to my unraid server via external SATA cable.  If I reboot now, the Main screen will show a Unassigned section, listing this new drive.  While running PreClear, the status will show on the Main screen.  It will also show progress on the Dashboard screen.  Last, it for sure will show status on the Tools --> PreClear screen.  However, if I attach the new hard drive and Do Not Reboot, the Main and Dashboard screens will never show the PreClear status, and there is no Unassigned section on the Main screen.  I can get the status only on the Tools --> PreClear screen.  I'm not sure if that is a PreClear plugin issue, or Webgui issue but it would be cool if I can avoid a reboot to get the Main screen to show the Unassigned section and PreClear status.

 

4.  Has anyone had any issues running a PreClear while a Parity Check was running?  I ask because today I'm running both for the very first time, and I'm praying no conflicts or errros as a result.

 

Thank you

 

Thank you

Link to comment
John_M Experienced

John_M

Posted
Posted

Hello guys,

 

Just got a new HGST 6tb drive that I'm about to Preclear.  I have version 2016.10.31.  I'm current with Unraid too, 6.2.3.

 

1. gfjardim's script is included with the plugin. If you have the latest version of the plugin you have the latest version of the script. If you want to use any other script you need to add it manually.

 

2. The fast post-read option only applies to bjp999's script.

 

3. You're trying to hot-plug disks, which isn't officially supported, but see here: https://lime-technology.com/forum/index.php?topic=53473.0

 

4. I left a parity build (P and Q) and two pre-clears running overnight. The parity completed without problems and the pre-clears are progressing well.

 

Link to comment
optiman Collaborator

optiman

Posted
Posted

Hello guys,

 

Just got a new HGST 6tb drive that I'm about to Preclear.  I have version 2016.10.31.  I'm current with Unraid too, 6.2.3.

 

1.  I select Start Preclear, I only see one Script option now, says gfjardim - 0.8 beta.  Is that the correct and latest and  greatest Script?

 

2.  I only have two options, Skip PreRead and Skip Post-Read.  I leave both off (NO), assuming this is the best.  I thought somebody posted that we should see a Check box that says Fast Option, or  Fast Post??  Or with the recent script updates, we don't need that option anymore because the newly updated script is faster without any of that?

 

3.  Not sure if this is related to my hardware or not, but I wanted to report a issue with the Main and Dashboard screens where the PreClear status is not displayed.    Let me explain how this happens.  I add a new hard drive to my unraid server via external SATA cable.  If I reboot now, the Main screen will show a Unassigned section, listing this new drive.  While running PreClear, the status will show on the Main screen.  It will also show progress on the Dashboard screen.  Last, it for sure will show status on the Tools --> PreClear screen.  However, if I attach the new hard drive and Do Not Reboot, the Main and Dashboard screens will never show the PreClear status, and there is no Unassigned section on the Main screen.  I can get the status only on the Tools --> PreClear screen.  I'm not sure if that is a PreClear plugin issue, or Webgui issue but it would be cool if I can avoid a reboot to get the Main screen to show the Unassigned section and PreClear status.

 

4.  Has anyone had any issues running a PreClear while a Parity Check was running?  I ask because today I'm running both for the very first time, and I'm praying no conflicts or errros as a result.

 

Thank you

 

Thank you

 

Preclear is for sure faster.  I have run Preclear on 5 new HGST 6TB drives.  All of them have taken 47 - 51 hours for one full pass.  With the new version and the same hard drive model, now I get 35 hours for one pass.

 

Here is the info:

 

Step 1 of 5 - Pre-read verification:                                                  [15:29:00 @ 107 MB/s] SUCCESS    #

#  Step 2 of 5 - Zeroing the disk:                                                      [11:32:03 @ 144 MB/s] SUCCESS    #

#  Step 3 of 5 - Writing unRAID's Preclear signature:                                                          SUCCESS    #

#  Step 4 of 5 - Verifying unRAID's Preclear signature:                                                        SUCCESS    #

#  Step 5 of 5 - Post-Read verification:                                                  [7:53:53 @ 138 MB/s] SUCCESS    #

#                                                                                                                          #

#                                Cycle elapsed time: 34:55:00 | Total elapsed time: 34:55:00                              #

 

 

Link to comment
cyberstyx Rookie

cyberstyx

Posted
Posted

Hey all,

 

I have added an older 2TB disk for PreClearing (2016.09.26b), and although it started at nice speeds now at step 5 it's really crawling - 61 hours at current step :S

 

############################################################################################################################
#                                                                                                                          #
#                                        unRAID Server Pre-Clear of disk /dev/sdg                                          #
#                                       Cycle 1 of 1, partition start on sector 64.                                        #
#                                                                                                                          #
#                                                                                                                          #
#   Step 1 of 5 - Pre-read verification:                                                    [9:58:19 @ 55 MB/s] SUCCESS    #
#   Step 2 of 5 - Zeroing the disk:                                                         [7:34:05 @ 73 MB/s] SUCCESS    #
#   Step 3 of 5 - Writing unRAID's Preclear signature:                                                          SUCCESS    #
#   Step 4 of 5 - Verifying unRAID's Preclear signature:                                                        SUCCESS    #
#   Step 5 of 5 - Post-Read in progress:                                                                     (53% Done)    #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#   ** Time elapsed: 61:24:10 | Current speed: 30.2 MB/s | Average speed: 4 MB/s                                           #
#                                                                                                                          #
############################################################################################################################
#                                Cycle elapsed time: 79:00:36 | Total elapsed time: 79:00:37                               #
############################################################################################################################


############################################################################################################################
#                                                                                                                          #
#                                                   S.M.A.R.T. Status                                                      #
#                                                                                                                          #
#                                                                                                                          #
#   ATTRIBUTE                      INITIAL    STATUS                                                                       #
#   5-Reallocated_Sector_Ct        0          -                                                                            #
#   9-Power_On_Hours               41989      -                                                                            #
#   194-Temperature_Celsius        30         -                                                                            #
#   196-Reallocated_Event_Count    0          -                                                                            #
#   197-Current_Pending_Sector     6          -                                                                            #
#   198-Offline_Uncorrectable      0          -                                                                            #
#   199-UDMA_CRC_Error_Count       0          -                                                                            #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
############################################################################################################################
#   SMART overall-health self-assessment test result: PASSED                                                               #
############################################################################################################################

 

And I have a new WD RED 6TB waiting to joing the Array.

 

Is this normal?

 

Can I / should I stop the process and if so will unRaid (6.2) allow me to add it in the array?

 

There was a "197-Current_Pending_Sector    6" which Googled to "zeroing the disk fixes it", and SMART overall status is passed.

 

Thank you, Christos.

Link to comment
RobJ Mentor

RobJ

Posted
Posted

I have added an older 2TB disk for PreClearing (2016.09.26b), and although it started at nice speeds now at step 5 it's really crawling - 61 hours at current step :S

...

#  197-Current_Pending_Sector    6          -                                                                            #

...

There was a "197-Current_Pending_Sector    6" which Googled to "zeroing the disk fixes it", and SMART overall status is passed.

The fact that the drive had 6 and is slow on the post-read may mean it's starting to fail.  Zeroing it *may* have fixed those 6, but if the drive is going bad, there may be more now.  You can let it complete or stop it, but I would do at least one more Preclear on it, preferably 2 more.  You want perfect Preclears, running at normal speed, before you can trust it.

Link to comment
cyberstyx Rookie

cyberstyx

Posted
Posted

I have added an older 2TB disk for PreClearing (2016.09.26b), and although it started at nice speeds now at step 5 it's really crawling - 61 hours at current step :S

...

#  197-Current_Pending_Sector    6          -                                                                            #

...

There was a "197-Current_Pending_Sector    6" which Googled to "zeroing the disk fixes it", and SMART overall status is passed.

The fact that the drive had 6 and is slow on the post-read may mean it's starting to fail.  Zeroing it *may* have fixed those 6, but if the drive is going bad, there may be more now.  You can let it complete or stop it, but I would do at least one more Preclear on it, preferably 2 more.  You want perfect Preclears, running at normal speed, before you can trust it.

 

From the web GUI I checked Tools > Preclear > Log option, and the pop-up window gets regularly spammed with these

 

Nov 8 18:45:54 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x1000000 SErr 0x0 action 0x0
Nov 8 18:45:54 Tower kernel: ata17.00: irq_stat 0x40000008
Nov 8 18:45:54 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED
Nov 8 18:45:54 Tower kernel: ata17.00: cmd 60/08:c0:70:00:44/00:00:7c:00:00/40 tag 24 ncq 4096 in
Nov 8 18:45:54 Tower kernel: res 41/40:00:70:00:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F>
Nov 8 18:45:54 Tower kernel: ata17.00: status: { DRDY ERR }
Nov 8 18:45:54 Tower kernel: ata17.00: error: { UNC }
Nov 8 18:45:54 Tower kernel: ata17.00: configured for UDMA/133
Nov 8 18:45:54 Tower kernel: sd 17:0:0:0: [sdg] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Nov 8 18:45:54 Tower kernel: sd 17:0:0:0: [sdg] tag#24 Sense Key : 0x3 [current] [descriptor] 
Nov 8 18:45:54 Tower kernel: sd 17:0:0:0: [sdg] tag#24 ASC=0x11 ASCQ=0x4 
Nov 8 18:45:54 Tower kernel: sd 17:0:0:0: [sdg] tag#24 CDB: opcode=0x28 28 00 7c 44 00 70 00 00 08 00
Nov 8 18:45:54 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084831344
Nov 8 18:45:54 Tower kernel: Buffer I/O error on dev sdg, logical block 260603918, async page read
Nov 8 18:45:54 Tower kernel: ata17: EH complete
Nov 8 18:45:57 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x8 SErr 0x0 action 0x0
Nov 8 18:45:57 Tower kernel: ata17.00: irq_stat 0x40000008
Nov 8 18:45:57 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED
Nov 8 18:45:57 Tower kernel: ata17.00: cmd 60/08:18:70:00:44/00:00:7c:00:00/40 tag 3 ncq 4096 in
Nov 8 18:45:57 Tower kernel: res 41/40:00:70:00:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F>
Nov 8 18:45:57 Tower kernel: ata17.00: status: { DRDY ERR }
Nov 8 18:45:57 Tower kernel: ata17.00: error: { UNC }
Nov 8 18:45:57 Tower kernel: ata17.00: configured for UDMA/133
Nov 8 18:45:57 Tower kernel: sd 17:0:0:0: [sdg] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Nov 8 18:45:57 Tower kernel: sd 17:0:0:0: [sdg] tag#3 Sense Key : 0x3 [current] [descriptor] 
Nov 8 18:45:57 Tower kernel: sd 17:0:0:0: [sdg] tag#3 ASC=0x11 ASCQ=0x4 
Nov 8 18:45:57 Tower kernel: sd 17:0:0:0: [sdg] tag#3 CDB: opcode=0x28 28 00 7c 44 00 70 00 00 08 00
Nov 8 18:45:57 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084831344
Nov 8 18:45:57 Tower kernel: Buffer I/O error on dev sdg, logical block 260603918, async page read
Nov 8 18:45:57 Tower kernel: ata17: EH complete
Nov 8 18:46:00 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x0
Nov 8 18:46:00 Tower kernel: ata17.00: irq_stat 0x40000008
Nov 8 18:46:00 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED
Nov 8 18:46:00 Tower kernel: ata17.00: cmd 60/08:88:20:04:44/00:00:7c:00:00/40 tag 17 ncq 4096 in
Nov 8 18:46:00 Tower kernel: res 41/40:00:20:04:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F>
Nov 8 18:46:00 Tower kernel: ata17.00: status: { DRDY ERR }
Nov 8 18:46:00 Tower kernel: ata17.00: error: { UNC }
Nov 8 18:46:00 Tower kernel: ata17.00: configured for UDMA/133
Nov 8 18:46:00 Tower kernel: sd 17:0:0:0: [sdg] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Nov 8 18:46:00 Tower kernel: sd 17:0:0:0: [sdg] tag#17 Sense Key : 0x3 [current] [descriptor] 
Nov 8 18:46:00 Tower kernel: sd 17:0:0:0: [sdg] tag#17 ASC=0x11 ASCQ=0x4 
Nov 8 18:46:00 Tower kernel: sd 17:0:0:0: [sdg] tag#17 CDB: opcode=0x28 28 00 7c 44 04 20 00 00 08 00
Nov 8 18:46:00 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084832288
Nov 8 18:46:00 Tower kernel: Buffer I/O error on dev sdg, logical block 260604036, async page read
Nov 8 18:46:00 Tower kernel: ata17: EH complete
Nov 8 18:46:03 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x0
Nov 8 18:46:03 Tower kernel: ata17.00: irq_stat 0x40000008
Nov 8 18:46:03 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED
Nov 8 18:46:03 Tower kernel: ata17.00: cmd 60/08:88:a8:08:44/00:00:7c:00:00/40 tag 17 ncq 4096 in
Nov 8 18:46:03 Tower kernel: res 41/40:00:a8:08:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F>
Nov 8 18:46:03 Tower kernel: ata17.00: status: { DRDY ERR }
Nov 8 18:46:03 Tower kernel: ata17.00: error: { UNC }
Nov 8 18:46:03 Tower kernel: ata17.00: configured for UDMA/133
Nov 8 18:46:03 Tower kernel: sd 17:0:0:0: [sdg] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Nov 8 18:46:03 Tower kernel: sd 17:0:0:0: [sdg] tag#17 Sense Key : 0x3 [current] [descriptor] 
Nov 8 18:46:03 Tower kernel: sd 17:0:0:0: [sdg] tag#17 ASC=0x11 ASCQ=0x4 
Nov 8 18:46:03 Tower kernel: sd 17:0:0:0: [sdg] tag#17 CDB: opcode=0x28 28 00 7c 44 08 a8 00 00 08 00
Nov 8 18:46:03 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084833448
Nov 8 18:46:03 Tower kernel: Buffer I/O error on dev sdg, logical block 260604181, async page read
Nov 8 18:46:03 Tower kernel: ata17: EH complete
Nov 8 18:46:05 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x0
Nov 8 18:46:05 Tower kernel: ata17.00: irq_stat 0x40000008
Nov 8 18:46:05 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED
Nov 8 18:46:05 Tower kernel: ata17.00: cmd 60/08:b0:a8:08:44/00:00:7c:00:00/40 tag 22 ncq 4096 in
Nov 8 18:46:05 Tower kernel: res 41/40:00:a8:08:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F>
Nov 8 18:46:05 Tower kernel: ata17.00: status: { DRDY ERR }
Nov 8 18:46:05 Tower kernel: ata17.00: error: { UNC }
Nov 8 18:46:05 Tower kernel: ata17.00: configured for UDMA/133
Nov 8 18:46:05 Tower kernel: sd 17:0:0:0: [sdg] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Nov 8 18:46:05 Tower kernel: sd 17:0:0:0: [sdg] tag#22 Sense Key : 0x3 [current] [descriptor] 
Nov 8 18:46:05 Tower kernel: sd 17:0:0:0: [sdg] tag#22 ASC=0x11 ASCQ=0x4 
Nov 8 18:46:05 Tower kernel: sd 17:0:0:0: [sdg] tag#22 CDB: opcode=0x28 28 00 7c 44 08 a8 00 00 08 00
Nov 8 18:46:05 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084833448
Nov 8 18:46:05 Tower kernel: Buffer I/O error on dev sdg, logical block 260604181, async page read
Nov 8 18:46:05 Tower kernel: ata17: EH complete
Nov 8 18:46:09 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x2000000 SErr 0x0 action 0x0
Nov 8 18:46:09 Tower kernel: ata17.00: irq_stat 0x40000008
Nov 8 18:46:09 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED
Nov 8 18:46:09 Tower kernel: ata17.00: cmd 60/08:c8:88:29:44/00:00:7c:00:00/40 tag 25 ncq 4096 in
Nov 8 18:46:09 Tower kernel: res 41/40:00:88:29:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F>
Nov 8 18:46:09 Tower kernel: ata17.00: status: { DRDY ERR }
Nov 8 18:46:09 Tower kernel: ata17.00: error: { UNC }
Nov 8 18:46:09 Tower kernel: ata17.00: configured for UDMA/133
Nov 8 18:46:09 Tower kernel: sd 17:0:0:0: [sdg] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Nov 8 18:46:09 Tower kernel: sd 17:0:0:0: [sdg] tag#25 Sense Key : 0x3 [current] [descriptor] 
Nov 8 18:46:09 Tower kernel: sd 17:0:0:0: [sdg] tag#25 ASC=0x11 ASCQ=0x4 
Nov 8 18:46:09 Tower kernel: sd 17:0:0:0: [sdg] tag#25 CDB: opcode=0x28 28 00 7c 44 29 88 00 00 08 00
Nov 8 18:46:09 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084841864
Nov 8 18:46:09 Tower kernel: Buffer I/O error on dev sdg, logical block 260605233, async page read
Nov 8 18:46:09 Tower kernel: ata17: EH complete
Nov 8 18:46:11 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x0
Nov 8 18:46:11 Tower kernel: ata17.00: irq_stat 0x40000008
Nov 8 18:46:11 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED
Nov 8 18:46:11 Tower kernel: ata17.00: cmd 60/08:30:88:29:44/00:00:7c:00:00/40 tag 6 ncq 4096 in
Nov 8 18:46:11 Tower kernel: res 41/40:00:88:29:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F>
Nov 8 18:46:11 Tower kernel: ata17.00: status: { DRDY ERR }
Nov 8 18:46:11 Tower kernel: ata17.00: error: { UNC }
Nov 8 18:46:12 Tower kernel: ata17.00: configured for UDMA/133
Nov 8 18:46:12 Tower kernel: sd 17:0:0:0: [sdg] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Nov 8 18:46:12 Tower kernel: sd 17:0:0:0: [sdg] tag#6 Sense Key : 0x3 [current] [descriptor] 
Nov 8 18:46:12 Tower kernel: sd 17:0:0:0: [sdg] tag#6 ASC=0x11 ASCQ=0x4 
Nov 8 18:46:12 Tower kernel: sd 17:0:0:0: [sdg] tag#6 CDB: opcode=0x28 28 00 7c 44 29 88 00 00 08 00
Nov 8 18:46:12 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084841864
Nov 8 18:46:12 Tower kernel: Buffer I/O error on dev sdg, logical block 260605233, async page read
Nov 8 18:46:12 Tower kernel: ata17: EH complete

 

which don't look promising...

Link to comment
Fireball3 Community Regular

Fireball3

Posted
Posted

Just a trivia, guys.

 

Tested both bjp999 and my script on a 2TB disk:

 

bjp999:  21h34m49s

gfjardim: 19h06m04s

 

Almost two and a half hours saved is a very good mark, IMO.

Saving some time is always welcome!

How is it possible?

 

Is this script also available for commandline use?

I don't like to preclear on my main server and have a spare machine not connected to the network doing it.

Link to comment
gfjardim Rising Star

gfjardim

Posted
  • Author
Posted

Just a trivia, guys.

 

Tested both bjp999 and my script on a 2TB disk:

 

bjp999:  21h34m49s

gfjardim: 19h06m04s

 

Almost two and a half hours saved is a very good mark, IMO.

Saving some time is always welcome!

How is it possible?

 

Is this script also available for commandline use?

I don't like to preclear on my main server and have a spare machine not connected to the network doing it.

Joe L. script read the disk in chunks, sum them and check for a zero result. In fact, it read the disk twice, once for speed calculation and other for comparison, relying on cache to keep the first read on RAM to speed up the process. My script read all the disk at once, and compare it against the pseudo block device /dev/zero. Using direct read, it also skip the RAM cache entirely so it has a smaller memory footprint.

 

It's not ready for command line because it doesn't have help, but if you want, you can always dig up the code for available options.

 

Link to comment
Fireball3 Community Regular

Fireball3

Posted
Posted

Thanks for the explanation.

 

Pro:

significant speed-up

 

Con:

The preclear is kind of a stress test.

I understand this improvement removes some stress/load (the multiple read) in favor of speed.

 

What would be the equivalent commandline options for "-A -f" in your script.

Where can I download the script alone?

Link to comment
gfjardim Rising Star

gfjardim

Posted
  • Author
Posted

Not a con, since the second read was done using RAM cache and didn't stress the disk.

 

If I'm not mistaken, -A switch is used to change the SMART device type, and it's not implemented in my script. I don't remember what -f is used for.

 

Enviado de meu SM-G930F usando Tapatalk

 

 

Link to comment
Fireball3 Community Regular

Fireball3

Posted
Posted
Not a con, since the second read was done using RAM cache and didn't stress the disk.

 

OK, if you say so...I'm not as far in the subject as you.

 

-A was to align 4k partitions if I remember correctly

 

-f was the "fast"-switch in the bjp script

 

Would appreciate if you enhance the script for commandline usage.

Link to comment
Fireball3 Community Regular

Fireball3

Posted
Posted

Aren't both of those options redundant? I would hope that 4k alignment is the default and surely gfjardim's script doesn't need a fast switch, since it's faster by design.

You're probably right with the -f switch.

With regard to the -A: gfjadrim will have to tell us, I can't figure it out in the code (in a reasonable time frame)

These are the options I found in the code:

-n|--notify
-s|--skip-preread
-S|--skip-postread
-r|--read-size
-w|--write-size
---read-blocks
-t|--test
-d|--no-stress
-l|--list
-c|--cycles
-u|--signature
-p|--verify
-j|--no-prompt
-v|--version
-o|--preclear-only
-m|--format-html

 

Either alignment of 4k partitions is done by default, or it is not foreseen in this script.

 

Will have to test if the script output is usable on console...

Link to comment
  • Squid featured, unfeatured and pinned this topic
  • Squid unpinned this topic

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Go to topic listing