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 Running VERY Slow (11 MB/s)?

Featured Replies

Been trying to preclear two drives.  The first is a 750 GB WD7500AKS, the second a 2 TB Seagate ST2000DL003.  The WD has successfully precleared 3 times at a rate of ~90 MB/s.  The Seagate operation was terminated twice somehow mid process.  It had been humming along at a similar rate.  The third time I ran preclear on the Seagate it is running at 11 MB/s.  Been running for 21+ hours and it's only 38% through the first pre-read. 

 

I don't know how the first two preclear processes were terminated (something about a remote host?), but it appears they've caused this slowdown.  Any advice on how to approach this?  I've not had any problem with this drive to date.  Is there a proper way to get the drive back on track speed wise?

Been trying to preclear two drives.  The first is a 750 GB WD7500AKS, the second a 2 TB Seagate ST2000DL003.  The WD has successfully precleared 3 times at a rate of ~90 MB/s.  The Seagate operation was terminated twice somehow mid process.  It had been humming along at a similar rate.  The third time I ran preclear on the Seagate it is running at 11 MB/s.  Been running for 21+ hours and it's only 38% through the first pre-read. 

 

I don't know how the first two preclear processes were terminated (something about a remote host?), but it appears they've caused this slowdown.  Any advice on how to approach this?  I've not had any problem with this drive to date.  Is there a proper way to get the drive back on track speed wise?

My car makes a funny noise... It is a Toyota.  My old car did not make any noise... What do you think might be the cause?  It used to run OK and I've taken it on several trips.

 

I've given you almost as much information as you've given me.

 

Usually a slowdown is accompanied by clues written to the system log.  Have you considered looking there?

 

The pre-clear will terminate if run via telnet and the telnet session terminates.  It is why the use of either the system console or the "screen" virtual screen manager is suggested.

 

Look here: http://lime-technology.com/forum/index.php?topic=9880.0

 

Joe L.

  • Author

Sorry for the lack of information, I'm still new to this.  Syslog is attached.  I was running preclear via Mac OS Terminal > telnet & screen when the process was terminated both times.  Neither time did I exit telnet or terminal.

 

The Syslog shows one of the preclear processes on the Seagate was actually successful, interestingly.  I don't see any errors or minor issues that stand out, but I'm still a newb and trying to learn.  There is only one instance of preclear on the Seagate listed, however, I started the Seagate & the WD simultaneously each time.

syslog-2012-03-06.txt.zip

 

The seagate seemed to have been pre-cleared just fine.  I see no evidence of any processes being killed.

 

Do you have a pre-clear running now?  Is it possible you have two running on the same disk at the same time?

(That would slow it to a crawl)

 

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: ========================================================================1.13

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: == invoked as: ./preclear_disk.sh -A /dev/sdd

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: ==  WDC WD7500AAKS-00RBA0    WD-WCAPT0072817

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: == Disk /dev/sdd has been successfully precleared

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: == with a starting sector of 64

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: == Ran 1 cycle

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: ==

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: == Using :Read block size = 8225280 Bytes

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: == Last Cycle's Pre Read Time  : 2:46:52 (74 MB/s)

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: == Last Cycle's Zeroing time  : 2:41:25 (77 MB/s)

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: == Last Cycle's Post Read Time : 5:32:39 (37 MB/s)

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: == Last Cycle's Total Time    : 11:02:05

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: ==

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: == Total Elapsed Time 11:02:05

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: ==

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: == Disk Start Temperature: 35C

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: ==

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: == Current Disk Temperature: 35C,

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: ==

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: ============================================================================

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: ** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd

Mar  4 02:10:43 Tower preclear_disk-diff[30574]:                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

Mar  4 02:10:43 Tower preclear_disk-diff[30574]:          Start_Stop_Count =    17      17            0        near_thresh 83787

Mar  4 02:10:43 Tower preclear_disk-diff[30574]:          Seek_Error_Rate =  100    200          51        ok          0

Mar  4 02:10:43 Tower preclear_disk-diff[30574]:  No SMART attributes are FAILING_NOW

Mar  4 02:10:43 Tower preclear_disk-diff[30574]:

Mar  4 02:10:43 Tower preclear_disk-diff[30574]:  0 sectors were pending re-allocation before the start of the preclear.

Mar  4 02:10:43 Tower preclear_disk-diff[30574]:  0 sectors were pending re-allocation after pre-read in cycle 1 of 1.

Mar  4 02:10:43 Tower preclear_disk-diff[30574]:  0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.

Mar  4 02:10:43 Tower preclear_disk-diff[30574]:  0 sectors are pending re-allocation at the end of the preclear,

Mar  4 02:10:43 Tower preclear_disk-diff[30574]:    the number of sectors pending re-allocation did not change.

Mar  4 02:10:43 Tower preclear_disk-diff[30574]:  0 sectors had been re-allocated before the start of the preclear.

Mar  4 02:10:43 Tower preclear_disk-diff[30574]:  0 sectors are re-allocated at the end of the preclear,

Mar  4 02:10:43 Tower preclear_disk-diff[30574]:    the number of sectors re-allocated did not change.

Mar  4 02:10:43 Tower preclear_disk-diff[30574]: ============================================================================

 

 

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: ========================================================================1.13

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: == invoked as: ./preclear_disk.sh -A /dev/sde

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: ==  ST2000DL003-9VT166    5YD557WM

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: == Disk /dev/sde has been successfully precleared

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: == with a starting sector of 64

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: == Ran 1 cycle

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: ==

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: == Using :Read block size = 8225280 Bytes

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: == Last Cycle's Pre Read Time  : 5:48:40 (95 MB/s)

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: == Last Cycle's Zeroing time  : 5:10:44 (107 MB/s)

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: == Last Cycle's Post Read Time : 12:09:50 (45 MB/s)

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: == Last Cycle's Total Time    : 23:10:22

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: ==

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: == Total Elapsed Time 23:10:22

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: ==

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: == Disk Start Temperature: 28C

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: ==

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: == Current Disk Temperature: 30C,

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: ==

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: ============================================================================

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: ** Changed attributes in files: /tmp/smart_start_sde  /tmp/smart_finish_sde

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:      Raw_Read_Error_Rate =  111    118            6        ok          41892016

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:          Seek_Error_Rate =    61      60          30        ok          1430299

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:          Spin_Retry_Count =  100    100          97        near_thresh 0

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:          End-to-End_Error =  100    100          99        near_thresh 0

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:  Airflow_Temperature_Cel =    70      72          45        near_thresh 30

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:      Temperature_Celsius =    30      28            0        ok          30

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:    Hardware_ECC_Recovered =    36      22            0        ok          41892016

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:  No SMART attributes are FAILING_NOW

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:  0 sectors were pending re-allocation before the start of the preclear.

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:  0 sectors were pending re-allocation after pre-read in cycle 1 of 1.

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:  0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:  0 sectors are pending re-allocation at the end of the preclear,

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:    the number of sectors pending re-allocation did not change.

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:  0 sectors had been re-allocated before the start of the preclear.

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:  0 sectors are re-allocated at the end of the preclear,

Mar  4 14:17:41 Tower preclear_disk-diff[4044]:    the number of sectors re-allocated did not change.

Mar  4 14:17:41 Tower preclear_disk-diff[4044]: ============================================================================

Mar  5 05:45:11 Tower preclear_disk-diff[735]: ========================================================================1.13

Mar  5 05:45:11 Tower preclear_disk-diff[735]: == invoked as: ./preclear_disk.sh -A /dev/sdd

Mar  5 05:45:11 Tower preclear_disk-diff[735]: ==  WDC WD7500AAKS-00RBA0    WD-WCAPT0072817

Mar  5 05:45:11 Tower preclear_disk-diff[735]: == Disk /dev/sdd has been successfully precleared

Mar  5 05:45:11 Tower preclear_disk-diff[735]: == with a starting sector of 64

Mar  5 05:45:11 Tower preclear_disk-diff[735]: == Ran 1 cycle

Mar  5 05:45:11 Tower preclear_disk-diff[735]: ==

Mar  5 05:45:11 Tower preclear_disk-diff[735]: == Using :Read block size = 8225280 Bytes

Mar  5 05:45:11 Tower preclear_disk-diff[735]: == Last Cycle's Pre Read Time  : 2:46:41 (75 MB/s)

Mar  5 05:45:11 Tower preclear_disk-diff[735]: == Last Cycle's Zeroing time  : 2:41:20 (77 MB/s)

Mar  5 05:45:11 Tower preclear_disk-diff[735]: == Last Cycle's Post Read Time : 5:29:56 (37 MB/s)

Mar  5 05:45:11 Tower preclear_disk-diff[735]: == Last Cycle's Total Time    : 10:59:06

Mar  5 05:45:11 Tower preclear_disk-diff[735]: ==

Mar  5 05:45:11 Tower preclear_disk-diff[735]: == Total Elapsed Time 10:59:06

Mar  5 05:45:11 Tower preclear_disk-diff[735]: ==

Mar  5 05:45:11 Tower preclear_disk-diff[735]: == Disk Start Temperature: 37C

Mar  5 05:45:11 Tower preclear_disk-diff[735]: ==

Mar  5 05:45:11 Tower preclear_disk-diff[735]: == Current Disk Temperature: 37C,

Mar  5 05:45:11 Tower preclear_disk-diff[735]: ==

Mar  5 05:45:11 Tower preclear_disk-diff[735]: ============================================================================

Mar  5 05:45:11 Tower preclear_disk-diff[735]: ** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd

Mar  5 05:45:11 Tower preclear_disk-diff[735]:                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

Mar  5 05:45:11 Tower preclear_disk-diff[735]:          Start_Stop_Count =    17      17            0        near_thresh 83787

Mar  5 05:45:11 Tower preclear_disk-diff[735]:  No SMART attributes are FAILING_NOW

Mar  5 05:45:11 Tower preclear_disk-diff[735]:

Mar  5 05:45:11 Tower preclear_disk-diff[735]:  0 sectors were pending re-allocation before the start of the preclear.

Mar  5 05:45:11 Tower preclear_disk-diff[735]:  0 sectors were pending re-allocation after pre-read in cycle 1 of 1.

Mar  5 05:45:11 Tower preclear_disk-diff[735]:  0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.

Mar  5 05:45:11 Tower preclear_disk-diff[735]:  0 sectors are pending re-allocation at the end of the preclear,

Mar  5 05:45:11 Tower preclear_disk-diff[735]:    the number of sectors pending re-allocation did not change.

Mar  5 05:45:11 Tower preclear_disk-diff[735]:  0 sectors had been re-allocated before the start of the preclear.

Mar  5 05:45:11 Tower preclear_disk-diff[735]:  0 sectors are re-allocated at the end of the preclear,

Mar  5 05:45:11 Tower preclear_disk-diff[735]:    the number of sectors re-allocated did not change.

Mar  5 05:45:11 Tower preclear_disk-diff[735]: ============================================================================

 

 

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: ========================================================================1.13

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: == invoked as: ./preclear_disk.sh -A /dev/sdd

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: ==  WDC WD7500AAKS-00RBA0    WD-WCAPT0072817

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: == Disk /dev/sdd has been successfully precleared

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: == with a starting sector of 64

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: == Ran 1 cycle

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: ==

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: == Using :Read block size = 8225280 Bytes

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: == Last Cycle's Pre Read Time  : 2:46:42 (74 MB/s)

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: == Last Cycle's Zeroing time  : 2:40:50 (77 MB/s)

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: == Last Cycle's Post Read Time : 5:27:56 (38 MB/s)

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: == Last Cycle's Total Time    : 10:56:35

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: ==

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: == Total Elapsed Time 10:56:35

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: ==

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: == Disk Start Temperature: 35C

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: ==

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: == Current Disk Temperature: 36C,

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: ==

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: ============================================================================

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: ** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd

Mar  5 21:02:21 Tower preclear_disk-diff[11968]:                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

Mar  5 21:02:21 Tower preclear_disk-diff[11968]:          Start_Stop_Count =    17      17            0        near_thresh 83787

Mar  5 21:02:21 Tower preclear_disk-diff[11968]:      Temperature_Celsius =  116    117            0        ok          36

Mar  5 21:02:21 Tower preclear_disk-diff[11968]:  No SMART attributes are FAILING_NOW

Mar  5 21:02:21 Tower preclear_disk-diff[11968]:

Mar  5 21:02:21 Tower preclear_disk-diff[11968]:  0 sectors were pending re-allocation before the start of the preclear.

Mar  5 21:02:21 Tower preclear_disk-diff[11968]:  0 sectors were pending re-allocation after pre-read in cycle 1 of 1.

Mar  5 21:02:21 Tower preclear_disk-diff[11968]:  0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.

Mar  5 21:02:21 Tower preclear_disk-diff[11968]:  0 sectors are pending re-allocation at the end of the preclear,

Mar  5 21:02:21 Tower preclear_disk-diff[11968]:    the number of sectors pending re-allocation did not change.

Mar  5 21:02:21 Tower preclear_disk-diff[11968]:  0 sectors had been re-allocated before the start of the preclear.

Mar  5 21:02:21 Tower preclear_disk-diff[11968]:  0 sectors are re-allocated at the end of the preclear,

Mar  5 21:02:21 Tower preclear_disk-diff[11968]:    the number of sectors re-allocated did not change.

Mar  5 21:02:21 Tower preclear_disk-diff[11968]: ============================================================================

  • Author

I do have one preclear process running on the Seagate at the moment (that I know of).  I started that process on the mac mini since the two disconnects happened while running on the macbook. 

 

Typing "screen -r" on the macbook it shows the following:

 

There are several suitable screens on:
27990.pts-0.Tower	(Attached)
9458.pts-0.Tower	(Detached)
2660.pts-0.Tower	(Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

 

I'm assuming the two detached are the ones that disconnected prematurely on the macbook and the attached is the process currently running on the mac mini?  I'm currently at a loss as to how to resume them as I don't understand the "screen [-d] -r [pid.]tty.host" prompt. 

I do have one preclear process running on the Seagate at the moment (that I know of).  I started that process on the mac mini since the two disconnects happened while running on the macbook. 

 

Typing "screen -r" on the macbook it shows the following:

 

There are several suitable screens on:
27990.pts-0.Tower	(Attached)
9458.pts-0.Tower	(Detached)
2660.pts-0.Tower	(Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

 

I'm assuming the two detached are the ones that disconnected prematurely on the macbook and the attached is the process currently running on the mac mini?  I'm currently at a loss as to how to resume them as I don't understand the "screen [-d] -r [pid.]tty.host" prompt.

You probably have three processes running at the same time.  that is why it is running so slow.

to attach to an existing session you would type

screen -r 2660.pts-0.Tower

(as an example to attach to the third session in your list)

  • Author

There are several suitable screens on:
27990.pts-0.Tower	(Attached)
9458.pts-0.Tower	(Detached)
2660.pts-0.Tower	(Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

 

I'm assuming the two detached are the ones that disconnected prematurely on the macbook and the attached is the process currently running on the mac mini?  I'm currently at a loss as to how to resume them as I don't understand the "screen [-d] -r [pid.]tty.host" prompt.

You probably have three processes running at the same time.  that is why it is running so slow.

to attach to an existing session you would type

screen -r 2660.pts-0.Tower

(as an example to attach to the third session in your list)

 

Thanks for the guidance, Joe.

 

I'm able to reconnect to 2660 & 9458.  I'm not given enough info on the first one to determine which drive it is.

** Changed attributes in files: /tmp/smart_start_sde  /tmp/smart_finish_sde
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE   
      Raw_Read_Error_Rate =   111     118            6        ok          41892016
          Seek_Error_Rate =    61      60           30        ok          1430299
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    70      72           45        near_thresh 30
      Temperature_Celsius =    30      28            0        ok          30
   Hardware_ECC_Recovered =    36      22            0        ok          41892016
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.

 

The second process (9458) is the WD7500AKS:

= Step 10 of 10 - Verifying if the MBR is cleared.              DONE
= Disk Post-Clear-Read completed                                DONE
Disk Temperature: 35C, Elapsed Time:  11:02:05
========================================================================1.13
==  WDC WD7500AAKS-00RBA0    WD-WCAPT0072817
== Disk /dev/sdd has been successfully precleared
== with a starting sector of 64
============================================================================
** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         Start_Stop_Count =    17      17            0        near_thresh 83787
          Seek_Error_Rate =   100     200           51        ok          0
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.

 

The third process (27990) returns the following, which I assume is because it is running on the mac mini rather than the macbook.

There is a screen on:
27990.pts-0.Tower	(Attached)
There is no screen to be resumed matching 27990.pts-0.Tower.

 

I guess the million dollar question is can I end the "2660" process somehow so that there are not two running on the Seagate drive at the same time?

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.