Jump to content

troymeredith

Members
  • Posts

    35
  • Joined

  • Last visited

Posts posted by troymeredith

  1. 20 minutes ago, trurl said:

    When the array is stopped and it is ready to allow disk assignments as in your screenshot, then it will allow you to assign parity2. If nothing is assigned to parity2 then when the array is started parity2 doesn't appear.

    gotcha - man thanks!

  2. 1 hour ago, trurl said:

    Not really very important, but your syslog is filling with these:

    
    Apr 14 07:06:03 Tower emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Basic.key (-3)

    Apple ecosystems seem to drop these annoying ._ files on everything they touch. You should delete that file from your flash after you get everything else fixed.

     

    Parity and parity2 are NOT interchangeable.

     

    Post a screenshot of Main - Array Devices.

     

    Screenshot 2019-04-14 at 14.40.10.png

  3. Disc issues - again!! My HDDs range from approx 4 to 18 months old and two of them are now unassigned on my microserver.

     

    The last time this happened, the issue was power-related, and I checked the cabling (disconnected then reconnected) until I got a positive result.

     

    I've done the same thing now, but to no avail.

     

    Is more checking of cables required, am I impatient by posting this, or is there something wrong with my discs?

     

    I have attached a diag in the hope that someone can immediately spot the problem and offer some guidance.

     

    TIA

    tower-diagnostics-20190414-0722.zip

  4. 15 hours ago, troymeredith said:

    Checked cabling, made sure everything was connected (pulled apart and then re-inserted) and powered on the server.  Currently rebuilding and has gone further than previous attempts.  Looking hopeful, but I'll keep an eye on it.  Will keep you updated.  Thanks for all your help!! 😊

     

  5. On 12/25/2018 at 11:13 AM, johnnie.black said:

    There are ATA errors on 3 different disks, so it's likely a power or connection problem, since it's a Microserver there's only one mini SAS cables, make sure it's well attached, and if that doesn't help try with a different PSU and/or a new cable.

    Checked cabling, made sure everything was connected (pulled apart and then re-inserted) and powered on the server.  Currently rebuilding and has gone further than previous attempts.  Looking hopeful, but I'll keep an eye on it.  Will keep you updated.  Thanks for all your help!! 😊

  6. 12 minutes ago, johnnie.black said:

    Stop the array, unassign the disk, start the array, stop the array, re-assign the disk, start the array to begin rebuilding, if the rebuild fails grab the diags before rebooting.

     

    P.S,; Like mentioned, disk1 is empty, you still need to rebuild to turn the array healthy, but there's not data there

    just tried, got to about 1.5% before the rebuild failed 😞

  7. 19 hours ago, Frank1940 said:

    First give us the last four digits of the serial number of the drive which failed.  

     

    Second, describe what you mean by "It reached 100% then failed.".  Did the the drive fail?  Of did the preclear operation fail to complete?  Were you using the preclear plugin or the preclear script (uses the Command Line)?  

    Last 4 digits of s/n: K0DY

     

    The preclear failed to complete, i used the plugin.

  8. HI there,

     

    I've had my unraid server for a while now, but i am far from an expert - hence this message. A couple of weeks ago, i replaced a drive because i appeared to have failed.  Inserted the new drive and performed a preclear on it.  It reached 100% then failed.

     

    Not sure what to do or how to proceed.  I attach my diagnostics in the hope that someone more knowledgable than me can detect the issue, provide a little guidance and send me on my way.

     

    Thanks in advance. 

    tower-diagnostics-20181223-1734.zip

  9. Dear All,
     
    I've had Couch Potato on my docker for a good few years now, however in the last couple of months I have been unable to connect to it.
     
    I get a "This site can't be reached" message along with:
     
    ERR_CONNECTION_REFUSED
     
    I've been using Chrome and Safari, same result.
     
    Any thoughts as to what I can do to rectify and get connected to CP again?

     

    Diagnostics attached.
     
    Many thanks in advance 

    tower-diagnostics-20180218-1605.zip

  10. Dear All,

     

    I've had Couch Potato on my docker for a good few years now, however in the last couple of months I have been unable to connect to it.

     

    I get a "This site can't be reached" message along with:

     

    ERR_CONNECTION_REFUSED

     

    I've been using Chrome and Safari, same result.

     

    Any thoughts as to what I can do to rectify and get connected to CP again?

     

    Many thanks in advance 

     

     

  11. 3 minutes ago, johnnie.black said:

    Don't understand the question.

     

    I would do a new config (tools -> new config) and then assign only the 3 data disks, start the array and if all works correctly add a new parity disk when you get a spare, if not post new diags, but note that like I said you'll lose any data written to disk3 since you disabled it.

    i've got no problem losing any data from disk3, nothing i can't get back anyway - will create a new config...

  12. 3 minutes ago, johnnie.black said:

    But it's still disabled, once a disk is disabled it's needs to be rebuilt or reset with a new config.

     

    Not much you can do about it now, since parity is failing it can no longer correctly emulate disk3.

    swap out disk 3 and parity, or is that too much?

  13. 2 minutes ago, johnnie.black said:

    You need to replace it, but since you currently have disk3 disable you need to figure out what to do about it, IIRC you disabled it on purpose, assuming nothing was written to the emulated disk you could do a new config without parity, see if everything is working correctly and if yes add a new parity disk later and then resync parity.

    ok, I can pop in a replacement for the parity now, disk3 has been re-inserted when i updated the flash - no idea if anything has been written to it.  so should i still replace the parity?

  14. 30 minutes ago, johnnie.black said:

    Parity failed:

     

    
    Feb  4 16:47:38 Tower kernel: md: disk0 read error, sector=2930369288
    Feb  4 16:47:38 Tower kernel: ata1: EH complete
    Feb  4 16:47:38 Tower kernel: md: disk0 read error, sector=2930369296
    Feb  4 16:47:38 Tower kernel: md: disk0 read error, sector=2930369304
    Feb  4 16:47:38 Tower kernel: md: disk0 read error, sector=2930369312
    Feb  4 16:47:38 Tower kernel: md: disk0 read error, sector=2930369320
    Feb  4 16:47:38 Tower kernel: md: disk0 read error, sector=2930369328
    Feb  4 16:47:38 Tower kernel: md: disk0 read error, sector=2930369336
    Feb  4 16:47:38 Tower kernel: md: disk0 read error, sector=2930369344

     

    
    197 Current_Pending_Sector  -O--C-   100   100   000    -    8
    198 Offline_Uncorrectable   ----C-   100   100   000    -    8

     

    ok, complete novice at this, so how do i proceed?

  15. 6 hours ago, johnnie.black said:

    The server isn't fully starting, no disks are mounted, I also see ATA timeouts on several disks, something weird going on there, you may try to redo your flashdrive, back it up first, then use the latest release and restore the config folder from current flash, then boot and upload new diags.

    updated flash drive with latest release, fired up server, disk light on server is solid, disks being mounted for 45mins now.

     

    diag attached

    tower-diagnostics-20180204-1718.zip

  16. 7 hours ago, johnnie.black said:

    Most likely filesystem corruption, maybe the emulated disk, you should still be able to get the diagnostics using the console/SSH by typing diagnostics

     

    But like trurl said

     

    disk 3 missing because i haven't inserted it, as i found the risk of freezing greatly reduced without it inserted.  will re-insert and try to run the diagnostic again

×
×
  • Create New...