Jump to content

almarma

Members
  • Content Count

    129
  • Joined

  • Last visited

Community Reputation

0 Neutral

About almarma

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Norway

Recent Profile Visitors

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

  1. Thank you @Trurl I've run last night a Parity check and it fixed the 3 remaining errors. I've also changed the docker.img path to a particular disk (now it reads /mnt/disk1/docker.img). And I've also stopped the array and adjusted it's size on the settings web interface to 20GB so it matches its real size, so it should be ok now. Thank you again for your assistance with my issue
  2. Hi Trurl. Thanks for your answer. I'm not really sure what you mean, but I'll investigate. I had to resize years ago docker.img because I was running out of space (I think because of Plex, but I'm not sure). Something got messed up, I'll investigate it. I'm not sure why is that. I'll check that too. I don't have a cache drive, so I guess I should just point it to a specific drive and that would do it, right? Yes, I lost control of it and used the terminal (it was the only visible icon from the web interface) to reboot it, but it seems like it crashed during the restart and a parity check started automatically. But every weekend I get a report of health status of the server (I don't remember how I enabled it) and it tells me it's ok. Should I run a new parity anyway?
  3. Hi, It's not the first time that this happens to me and I don't know why is this: I have around 7 dockers installed, and today a couple disappeared (Plex and Duckdns). I have no clue about why this happens. Should I be worried? Normally just by reinstalling them, the appdata is still there so nothing is lost, but it's scary. Any help would be really appreciated. galeon-diagnostics-20201108-1719.zip
  4. Hi everybody. I'm having a weird issue with my server: it has been working great for some months after I replaced the parity drive and I upgraded the RAM after testing it without issue. But on Friday and today again, after some hours being on, it was unresponsive: services like time machine backups couldn't connect, or any docker, but I could open the admin web interface, but only the top part was visible and the bottom part was blank for every tab. The console icon was visible so I used it to reboot but despite I used it, it triggered a new parity check. Can it be caused by some docker or plugin not working fine? Or is it a hardware issue? I attach a diagnostics zip file I generated after rebooting galeon-diagnostics-20201107-2137.zip
  5. Thank you Johnnie. I forgot to mention that I followed this guide step by step and saw no error during the process: https://wiki.unraid.net/The_parity_swap_procedure But I suspect that the old damaged disk I replaced contained maybe those errors and so they were "transmitted" to the new replacement one. Anyway, I'll follow your advice and will do another parity check this evening and check if it returns 0. Thank you again
  6. Hi, After replacing the old parity disk (3TB) with a new one (4TB, precleared) and a data drive with smart issues replaced with the old parity disk following the official guide from the wiki (fantastic guide, by the way), I performed a parity check and 244188000 errors were detected and corrected (yes, 244 millions!). The parity status is Valid. Other than that error, the server is working great, no other issue anywhere. I also replaced some SATA cables with better ones as recommended by @johnnie.black on another thread I opened when I begun having array writing issues, so everything is up and running as expected. Could it be maybe some "leftover issues" from the old damaged drive? Should I panic?
  7. I agree totally. I think that, when creating a native File Explorer it should be pointed really really clear that mixing /mnt/user/ with /mnt/diskN will corrupt data. Thinking about the interface, I think it should be warned at the first use, or pointed very clearly. Not everybody knows or understand Linux and even what "mounting" is. To avoid beginners mistakes I would create "safe" shortcuts to the recommended or safe places to go to manipulate files or folders. I'm thinking about the /mnt/user/ address specifically, I think it should be the default address, and if the user moves out of there (to the higher /mnt/ address) then he or she should get a warning. It takes a while to understand that /user/ correspond to the "Shares" tab within the UnRAID admin page. So maybe the best is to call that shortcut "Shares" for consistency with the UnRAID naming convention. I think having a File Explorer is a great addition to UnRAID. Sometimes deleting or moving files or folders is much faster locally than via LAN, and specially if there's any weird thing going on with permissions or so, having a way to access the file system from the admin UI is a great addition. I like Dolphin, but I miss: - Shortcuts on the left side of the screen. - A text file editor (to edit some settings on some plugins or dockers that require it).
  8. How can you be that sure? I just ask out of curiosity, to learn myself. Because I did the SMART extended test and it was ok and there's not a single error logged into it. Again, how did you found that out? Thank you in advance
  9. Thanks for your answer. But is it 100% sure it's the disk and not the cable? What do you mean with "Parity is failing"? As far as I know, parity is still ok and no error was corrected from parity:
  10. Hi everybody, A few months ago I came here asking for help to disable a supposedly damaged disk. I followed all the instructions but the last one: actually removing the disk from the array. I did it because summer holidays and such, I didn't want to hurry it or even risking to leave the array partially broken while on holidays with no access to the server. Well, now I'm back and last weekend I had an issue with a case fan which became noisy so I replaced it and rearranged the fans in another way because the cables were too tight. Well, after it, a new array test happened and now I saw 17 errors in the Parity disk, and no error in the supposedly damaged one. What's going on here? After that I did a new Extended SMART test from both disks and now none of them has any issues (the Disk3 reported issues before). Can it be the cable? Did I accidentally moved the cables while rearranging the case fans and now it's fine? It's a big weird that the issue has jumped from one disk to another one. This is the array status reporting 17 errors (not parity errors, the array shows as healthy): This is the Test results from the Parity Drive This is the test results from the Disk3 Drive. Here you can notice: - Last test, completed without error. - The previous one (#2) Completed with read failure. - Down in the error log, Error 19 happened at 42930 hours of age. No other error until now (2000 hours more). I've attached also the diagnostics file from my server in case somebody want or can help me. Thank you in advance. galeon-diagnostics-20190816-1010.zip
  11. Thanks for your answer. I did, I run the docker safe permission script but the error kept popping so I'm copying instead of moving so I'm not left with half copied folders. Maybe the safest way to move data deleting it from the original source would be: copy everything, verify, and only then if 100% is copied and ok, then delete the source. Is is done like this?
  12. I have a suggestion for this awesome plugin: I've noticed that, before any operation there's a scan of each share, folder, disk or whatever will be moved to ensure a successful operation (which is great!), but in case of warnings or issues, it's very difficult to read them, because it's a popup that disappears by itself after a few seconds, and you have no time to read it all. I think that, in case of warnings or errors, this popup should be permanent with maybe a "Close" or "OK" button. In this way the user has time to read it all and do the corrections needed to continue. Here's a screenshot example of a warning I get after the scan. It also was the only way I found to read it till the end:
  13. I agree with you. The only reason why I did that was because the "Fix Common Problems" recommended it to me. I had it as a user share but it told me it wasn't recommended
  14. OK. My progress so far: I was able to empty Disk1 totally. I was able to copy Docker.img and /appdata/ from Disk3 to Disk1 (using Dolphin Docker with root access. I copied, I didn't remove anything from Disk3 yet). Yes, I was using a docker app with the docker system still up, but because I just copied it, it seems it worked. Next I shut down Docker service, changed settings to Disk1 Then I changed the share location to use Disk1 instead of 3. I turned on Docker service and checked one by one all the apps and modified its settings to use Disk1 if I saw any path using Disk3. Everything seems to be working fine, and this was in my opinion the most critical part. Next I'll try: to rename Docker.img and /appdata/ folders (adding .backup or something) to see if nothing crashes and it's yet stable. Then I'll restart the Docker service to confirm the old folders are not used at all. And then I plan to reboot the server for same goal. If all goes as planned, I'll move the rest of the folders out of Disk3 and rebuild the array without it. Does it sounds fine? Am I missing some step?