Baskedk

Thanks for taking the time to look at the issue for me I will re-create the docker-file tonight 👍 Are you referring to any specific memtest? I am not aware of any memtest inside unraid? BR Baskedk

Hi everyone I have got a problem that I thought was a one-off a few days ago, where some of my containers was not responding anymore. I then went and looked at the docker section in unRAID where I was presented with "Docker service failed to start" I then rebooted the server and everything was fine again. But now, 3 days later, it happened again. I attached the diagnostics logs from unraid for any knowledgeable person to jump around in I would very much appreciate if anyone could help me find the root cause of this. Some containers are still running. I can access the server from Zerotier even after that message comes up. So docker is not completely dead. bytestacker-diagnostics-20231009-0803.zip

Hi community I have a kind of potentially massive issue..... I found out yesterday that one of my disks had been disabled due to errors, or something like that. I then (half an hour ago) replaced the disk with another one I had lying around. I made a clean shutdown, and replaced the disk while unpowered, booted up again, and assigned the disk (Disk 1) with the new disk and parity started building. I then after 10 minutes get a notification that the disks is experiencing massive error counts (See screenshot diskerrors.png) The disk 1 seems to be rebuilding, but what do I do with all these errors? Pasted the diagnostics as well. Hope someone out there will take a little time to help out I'm no expert, but that error count seems unhealthy..... jinx-diagnostics-20220401-1617.zip

I'm also running an asus one atm. Prime B450 I think. Cant remember the exact model in my head, but I think that's the one. I've actually never had issues with AsRock boards before and I've had quite a lot of them, so I might take your advice on that. This was my first Asus board, and I'm not thrilled about my experience. Does anyone in this thread know what to stay away from regarding these disk issues on AMD systems? Is it a chipset problem, manufacturer problem or completely random?

May I ask what board you switched to? I'm Running a 3700x with similar issues. And it's getting old to maneuver in the failed disks all the time. Would like a reliable system. I only have problems with the disks running on my board-connected disks. Disks via controller card is working flawlessly. Thanks in advance Baskedk

That can't be done unfortunately. You can not run a hypervisor i site another hypervisor. So if you want to use Synology virtual manager you'll have to install xpenology directly on to the metal. And make sure that your hardware supports virtualization.

No need to have a certificate to run sftp on the DSM. And yes, you can change the port DSM uses for sftp inside the settings there. I can't see why not you could do the entire setup remotely. It should only be for adding disks to the setup as i see it. As for which bootloader version to use, it varies a bit for people what works. I believe I've used the setup @bmac6996 provided the details for on page 3 in this threat here. As for how to get going, there is a well documented tutorial from the XPEnology forums here: https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ And here is the serial generator for it as well: https://xpenogen.github.io/serial_generator/ Just make sure you don't use any of the Synology Quickconnect features with xpenology, since it is the one thing that directly communicates with synology's servers. If you need remote access to your instance, forward ports to it 😉

Just to follow up on my issue, it seems that the beta update stopped my disk errors. My log is not flooded with errors anymore, and every thing seems to be in order. Glad i didn't move to ryzen earlier, when that option was not around 👍 Thanks @JorgeB for pointing me in the right direction 😎

Ahh, you meant the unRAID OS beta, and not a beta bios 🙄 I'll try that out and see if the kernel makes the difference 👍

thx, i'll give it a watch 👍

I don't even know what IOMMU is, so I have no idea if I need it hehe. I can not seem to find a newer version of my bios. And no beta versions at all. It's a 'Asus Prime B450M-A'. But if all this nonsense is sata controller related, can anyone recommend a good reliable AM4 motherboard to use for unRAID then? My life is to short for these kind of random data failures all the time. And if this can be solved with another mobo, that's my goto.

A reboot of the server, got everything working again. At least it looks like it for now. Still very curious on what could cause this. If it can happen out of the blue like that, it can happen again...... And that kind of stability is not something I'm a big fan of.

Hey everyone. Last night my unraid server got all crazy on me and decided to do read errors and mess with my dockers and VMs. I have no idea where to start on figuring out what caused this. And my cache is apparently full of BTRFS errors: Oct 13 07:39:02 Jinx kernel: print_req_error: I/O error, dev sdb, sector 5663456 Oct 13 07:39:02 Jinx kernel: BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 350, rd 905675, flush 0, corrupt 0, gen 0 Anyone got the knowledge and time to look through my diagnostics and figure out what the root problem to this is, it would be greatly appreciated. Here is a few visual representations of the problem from the gui Array: Docker: VMs I had 5-6 VMs yesterday.... I kind off regret that I switched to Ryzen. Have had so many problems with the system since I switched over. Anyone knows if this could be related. Is there compatibility problems on the AMD side? Thanks in advance lovely community. Best Regards Baskedk jinx-diagnostics-20201013-0728.zip

I've run XPEnology for 2+ years with passed through whole disks done i the same way you would pass a full disk to any other VM in unRAID without any issue what so ever. If you are in doubt about how to pass a full disk to a VM, see "spaceinvaderone's" exelent video on the topic. But when it is passed into the VM, you would just format it in the synology DSM software like if it was a standalone box. Hope this helps you going 😉

I don't know why it got disabled in the first place, but what you told me to do got the parity rebuild and is functional again, so thanks for that 💪👍 I will post here again if the problem returns. But for know, everything is great 👌🍻 Cheers

Aight, I'll do a new check and report back. The check is not called "Parity Check" anymore though. It's just a "Read-Check" Guess that's because the parity disk is disabled, but does it still do a check towards the parity? Is this test even doing anything useful if the parity disk is not active?

I just woke up this morning to a partly shut down unraid system. Last night my parity check started as it does every week. But when I woke up, all VMs and docker containers were offline, the dashboard could'n be shown and the parity disk was shown as disabled due to errors. The SMART stats on the disk says nothing about errors, and the system recognizes the disk after a reboot etc. But i can not get the status from disabled back to normal. What can cause this issue? Do I need to replace the drive? It's a "fairly new" drive which only have a year ontime. And it replaced a faulty parity disk that died from me two weeks ago. Here is a few screenshots for info: Crossing my fingers that we have some smart people out there that can help me get my data safe again...... Not really liking the idea that I have no redundancy atm..... Thx in advance Baskedk jinx-diagnostics-20200924-0716.zip

That did the trick, thanks 👍

Alright. Here you are. I actually resized the docker image about a week ago. Is that not a thing you should do? jinx-diagnostics-20200610-1847.zip

I noticed that a service i was running via docker was unresponsive and logged in to the unRAID instance to see that the CPU was all over the place and was running quite hot due to the CPU stressing. I then opened the log to see that my SSD was failing big time. Was getting the following: Jun 10 15:16:10 Jinx kernel: print_req_error: I/O error, dev loop2, sector 4475240 Jun 10 15:16:10 Jinx kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 180, rd 0, flush 0, corrupt 0, gen 0 Jun 10 15:16:40 Jinx kernel: loop: Write error at byte offset 2291322880, length 4096. Jun 10 15:16:40 Jinx kernel: print_req_error: I/O error, dev loop2, sector 4475240 Jun 10 15:16:40 Jinx kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 181, rd 0, flush 0, corrupt 0, gen 0 Jun 10 15:17:11 Jinx kernel: loop: Write error at byte offset 2291322880, length 4096. Jun 10 15:17:11 Jinx kernel: print_req_error: I/O error, dev loop2, sector 4475240 Jun 10 15:17:11 Jinx kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 182, rd 0, flush 0, corrupt 0, gen 0 Jun 10 15:17:42 Jinx kernel: loop: Write error at byte offset 2291322880, length 4096. Jun 10 15:17:42 Jinx kernel: print_req_error: I/O error, dev loop2, sector 4475240 Jun 10 15:17:42 Jinx kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 183, rd 0, flush 0, corrupt 0, gen 0 Jun 10 15:18:12 Jinx kernel: loop: Write error at byte offset 2291322880, length 4096. Jun 10 15:18:12 Jinx kernel: print_req_error: I/O error, dev loop2, sector 4475240 Jun 10 15:18:12 Jinx kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 184, rd 0, flush 0, corrupt 0, gen 0 Jun 10 15:18:43 Jinx kernel: loop: Write error at byte offset 2291322880, length 4096. Jun 10 15:18:43 Jinx kernel: print_req_error: I/O error, dev loop2, sector 4475240 Jun 10 15:18:43 Jinx kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 185, rd 0, flush 0, corrupt 0, gen 0 Jun 10 15:19:14 Jinx kernel: loop: Write error at byte offset 2291322880, length 4096. Jun 10 15:19:14 Jinx kernel: print_req_error: I/O error, dev loop2, sector 4475240 Jun 10 15:19:14 Jinx kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 186, rd 0, flush 0, corrupt 0, gen 0 Jun 10 15:19:45 Jinx kernel: loop: Write error at byte offset 2291322880, length 4096. Jun 10 15:19:45 Jinx kernel: print_req_error: I/O error, dev loop2, sector 4475240 Jun 10 15:19:45 Jinx kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 187, rd 0, flush 0, corrupt 0, gen 0 Jun 10 15:20:15 Jinx kernel: loop: Write error at byte offset 2291322880, length 4096. Jun 10 15:20:15 Jinx kernel: print_req_error: I/O error, dev loop2, sector 4475240 Jun 10 15:20:15 Jinx kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 188, rd 0, flush 0, corrupt 0, gen 0 Jun 10 15:20:46 Jinx kernel: loop: Write error at byte offset 2291322880, length 4096. Jun 10 15:20:46 Jinx kernel: print_req_error: I/O error, dev loop2, sector 4475240 Jun 10 15:20:46 Jinx kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 189, rd 0, flush 0, corrupt 0, gen 0 Jun 10 15:21:17 Jinx kernel: loop: Write error at byte offset 2291322880, length 4096. Jun 10 15:21:17 Jinx kernel: print_req_error: I/O error, dev loop2, sector 4475240 Jun 10 15:21:17 Jinx kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 190, rd 0, flush 0, corrupt 0, gen 0 Jun 10 15:21:48 Jinx kernel: loop: Write error at byte offset 2291322880, length 4096. Jun 10 15:21:48 Jinx kernel: print_req_error: I/O error, dev loop2, sector 4475240 Jun 10 15:21:48 Jinx kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 191, rd 0, flush 0, corrupt 0, gen 0 Jun 10 15:22:18 Jinx kernel: loop: Write error at byte offset 2291322880, length 4096. Jun 10 15:22:18 Jinx kernel: print_req_error: I/O error, dev loop2, sector 4475240 Jun 10 15:22:18 Jinx kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 192, rd 0, flush 0, corrupt 0, gen 0 Jun 10 15:22:49 Jinx kernel: loop: Write error at byte offset 2291322880, length 4096. Jun 10 15:22:49 Jinx kernel: print_req_error: I/O error, dev loop2, sector 4475240 Jun 10 15:22:49 Jinx kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 193, rd 0, flush 0, corrupt 0, gen 0 What can i do to combat this. Do I have to replace the disk? Is it only software related, so that a format could get me running again? And if i turn off docker and virtualization and reboot the device, could I maybe get the data off the drive ..... Thx in advance....

Just did the same as above on a i7-3770 on a ASRock Z77 Pro4-M today, and following the same procedure I got the same result. Works flawlessly. Thx again for the pointer. I don't know why it says it's an i3-4130, but it works, and that's what matters

Did the above and can confirm that it works. For me at least. I too am rocking af supermicro. My board is a X9DAL though with dual E5-2418L Xeons I've been trying before without luck. Not with the newest version though. But it is the first time i've tried to set the NIC as "e1000e" and not just "e1000". If that made the differance or not, I don't know. But if works now for sure. Thanks for the pointer

I did create the disk 1st. And i have the system running now on loader 1.03b, I just could'n get it to discover the disk on the 1.04b loader. It booted and all. It just did'n discover the 2nd disk somehow. But as said, on the 1.03b it works fine. I guess it might come down to what hardware ppl are using i guess. unRAID is unraid, but XPEnology can be quite picky on hardware, and maybe that is what screws ppl over in this setup. What works for some, might not work for others. But when it comes to accessing unRAID resources from within DSM you can set up NFS/CIFS shares on unRAID and setup remote folder sharing in FileStation and add the shares there. And then you have a bridge between the two systems. It's not paticular fast transfer rates, but it works. It is a virtual environment after all.

Nope. I've replicated everything you have in your XML to the extend possible. Still no luck. Could you maybe upload your synoboot.img file for me to DL? without the MAC ofc. Btw, for the ds918+, where do you get a serial for that? I can only find a generator for ds3615xs, ds3617xs and ds916+. Not ds918+ Is it not needed for that one? Or how does that work? And why do you need to have 2 extra hdd's in your setup? Why not just the boot disk (synoboot.img) and a storage disk? Just curious

I assume you are reffering to ds918+ since I can't seem to find a 1.04b loader for 916+ but there is one for 918+. But i can't even get this one to show up on the network. What have you done for it to be discovered on the network? NIC interface e1000 ? What bios? Seabios or OMVF?, Machine: Q35-2.9? What is your settings?