Jump to content

trurl

Moderators
 View Profile  See their activity

  • Posts

    44,054

  • Joined

  • Last visited

  • Days Won

    137

 Content Type 

Everything posted by trurl

  1. trurl
    Since you have dual parity, you can rebuild disk8 without having disk3 installed.
  2. trurl
    Do you know how to proceed?
  3. trurl
    Seems I misunderstood. It sounds like the disabled disk is not the disk you want to remove. Is that correct? Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
  4. trurl
    If there is any data on the emulated drive you want to keep you will have to copy it elsewhere before removing it.
  5. trurl
    To re-enable it in the array you have to rebuild it. To remove it from the array, New Config, unassign it, and rebuild parity.
  6. trurl
    You have configured docker.img to be on the isos share instead of system where it normally would be. And isos is on the array.
  7. trurl
    Looks like it might still have your config. Have you tried it?
  8. trurl
    Yes the missing disk can be read and even written but you have no redundancy until replace/rebuild of course.
  9. trurl
    Post a screenshot of the contents of that config folder.
  10. trurl
    Go to Tools-diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
  11. trurl
    Parity2 does have a lot of reallocated. I didn't look at the others. Are there SMART warnings for any other disks on the Dashboard?
  12. trurl
    You didn't notice the SMART warning on disk2? Extremely high number of CRC (connection) errors. Suspect you have numbers in the Errors column on Main also. You are doing parity2 swap? Why don't you have parity assigned?
  13. trurl
    Unless you have some reason to suspect some specific data disk you have no choice but to correct parity. For example, sync errors after a data disk rebuild in which there were errors on one or more disks would be a reason to suspect the rebuilt disk was out-of-sync instead of parity.
  14. trurl
    I think it might be just super.dat (disk assignments) that won't work with trial key. Make a screenshot of your disk assignments so you can assign them again and delete config/super.dat and see if it will let you use a trial key.
  15. trurl
    yes
  16. trurl
    Tools - Diagnostics, attach ZIP to your NEXT post.
  17. trurl
    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.
  18. trurl
    https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=566086
  19. trurl
    Do you know how to use dockers on Unraid?
  20. trurl
    Shouldn't be any rebuild issues due to SSD, but you do want to get SSD out of the array. It would make a good cache. Replace / rebuild parity first of course, then replace / rebuild the data disk.
  21. trurl
    Rebuild is not the way to fix unmountable. Likely the rebuild will also be unmountable. You need to repair the filesystem: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Probably broken user shares is just a symptom of the corrupt disk. Fix that and your user shares should be back, since they are just the top level folders on all disks.
  22. trurl
    The idea of using cache as a hot spare doesn't make as much sense as it did back in the pre V6 days of Unraid. Many will have SSD cache now, and cache is used for much more than just caching user share writes, such as fast data for dockers / VMs.
  23. trurl
    Unraid IS NOT RAID. Each disk is an independent filesystem. Redundancy is provided by 1 or 2 parity drives. No data drive can be larger than any parity drive.
  24. trurl
    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.
  25. trurl
    Shutdown, check connections on disk1 and disk3
×
×
  • Create New...