CvH

Members
  • Posts

    10
  • Joined

  • Last visited

Everything posted by CvH

  1. yea but if I try that it complains that the disc is too small because there are already partitions or something on it - rebuild doesn't work then Oh thats read a bit different to the other docs ... not sure why there is a very incomplete doc online at the official Unraid site that is google search hit number one. Who expects that incomplete docs are presented at the main unraid site. Normally I would would expect that you don't need such docs, but in unraids case the devs decided to make the rebuild function not bullet proof - so additionally your data depends on it which doc you actually read .... Sorry if this reads like a rant, but I really didn't thought that the rebuild process at unraid is so shaky and user-unfriendly designed The two different docs are just the icing on the cake, really.
  2. A disc died and I tried to rebuild the data with help of a used spare disc that was around. The "new" disc had already partitions and some old data on it (not related to the nas). So I followed https://wiki.unraid.net/Replacing_a_Data_Drive and at the "Assign the new drive in the slot of the old drive" it complained that the disc is too small. So I wiped the new disc with sgdisk --zap-all /dev/sdX Afterwards, if I remember correctly, it formatted the new disc. I was able to use it with the unassigned plugin. So afterwards I was able to add it at the "Assign the new drive in the slot of the old drive" step. Likewise it showed the popup that I "ignored" because I did not formatted any disc and was not aware that I format anything unmountable. So I ended up with a empty disc with complete data loss, realised it a week later so my memory is a bit fuzzy. I google a bit what could gone wrong and immediately found that this is a common Unraid problem (seriously wtf). At the next disc fail I would likely do it similar again. I did in the past at several different NAS vendors (Synology, Qnap, some HW Raid) and never had a problem because the way to do it was crystal clear and self explained. So what is the correct way if it complains for some reason like disc to small due old data on it? That is not covered by the docs and acting with common sense leads to data loss. Tbh I did not expect that Unraid tries to delete my files so I gave it not too much attention because I expected it just works like at all other NAS Software I used in the past.
  3. I fixed it in the meantime, as soon I do dual channel RAM the NVME goes south (even at Windows). At windows I needed to create some load at the cpu (prime95) and start a disk benchmark, then I got reproduce able crashes in under 20sec. After some trial and error It worked as soon I siwtched the ram modules, dualchannel is not working at all -> reproduce able crashes at windows. After switching the ram modules to single mode it worked perfectly. It is likely a board issue.
  4. tx, with this fix I was able to make passthrough work my AMD R9 280X, even used as primary GPU without any additional GPU in my system
  5. tower-diagnostics-20210120-2152_anonym.zip If anything else is needed just ask.
  6. Hi, I get a kernel crash if I use my NVME cache and write data on it. dmesg, crash not included https://pastebin.com/D9huGDF4 Nothing happens if I copy just ~5gb on it, everything is fine. As soon I copy more stuff on it crashs reproduceable after 10-30min (regardless if I use it as cache or directly copy onto it). After it crashs (hard freeze of the system) I need to reboot and then it crashs much faster ~2-5min). Temps are okay ~40°C and even with a DIY cooler directly on top nothing changes. Can't grep a complete log because ssh dies too and no output happens. What I tested so far and everything resulted in the same: - RAM was tested with https://www.memtest86.com/ for a day and was okay. - Nvme was replaced by an completely different one (different size and manufacture). - Tried copy over network and local. - Bios Update restore to stock settings etc. - VM on or off doesn't matter. - Complete reinstall with minimal config same result. If I am not using the nvme cache everything is super stable and perfectly useable. Same system at windows (did a test install to verify) has no problems with the nvme. If anyone has a good idea what I may test or what log I need to provide pls ask (I am familiar with linux).