Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Solved] 6.9b35 Trail - Spinning up a Win10 VM seem to kill parity disk

Featured Replies

I am still trailing Unraid 6.9b35 and after I managed to get couple of container and shares up and running I created a Win10 VM which seems to kill my parity disk.

 

Symptoms: I spin up the VM and use it to browse the web, suddenly the parity disk turns red, disabled and the sys log is full of errors. I wonder if my cache disk setup could case the issues. The VM is stored on the cache disk.

When I stop the array, remove the disk, add in again I can start a parity sync which has run for 3hrs with turbo write (constantly 182Mb/sec) without issues. Starting the VM again ended in the same result as described above.

 

System setup:

 

3x4 TB WD Red

2x 512GB SSD + 1x 250GB as Cache Pool Raid 1

 

Any advise how I can troubleshoot this? Diagnostics attached.

 

Thanks all!

 

 

ryzen-diagnostics-20201120-2201.zip

Edited by doesntaffect
issue so far solved

  • Community Expert

Diags are after rebooting with parity already disabled, re-sync it then grab diags after it gets disable and post those.

  • Author

I managed to copy parts of the sys log.

Moved the VM from Cache to HDD and so far no issues. Didn't test with a new VM on the SSD cache yet as I am afraid this will trouble the parity disk again.

 

Any further advise?

Nov 20 08:30:31 Ryzen kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0
Nov 20 08:30:34 Ryzen kernel: blk_update_request: I/O error, dev loop2, sector 149152 op 0x1:(WRITE) flags 0x1800 phys_seg 3 prio class 0
Nov 20 08:30:34 Ryzen kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0
Nov 20 08:30:34 Ryzen kernel: blk_update_request: I/O error, dev loop2, sector 153248 op 0x1:(WRITE) flags 0x1800 phys_seg 35 prio class 0
Nov 20 08:30:34 Ryzen kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0
Nov 20 08:30:34 Ryzen kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0
Nov 20 08:30:34 Ryzen kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 6, rd 0, flush 0, corrupt 0, gen 0
Nov 20 08:30:34 Ryzen kernel: blk_update_request: I/O error, dev loop2, sector 673440 op 0x1:(WRITE) flags 0x1800 phys_seg 3 prio class 0
Nov 20 08:30:34 Ryzen kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0
Nov 20 08:30:34 Ryzen kernel: blk_update_request: I/O error, dev loop2, sector 677536 op 0x1:(WRITE) flags 0x1800 phys_seg 35 prio class 0
Nov 20 08:30:34 Ryzen kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 8, rd 0, flush 0, corrupt 0, gen 0
Nov 20 08:30:34 Ryzen kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 9, rd 0, flush 0, corrupt 0, gen 0
Nov 20 08:30:34 Ryzen kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 10, rd 0, flush 0, corrupt 0, gen 0
Nov 20 08:30:34 Ryzen kernel: blk_update_request: I/O error, dev loop2, sector 156928 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0
Nov 20 08:30:34 Ryzen kernel: blk_update_request: I/O error, dev loop2, sector 681216 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0
Nov 20 08:30:34 Ryzen kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2327: errno=-5 IO failure (Error while writing out transaction)
Nov 20 08:30:34 Ryzen kernel: BTRFS info (device loop2): forced readonly
Nov 20 08:30:34 Ryzen kernel: BTRFS warning (device loop2): Skipping commit of aborted transaction.
Nov 20 08:30:34 Ryzen kernel: BTRFS: error (device loop2) in cleanup_transaction:1898: errno=-5 IO failure
Nov 20 08:30:40 Ryzen smbd[24055]: [2020/11/20 08:30:40.654245, 0] ../../source3/smbd/service.c:850(make_connection_snum)
Nov 20 08:30:40 Ryzen smbd[24055]: make_connection_snum: '/mnt/user/isos' does not exist or permission denied when connecting to [isos] Error was Input/output error
Nov 20 08:30:40 Ryzen smbd[24055]: [2020/11/20 08:30:40.655062, 0] ../../source3/smbd/service.c:850(make_connection_snum)
Nov 20 08:30:40 Ryzen smbd[24055]: make_connection_snum: '/mnt/user/isos' does not exist or permission denied when connecting to [isos] Error was Input/output error
Nov 20 08:30:40 Ryzen smbd[24055]: [2020/11/20 08:30:40.655821, 0] ../../source3/smbd/service.c:850(make_connection_snum)
Nov 20 08:30:40 Ryzen smbd[24055]: make_connection_snum: '/mnt/user/isos' does not exist or permission denied when connecting to [isos] Error was Input/output error

 

  • Community Expert

Not enough info, those errors are likely about the docker image, we'd need to see the beginning of the problem.

@doesntaffect What devices are you passing through to the VM? Any USB devices, controllers or disks? A complete diagnostic would be helpful

  • Author

So far the system has been stable for a couple of days after I changed my Cache config from 3 NVMEs (2x512+1x250; the latter in a PCIe 1x converter card) to just 2x512GB. The single NVME has been turned into a separate cache, obviously without any Raid config.

The Win10 VM is behaving fine, even with heavy load on the host and the VM over a couple of days. I'll mark this as solved since I cannot provide a copy of the original diagnostics.

 

Thanks guys!

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.