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.

[SOLVED] Very slow Pre-Clear Read speeds?

Featured Replies

  • Author

I started a new telnet session and screen -r 27289 and it worked, yay!

 

Thanks for your help. I just need a little more patience hopefully!

 

================================================================== 1.13
=                unRAID server Pre-Clear disk /dev/sdi
=               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: 88% complete.
(  1,763,500,032,000  of  2,000,398,934,016  bytes read ) 78.0 MB/s
Disk Temperature: 41C, Elapsed Time:  19:38:09

 

 

No worries just remember when your done with a screen session type exit to close that session or your end up with loads of open sessions :)

and it seems to be chugging along at a nice (normal) pace!

  • Author

Give me strength.

 

Logged in this morning:

 

root@Server:~# screen -ls
There are screens on:
        21603.pts-0.Server      (Detached)
        27289.pts-0.Server      (Detached)
        27271.pts-0.Server      (Detached)
3 Sockets in /root/.screen.

root@Server:~# screen -r 27289
= Post-Read in progress: 88% complete.
(  1,761,854,976,000  of  2,000,398,934,016  bytes read ) 78.1 MB/s
Disk Temperature: 41C, Elapsed Time:  19:37:27







================================================================== 1.13
=                unRAID server Pre-Clear disk /dev/sdi
=               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: 88% complete.
(  1,763,500,032,000  of  2,000,398,934,016  bytes read ) 78.0 MB/s
Disk Temperature: 41C, Elapsed Time:  19:38:09
root@Server:/boot# screen -r 27289
There is a screen on:
        27289.pts-0.Server      (Attached)
There is no screen to be resumed matching 27289.
root@Server:/boot# screen -r 27289
There is a screen on:
        27289.pts-0.Server      (Attached)
There is no screen to be resumed matching 27289.
root@Server:/boot#

 

Looks exactly the same as this time yesterday, please tell me I haven't got to do this again?

 

Adam :(

if it hasn't moved then yep.

 

i suspect you are doing 'screen' incorrectly and terminating the pre-clear. Posting a syslog might help determine if another error caused it.

 

first, kill all screen sessions using instructions in the wiki.

 

- start telnet, login to server root/password.

- type screen

- start pre-clear for drive

- CTRL-A then CTRL-D.

 

you will then be returned to the console where you can type exit to log out.

 

to check status again, login using telnet, type screen -r

 

 

  • Author

Well I couldn't wait any longer so started rebuilding the array a couple of hours ago with the disk. Hopefully it won't come back to bite me.

 

Thanks for your help though.

 

Adam :(

  • 1 month later...
  • Author

Hi,

 

Sorry to drag this thread up again.

 

My friend has has asked me to build him an unRaid server on an HP ProLiant Gen8 (yes he really has no one else to ask). I am preclearing the first disk and was wondering if you can have more than one disk being cleared at the same time or whether it just takes longer?

 

He has 4 WD Green 2Tb disks.

 

Thanks,

 

Adam :)

You can check out pre-clearing with screen

 

  • Author

Marvellous, thanks.

  • Author

I set all 4 disks preclearing but am having trouble switching between screens.

 

root@Tower:~# screen -ls
There are screens on:
        20184.pts-0.Tower       (Attached)
        22894.pts-0.Tower       (Detached)
        27136.pts-0.Tower       (Detached)
        582.pts-0.Tower (Detached)
        19628.pts-0.Tower       (Detached)
        6847.pts-0.Tower        (Detached)
6 Sockets in /root/.screen.

 

I get this error if I try to 'screen -r ####'

 

Cannot find terminfo entry for 'vt100'

 

Any ideas?

 

Thanks,

 

Adam :)

  • Author

Thanks.

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.