Jump to content

trurl

Moderators
  • Content Count

    25140
  • Joined

  • Last visited

  • Days Won

    79

Posts posted by trurl


  1. 8 minutes ago, GalaxyBird said:

    suggested restarting but with only 7 drives active.

    If you want to shrink the array, go to Tools - New Config, keep all assignments, then before starting the array, make any changes you want such as removing a drive. Then start the array and let it rebuild parity. Be sure you don't assign a data disk to a parity slot or it will be overwritten by parity.

     


  2. 3 hours ago, nos0n3 said:

    also how were you able to find which disks where the ones assigned to those ata slots

    syslog

    Sep 24 20:44:21 DLNQNT kernel: ata2.00: ATA-9: WDC WD100EMAZ-00WJTA0, JEGKNTAN, 83.H0A83, max UDMA/133
    ...
    Sep 24 20:44:21 DLNQNT kernel: ata3.00: ATA-9: WDC WD100EMAZ-00WJTA0, 1EG8SH2Z, 83.H0A83, max UDMA/133

    There were some reassignments and you can see all this in syslog, but that is the slots those serials ended up being assigned according to smart folder in diagnostics.


  3. Sounds like folklore passed on by people who don't know how things work.

     

    Or maybe you just misinterpreted good advice.

     

    If you schedule mover to run more often hoping it will fix the problem of filling cache, then the advice would be to reconsider what you are doing. No matter how frequently you move, you can't move from cache to slower array as fast as you can write to faster cache. Mover is intended for idle time.


  4. Likely nothing wrong with the original disk. And nothing apparently wrong with this one.

     

    An occasional small number of CRC errors, just go to the Dashboard, click on the warning, and acknowledge it. It will warn again if it increases. If it continues to increase, especially if it is not a small number, then try to fix the connection problem.

     

    No need to replace the disk.

     

     


  5. Seems like we are going back over things already discussed in this thread.

     

    Possibly emulated disk8 is being corrupted by the errors on other disks and maybe the physical disk8 is mountable.

     

    Still mounted disk9 is also showing corruption but that might just be the errors again.

     

    SMART for each disk in question looks OK.

     

    13 minutes ago, GTP said:

    I think I fixed the power/connection issues

    I don't think so.


  6. 38 minutes ago, trurl said:

    Setting a share cache-no means new files will not be written to cache. It also means mover will ignore the share so if it has files on cache they will not be moved. 

    There is help in the webUI. The Help (?) button will toggle Help for the entire webUI on/off. You can also toggle help for a specific setting by clicking on its label.

     

    Here is a FAQ that gives more details about the nuances of the Use cache setting: