nanouke

I finally find out where the right documentation was. Got my automatic flash back up downloaded and reinstall on a new (temporary) flash. This is my first time doing this, I will see if I discover new issue after this. Thanks for the help.

I want to make sure if I reboot and the usb still corrupted do I will be able to access my files again. Shoud I run backup before rebooting.

Hello everyone, I login to my unraid today and got surprise by a message saying : Cannot access your USB Flash boot device. Right now everything looks like working properly because the os is running from the RAM I guess. I want to know if they are anything I can do at this point. I cannot create a flash backup. I was on the impression the unraid connect was doing those backup automatically but I did not find where those backups are. What is the best thing I can do for now on. I will like to keep the data at worst. installation-00-diagnostics-20240223-1125.zip

I never think about it because it was working on my old PC but I already see errors from the test so I guess I will need to shop for RAM now. Do ECC memory will help mitigate those issue or regular is fine just need to test them before using it? Thanks for your help I am learning every day,

Hello everyone, I know this is not a new subject I did see a similar issue on the forum but I am really not an expert btrfs and cache corruption, I want to correct the issue, the right way. I recently update my server with my personal old PC I change the motherboard, CPU, RAM. When I boot the machine, I did have some issue with the cache drive it was corrupted. At that time I got the impression the SSD was just dead because it was a cheap WD did have an issue with WD SSD before so I decided to replace the only cache drive by 2 Crucial nvme SSD to add parity. After a few days did start having issues with the docker btfs image some corruption. I rebuild it... fine for a few days. Now I have an error on the cache pool : Jun 15 20:59:12 INSTALLATION-00 kernel: BTRFS error (device nvme0n1p1): block=178208145408 write time tree block corruption detected Jun 15 20:59:12 INSTALLATION-00 kernel: BTRFS: error (device nvme0n1p1) in btrfs_commit_transaction:2460: errno=-5 IO failure (Error while writing out transaction) Jun 15 20:59:12 INSTALLATION-00 kernel: BTRFS: error (device nvme0n1p1: state EA) in cleanup_transaction:1958: errno=-5 IO failure Jun 15 20:59:13 INSTALLATION-00 kernel: loop: Write error at byte offset 433504256, length 4096. Jun 15 20:59:13 INSTALLATION-00 kernel: loop: Write error at byte offset 165068800, length 4096. Jun 15 20:59:13 INSTALLATION-00 kernel: loop: Write error at byte offset 433487872, length 4096. Jun 15 20:59:13 INSTALLATION-00 kernel: loop: Write error at byte offset 165052416, length 4096. Jun 15 20:59:13 INSTALLATION-00 kernel: I/O error, dev loop2, sector 846688 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Jun 15 20:59:13 INSTALLATION-00 kernel: I/O error, dev loop2, sector 322400 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Jun 15 20:59:13 INSTALLATION-00 kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 2, gen 0 Jun 15 20:59:13 INSTALLATION-00 kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 0, corrupt 2, gen 0 Jun 15 20:59:13 INSTALLATION-00 kernel: I/O error, dev loop2, sector 846656 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Jun 15 20:59:13 INSTALLATION-00 kernel: I/O error, dev loop2, sector 322368 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Jun 15 20:59:13 INSTALLATION-00 kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 2, gen 0 Jun 15 20:59:13 INSTALLATION-00 kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 0, flush 0, corrupt 2, gen 0 Jun 15 20:59:13 INSTALLATION-00 kernel: loop: Write error at byte offset 163217408, length 4096. Jun 15 20:59:13 INSTALLATION-00 kernel: loop: Write error at byte offset 431652864, length 4096. Jun 15 20:59:13 INSTALLATION-00 kernel: loop: Write error at byte offset 163315712, length 4096. Jun 15 20:59:13 INSTALLATION-00 kernel: I/O error, dev loop2, sector 318784 op 0x1:(WRITE) flags 0x1800 phys_seg 11 prio class 2 Jun 15 20:59:13 INSTALLATION-00 kernel: loop: Write error at byte offset 431751168, length 4096. Jun 15 20:59:13 INSTALLATION-00 kernel: loop: Write error at byte offset 163397632, length 4096. Jun 15 20:59:13 INSTALLATION-00 kernel: loop: Write error at byte offset 431833088, length 4096. Jun 15 20:59:13 INSTALLATION-00 kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 5, rd 0, flush 0, corrupt 2, gen 0 Jun 15 20:59:13 INSTALLATION-00 kernel: I/O error, dev loop2, sector 843072 op 0x1:(WRITE) flags 0x1800 phys_seg 11 prio class 2 Jun 15 20:59:13 INSTALLATION-00 kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 6, rd 0, flush 0, corrupt 2, gen 0 Jun 15 20:59:13 INSTALLATION-00 kernel: I/O error, dev loop2, sector 318976 op 0x1:(WRITE) flags 0x1800 phys_seg 12 prio class 2 Jun 15 20:59:13 INSTALLATION-00 kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 7, rd 0, flush 0, corrupt 2, gen 0 Jun 15 20:59:13 INSTALLATION-00 kernel: I/O error, dev loop2, sector 843264 op 0x1:(WRITE) flags 0x1800 phys_seg 12 prio class 2 Jun 15 20:59:13 INSTALLATION-00 kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 8, rd 0, flush 0, corrupt 2, gen 0 Jun 15 20:59:13 INSTALLATION-00 kernel: I/O error, dev loop2, sector 319136 op 0x1:(WRITE) flags 0x1800 phys_seg 20 prio class 2 Jun 15 20:59:13 INSTALLATION-00 kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 9, rd 0, flush 0, corrupt 2, gen 0 Jun 15 20:59:13 INSTALLATION-00 kernel: I/O error, dev loop2, sector 843424 op 0x1:(WRITE) flags 0x1800 phys_seg 20 prio class 2 Jun 15 20:59:13 INSTALLATION-00 kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 10, rd 0, flush 0, corrupt 2, gen 0 Jun 15 20:59:13 INSTALLATION-00 kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2460: errno=-5 IO failure (Error while writing out transaction) Jun 15 20:59:13 INSTALLATION-00 kernel: BTRFS: error (device loop2: state EA) in cleanup_transaction:1958: errno=-5 IO failure I know I can just rebuild the cache drive and it will probably work for 2 or 3 weeks before doing it again I am trying to find the root cause of this problem so I can fix it for good. Also not sure if this is related but when I did the updated to 6.12 those errors appear: Jun 15 10:50:36 INSTALLATION-00 root: moving obsolete plugin gpustat.plg version 2022.11.30a to /boot/config/plugins-error Jun 15 11:02:07 INSTALLATION-00 root: Fix Common Problems: Error: Multiple NICs on the same IPv4 network ** Ignored Jun 15 11:57:36 INSTALLATION-00 kernel: CPU: 12 PID: 1239 Comm: kworker/u64:8 Tainted: P O 6.1.33-Unraid #1 Jun 15 11:57:36 INSTALLATION-00 kernel: Call Trace: Jun 15 14:02:45 INSTALLATION-00 kernel: CPU: 3 PID: 2199 Comm: smartctl_type Tainted: P W O 6.1.33-Unraid #1 Jun 15 14:02:45 INSTALLATION-00 kernel: Call Trace: Jun 15 14:02:45 INSTALLATION-00 kernel: CPU: 3 PID: 2199 Comm: smartctl_type Tainted: P B W O 6.1.33-Unraid #1 Jun 15 14:02:45 INSTALLATION-00 kernel: Call Trace: Jun 15 14:03:46 INSTALLATION-00 kernel: CPU: 22 PID: 2987 Comm: smartctl_type Tainted: P B W O 6.1.33-Unraid #1 Jun 15 14:03:46 INSTALLATION-00 kernel: Call Trace: Let me know if you need more information I am open to any solution. Thank everyone, installation-00-diagnostics-20230616-0742.zip

I have the same issue, still looking how I can have access to shinobi form other PC on my LAN. I am able to ping the IP but not able to access the webUI. I know the webUI is working because if I curl shinobi from the server I am able to see html. I f some one has any idea it will be great thanks. PS: I try to add a vlan in windows 10, so I created a new vlan adapter with the same vlan that shinobi and got the same issue. If I curl from windows, I got connection refused.

Changed Status to Open Changed Priority to Minor

Why, currently my server is behind a firewall (then it is no longer accessible from outside) and it is not usable because of the bug. So I do not see the importance of securing it. I do not even know if the problem will persist.

Finally, I think it's related to the NFS bug. I'm going to open a post in the bug section. Thank you for your help and I promise to secure my server once the bug is fixed.

I hope that is not the case. I'll confirm that tomorrow. On the other hand, it looks a lot like my problem. If it's the same problem, I do not know how I'm going to fix it. Thanks for your help.

For now, I will stay in local and I restarted the server. I do not know if this will solve the problem of the shares folder, but it will not hurt. I'll have to wait until tomorrow, see if the problem comes back. Thank you for pointing out the security problem. Usually it is not my style to neglect this type of problem, but being novice in Unraid I got excited about the things I could do, neglecting safety.

Yes, my server is exposed on the web in a DMZ. Strangely, I often connect to a VPN in Netherlands, but I never connect to my server from this network interface. I will cut off access immediately.

Here are my diagnostic files. I specify that the WebUi works perfectly. tower-diagnostics-20181106-1901.zip

Hello everyone, I have a problem with the share. After a while, my shares are no longer visible on the WebUi and I can not access them from Windows. If I restart the server, everything returns to normal. I do not know if it's related to updates. If not the only thing that has changed on my server is adding a Melanox Connectx II card. I do not know where to start if someone had an idea that would be appreciated. Thank you for your answers Unraid version : 6.6.3