FrequencyLost

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

FrequencyLost's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. Thank you for this amazing app. And really loving the latest update with suspend/resume/kill now available from the GUI. Also GUI interaction seems quicker
  2. +1 for this Having switched from Xpenology/Synology to Unraid, the one thing I really miss is a well made built-in file manager. The current Unraid options are extremely clunky in comparison. Without previously using file managers from other NAS/Storage solutions like Synology and QNAP, it may not seem that way or seem like a downgrade, but it certainly is. Considering how underpowered CPU/RAM wise most consumer Synology is, and it has a great file manager. Compared to how powerful some of our Unraid setups are, I dont think resources will be an issue. Having a visually pleasing and modern built-in file manager would be a great addition to the Unraid solution.
  3. @johnnie.black Thank you so much! Followed all of the above and this has worked. As far as I can tell I don't have any data issues. Have deleted anything in the 24 hours preceding the fault to be on the cautious side, and parity resync completed a short while ago. Coming from years of using RAID5 setups until a few months ago when switching to UnRAID. I don't think those setups could have recovered in the same way from errors on more drives than parity, such as with this controller card failure. Lessons learned.. RAID is not a backup Set up an external syslog server Install one of the file integrity plugins, Squid's Checksum or Bonienl's Bunker
  4. Thank you @johnnie.black for the information and for getting back to me. I disabled docker and VMs to stop those log spams and to limit any disk activity when starting the array. Array has been started with disks in emulated mode as instructed. Diagnostics are attached and screenshot below. Thank you in advance.
  5. I'm hoping someone can please give me some guidance on the best way to recover from this catastrophic failure. This happened a few days ago, I downloaded diagnostics then (attached), and shut it down so I could inspect hardware, cables, and order replacement parts. The array has not been restarted since. Based on the number and location of the drives with errors, I believe this was an LSI HBA controller card failure. Parity 1 & 2, Cache 1 & 2, Disk 1 & 2 are all directly connected to the motherboard. Disk 3 to 8 are via an LSI 9217 flashed to HBA controller. Disks with errors are across both 4 port SAS SATA breakout cables. It looks like Disk 3 and Disk 4 failed first and were disabled while being protected by dual parity. The problem is the mass of errors on Disk 5 and Disk 7 that wont be parity protected. This all started at 5am when Mover kicked in and moved data from cache to array. Due to this, I wasn't aware of what was happening until I woke up later in the day. I've been looking at whatever documentation I can find, and forum posts etc, for people who have been similar situations. Only found examples of people with controller card failures with only read errors, or were still protected by parity. https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive https://wiki.unraid.net/Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily If I know what files were moved to the array during the time of failure, can I ignore the parity data and delete the corrupted files? Then rebuild parity based on whats left. So, Unassign parity drives Start array (unprotected) Delete any files in the 24 hours preceding this failure Stop array Assign parity drives and rebuild parity. Will this work? Or is the data on Disks 5 and 7 toast? Any advice or additional options would be greatly appreciated.
  6. Thanks for that information I use command line considerably for networking equipment, but my unraid/linux knowledge is still of beginner level. I read somewhere not to mess with unraid disk shares, so have avoided it so far. But your explanation makes sense, disk to disk or user to user. I've got Krusader installed so will try that method for now and then try rsync later when I'm feeling more confident.
  7. Thanks for this plugin. I have my shares setup so they each use their own hard drive exclusively. I prefer the order of keeping things together, and i've been using this plugin to shift files when necessary to the drive its share is assigned to. One of my shares now exceeds the size of its hard drive, so I've added an additional drive for that share so it uses 2 disks exclusively, similar to the example below, Share 1 = Disk 1 Share 2 = Disk 2 Share 3 = Disk 3, Disk 4 As far as I can tell its not possible, but can you please confirm if there is any way to use this plugin (or other means) to gather the files from Share 3 scattered across all disks and place them on either Disk 3 or Disk 4? Thanks in advance for any information you can provide