Jump to content

henrik38

Members
  • Posts

    17
  • Joined

  • Last visited

Recent Profile Visitors

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

henrik38's Achievements

Noob

Noob (1/14)

1

Reputation

  1. That's good to know, thank you. When I want to replace my PCIe/SATA card with one that has more than 2 SATA ports, the hardware ID will be different, right? Would I then lose all the data from the two connected drives, even when i disabled VMs prior, because unraid thinks it has lost connection to the sata controller?
  2. Thank you for the quick response Yeah, due to the Fix Common Problems plugin, I noticed this right after a restart, before I moved the PCIe card to a different slot, everything was okay. Btw., I didn't move the PCIe -> SATA card yesterday but today. (I mixed something up) I "fixed" it by removing the card (SATA Controller) from "Other PCI Devices:". After that, there was an error message in the disk log, something along the lines of the controller/disk not supporting hot swap. Then I restarted Unraid, and the SATA controller from the PCIe card was no longer visible under "Other PCI Devices:". Yeah I see haha. Could have ended bad. But isn't that a huge problem? What if it had happened to me when two or more HDDs were connected to the controller? Shouldn't Unraid recognize the controller and the hard drives when the PCIe card has changed slots? And why was the card then automatically assigned to my VM without me passing through the IOMMU group (I didn't even thought that was possible lol)? Thank you! I will then cancel the smart test (in my opinion, it's very unlikely that it's due to the HDD) and follow the instructions.
  3. Hey, Today, unfortunately, I encountered the message "DEVICE IS DISABLED, CONTENTS EMULATED." It seems highly unlikely that the hard drive or the cable is at fault, as both are only about two months old. I've initiated an extended SMART test, but it looks like it will take over 30+ hours to complete for the hard drive. My assumption is that the hard drive was disabled due to a bug. However, I'm not certain, which is why I'm posting in this forum and not the report bugs one. In recent days, as I've been experimenting with OPNsense and VMs, I've frequently reseated my PCIe cards. Just yesterday, I moved a PCIe -> SATA card (http://tinyurl.com/2482fvxk), which only had the now-disabled hard drive connected, to a different PCIe slot. Additionally, I noticed that the card appeared under "Other PCI Devices:" in my Windows VM, with a checkmark next to it, even though I had never passed through the IOMMU group of the SATA controller. My suspicion is that the slot currently occupied by the PCIe -> SATA card was previously used by a NIC or USB PCIe card that was assigned to the VM. The diagnostic files attached were unfortunately captured after a restart, but idk, they might still be helpful. - What should my next steps be? - Should I cancel the test and start rebuilding? - Since the array had been started in the meantime, the data is definitely no longer synchronized. Do I need to create a new configuration under (Tools -> New Config), assign the hard drives as before, and then Unraid will rebuild the drive? Henrik unraidserver-diagnostics-20240214-1501.zip
  4. Thanks for all the answers. The new RAM sticks passed MemTest with three passes and have been working fine since then. I've also installed the AppData backup plugin, and it works really great. I set it up again yesterday with Btrfs, but if I encounter another problem, I will try ZFS. Now that I have a backup of everything, it's much less of a problem if something like this happens again. The only thing that was full at some point was the RAM; it was at 100% because of one Docker, and the whole server crashed. Maybe that caused it, I don't know. Apart from that, I have set a minimum free space as well. @itimpi Thanks, that's good to know!
  5. Oh, interesting. I had assumed that the moderators were part of the official Unraid support team and worked for Unraid. I'm not angry or anything! The solution was ultimately the right one, and everything important is working again. I was just a bit frustrated and wanted to give feedback. Additionally, it's quite different since you are doing it voluntarily. As I said, I am very grateful for the forum. Without it, I would have encountered problems more often.🤣 Yeah, I will let it run overnight; 64GB will probably take a few hours from what ive read online. I've never used MemTest before. Will look into it. I'm currently using LuckyBackup, but backing up all the small 50k+ files from Plex, for example, doesn't work very well. I have a few questions. You don't have to answer them directly. Feel free to send a link to an explanation or something similar. Im just not quite sure what to search for to get the answeres from google, haha: - What "exactly" was damaged? Was it a single file, a bit that was different from what it should have been? - Why did I have a significantly higher number of corrupted files when I accessed them via "/mnt/usr/appdata", but far fewer when I used the disk share directly? - How can such an error occur? What can I do differently or better to prevent this problem from happening again? - I've now encountered a problem with the btrfs filesystem for the second time. Is there a better alternative that also supports RAID 1? Maybe a bug report, I don't know: When I started the array today, it went straight into a parity check while (probably) the issue with the Btrfs cache pool existed. When I then accessed the interface, I could see that the CPU usage was pinned at 100%. After a few seconds, the server completely crashed. In the log, I could see that there was a "CPU Stall." The server could only be shut down by unplugging it. I was only able to break out of this loop when I spammed the cancel button for the parity check at the array start. Sorry for the wall of text. And again, thank you, I find it really remarkable that you do this voluntarily!
  6. Changed Status to Solved
  7. For everyone seeing this in the future: Accessing the cache pool as a disk share eliminated 95% of the "corrupted" files. I simply copied them to my PC, formatted the pool, and then copied them back onto the server. Everything seems to work now. ----- First of all, thank you for your help. I'm not sure if you moderators get paid or do this voluntarily, but either way, I really appreciate the support provided through this forum. A few weeks ago, you assisted me swiftly and effectively with a problem. However, I must admit that this time I was quite disappointed. When I reach out in this forum, I have a problem and expect to be communicating with experts who can guide me or offer direct assistance. Consequently, I trust what you say nearly 100%. For this reason, I find it really unfortunate that your only solution was to suggest copying the files, especially since I told you that many files were corrupted and you didn’t offer any alternative ideas, like using the disk share instead of the appdata share. If I hadn't tested it myself, I might have lost many files or caused further damage with the repair command. The idea of just copying everything is something I could have come up with on my own. Receiving advice on how to salvage the damaged files would have been much more helpful. Especially when it comes to data loss, I can’t comprehend why the responses are extremely short, sporadically and lack substantial solutions, as well as dos and don'ts to prevent further damage. Moreover, I don't appreciate that you simply marked the ticket as "closed." Whether it's in the right category or not is irrelevant to me at that moment. You're more than welcome to move it to the correct category or notify me about it! But closing the topic when it's obviously not resolved is, to put it mildly, really unacceptable. Despite this, I'm very grateful for the help from you and the forum in general.
  8. Is there no other option? Either I don't have the files, or I use this command without understanding what it does, which could potentially cause more harm. Neither option seems appealing.
  9. Yeah, I'm attempting to transfer the files to my PC, but it appears that many files are corrupted. I'm unable to copy or open them, although I can open the same file from a backup made yesterday. I have a backup for the crucial files, but not for my AppData folder, which somewhat important data like game save files, and all my configs. Can't I simply run this '--repair' command and have the filesystem repair itself? After all, it seems there's only one bad "sector" or whatever its called.
  10. Oh, sorry, I didn't know about the other forum; I'll note it down for future requests. Isn't there a way to just delete the corrupted file or fix it somehow else? Copying the appdata stuff takes ages. I thought having a redundant cache would protect me against drive or filesystem failures. Thx for your help!
  11. Hey, My SSD pool is somewhat broken and set itself to read only; please help. 😅 I changed my RAM today, and it worked fine afterward. However, I switched it back to the old RAM. Now, the server is in a state in which it has been working without any issues for days. The only thing I did today besides the RAM change was installing a Docker. Henrik unraidserver-diagnostics-20240130-1608.zip
  12. Installing the "RTL8125(B) PCI Driver" by jinlife did the trick; I'm now running on 6.12.6, and everything is working fine, even with jumbo frames. Thanks a lot for your help!
  13. Oh, that's really good to know, it worked. I'm back on .4 now. unraidserver-diagnostics-20240106-1201.zip
×
×
  • Create New...