Jump to content

oconnellc

Members
  • Posts

    146
  • Joined

  • Last visited

Posts posted by oconnellc

  1. 10 hours ago, jowi said:

    Like i said, the media are bluray and UHD ISO's and BDMV structures. No mp4 or dvd's. Just copies of actual Bluray's and UHD's. Each in a separate folder.

    I guess Plex can't handle bluray/UHD ISO's or BDMV structures?

    https://support.plex.tv/articles/201426506-why-are-iso-video-ts-and-other-disk-image-formats-not-supported/

     

    Basically, no.  Plex doesn't support those structures.

    • Upvote 1
  2. So, I figured out what is keeping my disks spun up...  I have my Plex docker on a disk in my array.  I don't remember what I did to put it there.  How can I move it?  I have a cache disk and so I have the configuration files there, but the docker.img file is still in my array.  If anyone could point me to some instructions for moving, that would really help me out.

  3. 3 hours ago, Squid said:

    If you always want to run the latest and greatest Plex (which seems to have an update for it every minute or so), then switch to the LinuxServer flavour of Plex.

    I don't.  I'm fine waiting for the Lime docker to get updated.  I don't have any issues with my current installation and there isn't any functionality (that I know of) that I'm eager to start using.  I'm happy with the current level of 'service', especially given that it was free to me.  I guess I'm just curious to know if someone is maintaining the Lime version of the Docker?  Eventually, there will be a security patch that I should have or something else equally important and I want to know if someone is, even if it is moving very slowly, maintaining the Docker.

     

    Thanks for your help!

  4. I'm kinda new to this particular game and so I hope I'm not asking a silly question.  I need to buy a UPS.  The research I'm doing is a little inconsistent.  Some things report that you need a UPS to provide a pure sine wave and other people say it isn't terribly important.  Honestly, I'm willing to spend a few extra bucks to get a UPS that will 'just work' and not require much time playing with it.  I really only need something that will allow me to set unraid (v6.1.3) to gracefully shut itself down if the power is out for more than a few minutes.  This is a simple home application, so I don't need anything fancy.  I just want to power the unraid box and maybe one other desktop machine running windows (plus monitors for both).

     

    Any reco's would be greatly appreciated.  (and, should I bother upgrading unraid to 6.1.8 first)

     

    Thanks,

    Chris

  5. That happened to me once.  But only once.  I had to hard restart the popcorn hour and then everything worked fine, I suspect because the initial attempt had spun up the disks.  Every time after that, I get a message saying 'buffering' and then things run like a champ.

     

    There are other threads about that subject.  I haven't really investigated them, but I know some solutions involved things like a script that ran every X seconds looking for the player to be active on the network.  If the script found the player, it just spun up the drive.

     

    Chris

  6. Sorry if this is a 'duh' kind of question, but I am going to upgrade to 4.5.4 to get support for a card I just purchased.  I have been running 4.4.2 for a couple years now, and would have happily stayed on that platform, running bubbaq for the rest of the life of my hardware.

     

    So, I know that the simple upgrade steps are (obviously) simple.  But, what does bubbaraid add to the mix?  Do I have to remove bubbaraid and then upgrade and add bubbaraid back?  Or do I drop 4.5.4 on top of by bubbaraid/4.4.2 system?

     

    Thanks,

    Chris

  7. I've got this working using a networked share in my c-200.  But, I'm thinking of adding another and the word on the street is that the best performance is obtained by streaming using http.  Anyone have this working?  Care to share a few of the details?  I have bubbaraid installed, so I already have a webserver running on my Tower, so I'm hoping just a few nudges in the right direction will get me going...

     

    Thanks,

    Chris

  8. Scanning the library actually just generates a bunch of html files.  The popcorn hour renders the html the same way a browser would.  You can just open up 'index.html' in a browser and see what the skin will look like on the popcorn hour.  All the links should work the same way in a browser that they will work in a pch.

     

    Chris

  9. Using the GUI to create a script is pretty easy, it turns out.  After you choose your settings, go to the 'Query Editor' tab and click the button to generate the query.  This represents the command line arguments to the CLI.  Here is a link to the Handbrake page with the parameters: http://trac.handbrake.fr/wiki/CLIGuide  One thing to look out for is that the gui will generate a file with the chapter increments.  The flags for this will be on the generated query unless you go out of your way to turn them off.  I wasted a lot of time trying to figure out if there was a problem with my encoding when it turned out that somehow I had the 'c' setting in there limiting me to the first 17 chapters of a movie.

     

    In case it might help someone out, here is the script that I put together for encoding movies for my iPhone (based on the iPhone settings of Handbrake).  Note, you may not have your movies in the same place I have mine :)

     

    HandBrakeCLI -i /mnt/disk1/Movies/$1 -t 1 -o /mnt/disk1/Movies/movie_stuff/$1.m4v -f m4v -X 480 -e x264 -q 0.59 -a 1 -E faac -B 128 -R 48 -6 dpl2 -D 1 -x level=30:cabac=0:ref=2:mixed-refs=1:analyse=all:me=umh:no-fast-pskip=1 -v

     

    Thanks again for building this.  This is such a great addition to my server and stuff like this is the reason I bought a core2duo with 4G of ram...

     

    Chris

  10. Did you by chance have a "Long" or "Short" status test queued up when you started the preclear process?  (As far as I know, the "Offline data collection activity" refers to those two activities)

     

    In any case, it looks like a nicely working disk.  Your new SATA cable is working well.

     

    That is nice to hear.  I did set up at least on smart status report.  I don't remember when exactly, but I'm guessing that that could be what you are referring to.  Also, just to make sure (I'm anal and paranoid, a combination that bothers my wife to no end), I'm actually still using the old cable.  I just pulled the old cable out of one of the plugs on the mobo and put it into a different one.  I'm wondering if the plug on the mobo could be bad?

     

    Thanks again for your help.  How is it that free support on a board like this is better than paid support for so many products?

     

    Chris

  11. So, I bought a new SATA cable, but just for grins decided to give the old one one last try by plugging it into a different plug on the mobo.  I set preclear up to run for 4 cycles and it worked.  Go figure.  However, I get a message when the last cycle ran and I don't know how to interpret it.  Does this make sense to anyone?

     

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

    =                unRAID server Pre-Clear disk /dev/sdc

    =                      cycle 4 of 4

    = 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 - Testing if the clear has been successful.    DONE

    = Disk Post-Clear-Read completed                                DONE

    Elapsed Time:  44:59:41

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

    ==

    == Disk /dev/sdc has been successfully precleared

    ==

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

    S.M.A.R.T. error count differences detected after pre-clear

    note, some 'raw' values may change, but not be an indication of a problem

    19,20c19,20

    < Offline data collection status:  (0x82)      Offline data collection activity

    <                                      was completed without error.

    ---

    > Offline data collection status:  (0x84)      Offline data collection activity

    >                                      was suspended by an interrupting command from host.

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

     

    Thanks,

    Chris

  12. Ok.  Thanks for the tip.  It is a new drive, so I went into the guts of the thing, unplugged and replugged the SATA cable back into the drive and made sure I pushed extra hard to push it both into the drive and the mobo.  Then, for grins, I decided to try again and preclear is now running.  I'm 15GB into reading a 1TB drive.  So, I should know more by morning.

     

    If I'm reading this right, either the cable is bad, or I didn't have it plugged in 'well' the first time.  So, for my own edification, I would appreciate if anyone could answer a question or two.  If the either of these two is correct (bad cable or badly connected), why did everything other than preclear seem to work.  The drive got exported and I could add it to the array.  unraid would preclear it (something that took several hours and resulted in many many writes to the drive).  I was also able to complete most of a preclear cycle on the disk the first time around.  Shouldn't that preclear cycle have failed at the same place (at the beginning, instead of several hours in)?

     

    Is this a function of quantity, not quality?  Could I have read 1 byte from the drive every day forever, but as soon as I tried to read a 3 GB video file, would I have crashed and burned?

     

    Thanks again for your help and the cool utility.

     

    Chris

  13. Any ideas why the preclear script wouldn't run?  I got a new WD 'Green' drive and tried to run preclear and after typing 'Yes', I got the preclear screen, but it was just frozen and nothing happened.  So, I decided to just go ahead and add the drive to the array, to see what would happen.  Unraid added the drive, but I had to wait about 4 hours while unraid cleared the disk.  No problems there.  So, after that happened, I removed it from the array and tried to run preclear again.  I ran just fine, until it got to the last step of reading the disk for the final time and froze 88% of the way through.  So, I stopped it and tried to run preclear again.  This time, it froze and wouldn't run.  So, I added it back to the array and I waited for another 4 hours while unraid cleared it again.  This surprised me as I figured unraid should see the disk as cleared.  So, after waiting the 4 hours, I tried to run preclear again.  Again, no luck.

     

    So, I decided to do a 'smartctl --test=long /dev/sdb' and so now I have to wait 255 minutes.  Any ideas what is going on?

  14. I can't remember if I had to stop parity manually or if it didn't run when I restarted the array.  In any case, I kicked it off and it ran just fine.  So, now I'm just burning it in with 'preclear'.

     

    I'm doing the as the preclear script updates and it looks like I'm reading from each disk at about 100MB/sec as I run preclear on both disks at the same time.  That seems like it is pretty fast, but I don't know if this is necessarily a good test or not.

     

    Chris

  15. Thanks.  I didn't realize that the parity didn't have a filesystem.  In retrospect, it makes sense.  I just started the array, didn't have it rebuild parity.  I've learned a lot from your last two posts, and I'll try to learn more before asking questions next time to avoid wasting your time.  Given what I have learned, I will probably start preclear runs on both disks with a count of 5 or 10 just to put them through their paces a bit before starting things up.  This is a brand new, first time build for me, so I have been a bit paranoid before starting out.  Given how long a singly cycle takes for me, I should have an operational unraid by Monday or so.

     

    Thanks again for all of your help.

     

    Unrelated...  what do you use to turn a screen grab into an image?  My only thought was to hit "alt + prtscrn" and paste it into word.  If you know of a tool that would let me save it directly as an image that would help.

     

    Thanks again.

  16. Thanks for taking a look.  Just to make sure I am clear and understand you, 'Unformatted' is alright.  However, only the first drive disk had that.  The parity disk didn't say 'Unformatted', it just had a "-" character.  Maybe parity is "different" and that is what it is supposed to say?  I didn't click the button to have unraid format any unformatted drives.  Assuming that "-" is not a problem, I will do that and then start a parity check.

     

    Sorry I didn't upload the screen shot, but there is a problem with the forum now and it reports an error when trying to upload a file.

     

    Thanks again,

    Chris

  17. Oh, and as for the status of the array.  Well, I can't upload anything, so I'll describe it to you.  I reassigned the devices to a spot in the array (same place they were in before), then I went to the main page and started the array.  Both disks are 'green' and have lots of reads/writes.  For the 'Free' number, the parity disk (sda in all my previous posts, the 1TB WD drive) just has a dash "-".  The other disk (a WD 750 GB drive) says 'Unformatted'.  I don't understand that at all...  Since both completed the preclear, shouldn't they both be 'Unformatted'?

  18. So, I got an error trying to upload the files, so here is the actual contents.  The only difference I can see between the two is the the last section with the info about the self test log structure.

     

    smart.txt

    smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen

    Home page is http://smartmontools.sourceforge.net/

     

    === START OF INFORMATION SECTION ===

    Device Model:    WDC WD1001FALS-00J7B0

    Serial Number:    WD-WMATV0509648

    Firmware Version: 05.00K05

    User Capacity:    1,000,204,886,016 bytes

    Device is:        Not in smartctl database [for details use: -P showall]

    ATA Version is:  8

    ATA Standard is:  Exact ATA specification draft version not indicated

    Local Time is:    Fri Feb  6 07:15:23 2009 GMT+6

    SMART support is: Available - device has SMART capability.

    SMART support is: Enabled

     

    === START OF READ SMART DATA SECTION ===

    SMART overall-health self-assessment test result: PASSED

     

    General SMART Values:

    Offline data collection status:  (0x84) Offline data collection activity

    was suspended by an interrupting command from host.

    Auto Offline Data Collection: Enabled.

    Self-test execution status:      (  0) The previous self-test routine completed

    without error or no self-test has ever

    been run.

    Total time to complete Offline

    data collection: (19200) seconds.

    Offline data collection

    capabilities: (0x7b) SMART execute Offline immediate.

    Auto Offline data collection on/off support.

    Suspend Offline collection upon new

    command.

    Offline surface scan supported.

    Self-test supported.

    Conveyance Self-test supported.

    Selective Self-test supported.

    SMART capabilities:            (0x0003) Saves SMART data before entering

    power-saving mode.

    Supports SMART auto save timer.

    Error logging capability:        (0x01) Error logging supported.

    General Purpose Logging supported.

    Short self-test routine

    recommended polling time: (  2) minutes.

    Extended self-test routine

    recommended polling time: ( 221) minutes.

    Conveyance self-test routine

    recommended polling time: (  5) minutes.

    SCT capabilities:       (0x303f) SCT Status supported.

    SCT Feature Control supported.

    SCT Data Table supported.

     

    SMART Attributes Data Structure revision number: 16

    Vendor Specific SMART Attributes with Thresholds:

    ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

      1 Raw_Read_Error_Rate    0x002f  200  200  051    Pre-fail  Always      -      0

      3 Spin_Up_Time            0x0027  232  229  021    Pre-fail  Always      -      8375

      4 Start_Stop_Count        0x0032  100  100  000    Old_age  Always      -      17

      5 Reallocated_Sector_Ct  0x0033  200  200  140    Pre-fail  Always      -      0

      7 Seek_Error_Rate        0x002e  200  200  000    Old_age  Always      -      0

      9 Power_On_Hours          0x0032  100  100  000    Old_age  Always      -      47

    10 Spin_Retry_Count        0x0032  100  253  000    Old_age  Always      -      0

    11 Calibration_Retry_Count 0x0032  100  253  000    Old_age  Always      -      0

    12 Power_Cycle_Count      0x0032  100  100  000    Old_age  Always      -      10

    192 Power-Off_Retract_Count 0x0032  200  200  000    Old_age  Always      -      4

    193 Load_Cycle_Count        0x0032  200  200  000    Old_age  Always      -      17

    194 Temperature_Celsius    0x0022  122  107  000    Old_age  Always      -      28

    196 Reallocated_Event_Count 0x0032  200  200  000    Old_age  Always      -      0

    197 Current_Pending_Sector  0x0032  200  200  000    Old_age  Always      -      0

    198 Offline_Uncorrectable  0x0030  200  200  000    Old_age  Offline      -      0

    199 UDMA_CRC_Error_Count    0x0032  200  200  000    Old_age  Always      -      0

    200 Multi_Zone_Error_Rate  0x0008  200  200  000    Old_age  Offline      -      0

     

    SMART Error Log Version: 1

    No Errors Logged

     

    SMART Self-test log structure revision number 1

    Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error

    # 1  Extended offline    Completed without error      00%        27        -

    # 2  Extended offline    Aborted by host              90%        24        -

     

    SMART Selective self-test log data structure revision number 1

    SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS

        1        0        0  Not_testing

        2        0        0  Not_testing

        3        0        0  Not_testing

        4        0        0  Not_testing

        5        0        0  Not_testing

    Selective self-test flags (0x0):

      After scanning selected spans, do NOT read-scan remainder of disk.

    If Selective self-test is pending on power-up, resume after 0 minute delay.

     

    and smart2.txt

    smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen

    Home page is http://smartmontools.sourceforge.net/

     

    === START OF INFORMATION SECTION ===

    Device Model:    WDC WD1001FALS-00J7B0

    Serial Number:    WD-WMATV0509648

    Firmware Version: 05.00K05

    User Capacity:    1,000,204,886,016 bytes

    Device is:        Not in smartctl database [for details use: -P showall]

    ATA Version is:  8

    ATA Standard is:  Exact ATA specification draft version not indicated

    Local Time is:    Fri Feb  6 07:31:31 2009 GMT+6

    SMART support is: Available - device has SMART capability.

    SMART support is: Enabled

     

    === START OF READ SMART DATA SECTION ===

    SMART overall-health self-assessment test result: PASSED

     

    General SMART Values:

    Offline data collection status:  (0x85) Offline data collection activity

    was aborted by an interrupting command from host.

    Auto Offline Data Collection: Enabled.

    Self-test execution status:      (  0) The previous self-test routine completed

    without error or no self-test has ever

    been run.

    Total time to complete Offline

    data collection: (19200) seconds.

    Offline data collection

    capabilities: (0x7b) SMART execute Offline immediate.

    Auto Offline data collection on/off support.

    Suspend Offline collection upon new

    command.

    Offline surface scan supported.

    Self-test supported.

    Conveyance Self-test supported.

    Selective Self-test supported.

    SMART capabilities:            (0x0003) Saves SMART data before entering

    power-saving mode.

    Supports SMART auto save timer.

    Error logging capability:        (0x01) Error logging supported.

    General Purpose Logging supported.

    Short self-test routine

    recommended polling time: (  2) minutes.

    Extended self-test routine

    recommended polling time: ( 221) minutes.

    Conveyance self-test routine

    recommended polling time: (  5) minutes.

    SCT capabilities:       (0x303f) SCT Status supported.

    SCT Feature Control supported.

    SCT Data Table supported.

     

    SMART Attributes Data Structure revision number: 16

    Vendor Specific SMART Attributes with Thresholds:

    ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

      1 Raw_Read_Error_Rate    0x002f  200  200  051    Pre-fail  Always      -      0

      3 Spin_Up_Time            0x0027  232  229  021    Pre-fail  Always      -      8375

      4 Start_Stop_Count        0x0032  100  100  000    Old_age  Always      -      17

      5 Reallocated_Sector_Ct  0x0033  200  200  140    Pre-fail  Always      -      0

      7 Seek_Error_Rate        0x002e  200  200  000    Old_age  Always      -      0

      9 Power_On_Hours          0x0032  100  100  000    Old_age  Always      -      47

    10 Spin_Retry_Count        0x0032  100  253  000    Old_age  Always      -      0

    11 Calibration_Retry_Count 0x0032  100  253  000    Old_age  Always      -      0

    12 Power_Cycle_Count      0x0032  100  100  000    Old_age  Always      -      10

    192 Power-Off_Retract_Count 0x0032  200  200  000    Old_age  Always      -      4

    193 Load_Cycle_Count        0x0032  200  200  000    Old_age  Always      -      17

    194 Temperature_Celsius    0x0022  122  107  000    Old_age  Always      -      28

    196 Reallocated_Event_Count 0x0032  200  200  000    Old_age  Always      -      0

    197 Current_Pending_Sector  0x0032  200  200  000    Old_age  Always      -      0

    198 Offline_Uncorrectable  0x0030  200  200  000    Old_age  Offline      -      0

    199 UDMA_CRC_Error_Count    0x0032  200  200  000    Old_age  Always      -      0

    200 Multi_Zone_Error_Rate  0x0008  200  200  000    Old_age  Offline      -      0

     

    SMART Error Log Version: 1

    No Errors Logged

     

    SMART Self-test log structure revision number 1

    Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error

    # 1  Short offline      Completed without error      00%        47        -

    # 2  Extended offline    Completed without error      00%        27        -

    # 3  Extended offline    Aborted by host              90%        24        -

     

    SMART Selective self-test log data structure revision number 1

    SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS

        1        0        0  Not_testing

        2        0        0  Not_testing

        3        0        0  Not_testing

        4        0        0  Not_testing

        5        0        0  Not_testing

    Selective self-test flags (0x0):

      After scanning selected spans, do NOT read-scan remainder of disk.

    If Selective self-test is pending on power-up, resume after 0 minute delay.

     

    Thanks again.

  19. Ok, I think I am in a better state now.  I have run the preclear on both disks and it completed.  The 750GB disk finished with no issue.  The 1TB preclear looks like this:

     

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

    =                unRAID server Pre-Clear disk /dev/sda

    =                      cycle 1 of 1

    = 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 - Testing if the clear has been successful.    DONE

    = Disk Post-Clear-Read completed                                DONE

    Elapsed Time:  9:43:07

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

    ==

    == Disk /dev/sda has been successfully precleared

    ==

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

    S.M.A.R.T. error count differences detected after pre-clear

    note, some 'raw' values may change, but not be an indication of a problem

    19,20c19,20

    < Offline data collection status:  (0x82)      Offline data collection activity

    <                                      was completed without error.

    ---

    > Offline data collection status:  (0x84)      Offline data collection activity

    >                                      was suspended by an interrupting command from host.

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

     

    So, here is a smart report for that disk (smart.txt).  I don't know if the fact that "Offline data collection activity was suspended" is a big deal or not.  So, I decided to run another smart test, and then I got another report (smart2.txt).

     

    I appreciate you taking the time to look at this.

  20. Well, I can't send you either of the logs.  I went over to the drive to 'listen' and didn't hear anything.  The sides are not attached, so I thought I would slide one off and double check the cables and so I had to move the case a few inches and hit the 'power' button and shut it down.

     

    So, I had gone through the syslog and didn't see anything that looked scary, but that doesn't mean anything...  So, I restarted the box and for grins, I went to the tower management page and added the two disks back to the array and started it up, and surprise, the management page told me that the drive that had 'frozen' was all right and formatted.  The drive that had finished said 'unformatted'.  No idea how that happens...

     

    So, I'm running a smartctl report on both disks now.  I have to go to work, so I'll post the logs when I get home and then maybe rerun the preclear for a single cycle.

     

    Thanks for the help.

     

    BTW, I'm pretty new to all this command line stuff, so here is the syntax for the smartctl report I ran.  There are a lot of options and so I'm not sure which is correct.

     

    root@Tower:~# smartctl --test=long /dev/sda

    smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen

    Home page is http://smartmontools.sourceforge.net/

     

    === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===

    Sending command: "Execute SMART Extended self-test routine immediately in off-line mode".

    Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful.

    Testing has begun.

    Please wait 221 minutes for test to complete.

    Test will complete after Thu Feb  5 11:44:39 2009

     

    Use smartctl -X to abort test.

     

    Where will smartctl write the report?

     

    Chris

  21. I ran this for a single cycle against a WD 1TB drive.  Got up this morning and the display seems 'frozen'.  No errors or anything, but it isn't doing anything.  While this was running I also did a single cycle for a WD 750 GB drive which appears to have completed successfully.  Here is the display for the frozen drive:

     

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

    =                unRAID server Pre-Clear disk /dev/sda

    =                      cycle 1 of 1

    = 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 - Testing if the clear has been successful.    DONE

    = Post-Read in progress: 88% complete.

    (  888,330,240,000  of  1,000,204,886,016  bytes read )

    Elapsed Time:  9:17:36

     

    I'm not sure if this 'happens' sometimes and I should let it continue or if something horribly wrong has happened with the drive.  Any ideas?

     

    Thanks,

    Chris

     

    edit

    FWIW, I just ran 'top' and "preclear" seems to still be doing something, even though it isn't updating the display:

     

    top - 07:16:06 up 10:47,  2 users,  load average: 1.00, 1.00, 1.00

    Tasks:  64 total,  2 running,  62 sleeping,  0 stopped,  0 zombie

    Cpu(s): 50.0%us,  0.0%sy,  0.0%ni, 50.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st

    Mem:  4113156k total,  172132k used,  3941024k free,      80k buffers

    Swap:        0k total,        0k used,        0k free,  153560k cached

     

      PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND

    27981 root      20  0  2708  872  328 R  100  0.0  27:54.22 preclear_disk.s

        1 root      20  0  776  304  264 S    0  0.0  0:01.57 init

     

×
×
  • Create New...