mdaryabe

Members
  • Posts

    13
  • Joined

  • Last visited

mdaryabe's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Sorry, UD installed but no Recycle Bin
  2. I Have UD Installed but not the recyle bin
  3. Hi Everyone, I got an error in fix common problems in regards to an invalid folder in /mnt. A quick search and suggestion was to restart the server which I did. but unfortuanly that did not fix the problem. There is a "rootshare" folder in my /mnt that I have no idea how it got there. I haven't installed anything new on the server for a few weeks. Just general docker/plugin update. I have browsed to the folder, It's empty. I have tried to delete the folder but I get permission denied. I have tried using "MC" to delete it; with same results. Could you please take a look at it and maybe point me to the right direction. Thank you Invalid folder rootshare contained within /mnt caspian-1-diagnostics-20220311-0858.zip
  4. That worked! Thank you so much. Just for clarification, If now I want to replace Disk 7. I would just shut down the Array and replace that drive physically and run the array and let the parity rebuild the drive?
  5. So I ran "-L" on disk 5, shut down the Array and turned it back on and it seems that it fixed Disk 5, it is now mounted with around 6TB data on it. Should I do the same for Disk 8?
  6. Disk 5 and 8 both: Should I use the following command for Disk 5 with 2 parity drives? caspian-1-diagnostics-20210820-0844.zip I much appreaciate your help!
  7. So the parity-checkl/data-rebuild is done on those drives. they both show as green on the main page but they both still say "Unmountable: Not mounted" Do you need an updated log file?
  8. Thank you, I have updated the screenshots. I'll wait for the parity to finish and will update you. So Disk 7 and 8 were the disk I was trying to replace. What happened is, that I unplugged disk 5(didn't count the parity drives on the physical server while array was on - Dumb me!) and plugged it back in right away. Then shut down the array and replaced both 7 and 8. Unraid said it's missing more than 2(Disk 5, 7, 8 ) drives from parity and is unable to fix it. so I replaced back disk 8(original 4tb) with only disk 5, 8 missing I started the parity/rebuild. which did it for Disk 8. After that, I went on Maintenace mode to do the check for Drive 5. and it was giving me an error. I shut down the array and removed the drive from the array and started without disk 5. then turned off the array and added disk 5 again and started the parity check. Btw Disk 5, is the same original disk. it was just unplugged and plugged back in right away. I think it rebuild the array without that disk once, and now it's rebuilding that 8tb(Disk 5) drive again. Disk 7 is the next disk I want to replace after its fixed. Once again, Thank you for your help!
  9. Hi Guys, I got myself in a bit of trouble. I was trying to replace 2 of my older hard drives with a couple of 10tb drives. While the array was on, I accidentally pulled Disk 5 out, but I plugged it back in right away(not the hdd that I wanted to replace). Then I shut down the array and removed one of the 4tb hdd(Disk 8) and replaced it with one of the new 10 TB hdd(disk 8). Restarted the array and waited for the party sync to start. initially Disk 5 was showing disabled. after the Parity check I have(which synced for Disk 8) restarted the array in the maintenance mode, now it shows the device as emulated while its trying to rebuild the Disk 5. On the main page it still shows both Disk 5 and Disk 8 as unmountable. Now my question is would they both go back to normal after the parity sync? What do you guys recommend to do? diagnostics-20210819-0839.zip