Jump to content

golli53

Members
  • Content Count

    36
  • Joined

Community Reputation

2 Neutral

About golli53

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. I also think these two are related. Experiencing both on 6.7.2
  2. Does anyone have a sense whether 6.8 will fix this? I am considering downgrading to 6.6.7 as everything freezes during mover (I moved a bunch of mission critical services to an older PC for now), but I started off on 6.7.x, so I would need to downgrade manually and am afraid I'll break something eg plugins/settings.
  3. Do these snapshots work when passing through a GPU? I ask because virsh save doesn't work when this is the case.
  4. Wrote this after a potential nightmare when mounting a cache drive with an extra empty slot erased my LUKS header Run in ssh from whichever directory you want to store the headers. Will be automatically named with model and serial numbers. Finishes in a few seconds for i in {/dev/sd*,/dev/nvme*}; do if cryptsetup luksDump $i &>/dev/null; then dd if=$i of=`udevadm info --query=all --name=$i | sed -n 's/.*ID_SERIAL=//p'`.img bs=512 count=4096; fi; done
  5. I hope the 6.8 changes won't break the ability to GUI mount an encrypted drive (with or without retyping pass) using Unassigned Devices after array start
  6. The ssd2 is from running: /usr/sbin/cryptsetup luksOpen /dev/nvme1n1p1 ssd2 --allow-discards --key-file /root/keyfile
  7. Got it - is the error above when trying degraded mode ("wrong fs type, bad option, bad superblock on /dev/mapper/ssd2, missing codepage or helper program, or other error.") due to the bug that you referenced? Mounting as a pool unfortunately hangs forever
  8. Oh shoot - I didn't see this bug. I do think it was created 6.7+. On second reboot, the bad drive (nvme0n1, ssd) re-appeared in unRAID, but can't mount the pool (hangs). Then tried mounting with degraded using the good drive (nvme1n1, ssd2) - see below. Am I toast? login as: root Linux 4.19.56-Unraid. root@Tower:~# /usr/sbin/cryptsetup luksOpen /dev/nvme1n1p1 ssd2 --allow-discards --key-file /root/keyfile root@Tower:~# mkdir /mnt/disks/ssd root@Tower:~# /sbin/mount -o usebackuproot,ro '/dev/mapper/ssd' '/mnt/disks/ssd' ^C root@Tower:~# /sbin/mount -o degraded,usebackuproot,ro '/dev/mapper/ssd2' '/mnt/disks/ssd' mount: /mnt/disks/ssd: wrong fs type, bad option, bad superblock on /dev/mapper/ssd2, missing codepage or helper program, or other error.
  9. Thanks- I rebooted and the drive no longer shows up under Unassigned Devices. I guess the drive (or mobo controller) failed. What would you recommend as the safest way to recover the data from the other (hopefully) still good drive in the RAID1 btrfs array?
  10. These NVME drives were mounted as unassigned devices in RAID1 and were running my Win10 VMs. Not sure whether this was due to a hardware or filesystem issue. The directory on the drive that contained my VMs (that were running at the time and crashed after the errors) shows up as empty now (all VM images missing). Not sure whether it is s afe to disconnect/reconnect the drives or best way to proceed. Would appreciate any advice. [edit] I forced stopped my VM and disabled virtualization in the GUI - I don't know if this caused my VM images to go missing on disk. My highest priority is recovering these images Sep 5 14:33:22 Tower kernel: nvme nvme0: I/O 408 QID 9 timeout, aborting Sep 5 14:33:23 Tower kernel: nvme nvme0: I/O 409 QID 9 timeout, aborting Sep 5 14:33:23 Tower kernel: nvme nvme0: I/O 410 QID 9 timeout, aborting Sep 5 14:33:23 Tower kernel: nvme nvme0: I/O 411 QID 9 timeout, aborting Sep 5 14:33:23 Tower kernel: nvme nvme0: I/O 737 QID 7 timeout, aborting Sep 5 14:33:23 Tower kernel: nvme nvme0: I/O 738 QID 7 timeout, aborting Sep 5 14:33:23 Tower kernel: nvme nvme0: I/O 739 QID 7 timeout, aborting Sep 5 14:33:23 Tower kernel: nvme nvme0: I/O 198 QID 8 timeout, aborting Sep 5 14:33:52 Tower kernel: nvme nvme0: I/O 408 QID 9 timeout, reset controller Sep 5 14:34:23 Tower kernel: nvme nvme0: I/O 11 QID 0 timeout, reset controller Sep 5 14:35:23 Tower kernel: nvme nvme0: Device not ready; aborting reset Sep 5 14:35:23 Tower kernel: nvme nvme0: Abort status: 0x7 Sep 5 14:35:23 Tower kernel: nvme nvme0: Abort status: 0x7 Sep 5 14:35:23 Tower kernel: nvme nvme0: Abort status: 0x7 Sep 5 14:35:23 Tower kernel: nvme nvme0: Abort status: 0x7 Sep 5 14:35:23 Tower kernel: nvme nvme0: Abort status: 0x7 Sep 5 14:35:23 Tower kernel: nvme nvme0: Abort status: 0x7 Sep 5 14:35:23 Tower kernel: nvme nvme0: Abort status: 0x7 Sep 5 14:35:23 Tower kernel: nvme nvme0: Abort status: 0x7 Sep 5 14:35:42 Tower dhcpcd[2016]: br0: failed to renew DHCP, rebinding Sep 5 14:35:42 Tower dhcpcd[2016]: br0: truncated packet (180) from 192.168.10.10 Sep 5 14:35:42 Tower dhcpcd[2016]: br0: truncated packet (180) from 192.168.10.10 Sep 5 14:35:42 Tower dhcpcd[2016]: br0: truncated packet (152) from 192.168.10.10 Sep 5 14:35:42 Tower dhcpcd[2016]: br0: truncated packet (152) from 192.168.10.10 Sep 5 14:35:42 Tower dhcpcd[2016]: br0: truncated packet (132) from 192.168.10.12 Sep 5 14:35:42 Tower dhcpcd[2016]: br0: truncated packet (132) from 192.168.10.12 Sep 5 14:35:42 Tower dhcpcd[2016]: br0: truncated packet (24) from 192.168.10.12 Sep 5 14:35:42 Tower dhcpcd[2016]: br0: truncated packet (24) from 192.168.10.12 Sep 5 14:35:54 Tower kernel: nvme nvme0: Device not ready; aborting reset Sep 5 14:35:54 Tower kernel: nvme nvme0: Removing after probe failure status: -19 Sep 5 14:36:24 Tower kernel: nvme nvme0: Device not ready; aborting reset Sep 5 14:36:24 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Sep 5 14:36:24 Tower kernel: print_req_error: I/O error, dev nvme0n1, sector 1419705920 Sep 5 14:36:24 Tower kernel: print_req_error: I/O error, dev nvme0n1, sector 1426329664 Sep 5 14:36:24 Tower kernel: print_req_error: I/O error, dev nvme0n1, sector 1313322472 Sep 5 14:36:24 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 Sep 5 14:36:24 Tower kernel: print_req_error: I/O error, dev nvme0n1, sector 726592960 Sep 5 14:36:24 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 4, rd 0, flush 0, corrupt 0, gen 0 Sep 5 14:36:24 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 5, rd 0, flush 0, corrupt 0, gen 0 Sep 5 14:36:24 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 6, rd 0, flush 0, corrupt 0, gen 0 Sep 5 14:36:24 Tower kernel: print_req_error: I/O error, dev nvme0n1, sector 1416326976 Sep 5 14:36:24 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 7, rd 0, flush 0, corrupt 0, gen 0 Sep 5 14:36:24 Tower kernel: print_req_error: I/O error, dev nvme0n1, sector 1426329600 Sep 5 14:36:24 Tower kernel: print_req_error: I/O error, dev nvme0n1, sector 1385254080 Sep 5 14:36:24 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 9, rd 0, flush 0, corrupt 0, gen 0 Sep 5 14:36:24 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 9, rd 0, flush 0, corrupt 0, gen 0 Sep 5 14:36:24 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 10, rd 0, flush 0, corrupt 0, gen 0 Sep 5 14:36:24 Tower kernel: print_req_error: I/O error, dev nvme0n1, sector 1416326896 Sep 5 14:36:24 Tower kernel: print_req_error: I/O error, dev nvme0n1, sector 1419705792 Sep 5 14:36:24 Tower kernel: print_req_error: I/O error, dev nvme0n1, sector 1355724792 Sep 5 14:36:24 Tower kernel: nvme nvme0: failed to set APST feature (-19) Sep 5 14:36:24 Tower kernel: BTRFS: error (device dm-14) in btrfs_run_delayed_refs:2935: errno=-5 IO failure Sep 5 14:36:24 Tower kernel: BTRFS info (device dm-14): forced readonly Sep 5 14:36:24 Tower kernel: BTRFS: error (device dm-14) in __btrfs_free_extent:6803: errno=-5 IO failure Sep 5 14:36:24 Tower kernel: BTRFS: error (device dm-14) in btrfs_run_delayed_refs:2935: errno=-5 IO failure Sep 5 14:36:24 Tower kernel: BTRFS warning (device dm-14): Skipping commit of aborted transaction. Sep 5 14:36:24 Tower kernel: BTRFS: error (device dm-14) in cleanup_transaction:1846: errno=-5 IO failure Sep 5 14:36:24 Tower kernel: BTRFS info (device dm-14): delayed_refs has NO entry Sep 5 14:36:32 Tower kernel: btrfs_dev_stat_print_on_error: 641 callbacks suppressed Sep 5 14:36:32 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 385, rd 268, flush 0, corrupt 0, gen 0 Sep 5 14:36:32 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 385, rd 269, flush 0, corrupt 0, gen 0 Sep 5 14:36:32 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 385, rd 270, flush 0, corrupt 0, gen 0 Sep 5 14:36:32 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 385, rd 271, flush 0, corrupt 0, gen 0 Sep 5 14:36:32 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 385, rd 272, flush 0, corrupt 0, gen 0 Sep 5 14:36:32 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 385, rd 273, flush 0, corrupt 0, gen 0 Sep 5 14:36:32 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 385, rd 274, flush 0, corrupt 0, gen 0 Sep 5 14:36:32 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 385, rd 275, flush 0, corrupt 0, gen 0 Sep 5 14:36:32 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 385, rd 276, flush 0, corrupt 0, gen 0 Sep 5 14:36:32 Tower kernel: BTRFS error (device dm-14): bdev /dev/mapper/ssd errs: wr 385, rd 277, flush 0, corrupt 0, gen 0 tower-diagnostics-20190906-0116.zip
  11. def toggle_unraid_share(url, setting=True, share_name='share'): from requests_html import HTMLSession session = HTMLSession() r = session.get(url) r.html.render() token = re.search(r"csrf_token=([A-Z0-9]+)", r.html.full_text).groups()[0] r2 = session.post(f"{url}/update.htm", data={'shareName': share_name, 'shareExport': 'e' if setting else '-', 'shareSecurity': 'public', 'changeShareSecurity': 'Apply', 'csrf_token': token}) r2.raise_for_status() session.close() Here's the script in function form. Requires Python 3 and requests_html. Should be fairly easy to generalize it to other settings changes (by changing the data argument in the sessions.post call). URL is your unraid address, incl http(s)://
  12. Couldn't figure this out using the shell, but ended up writing a short Python script to toggle options through HTTP to the webgui. CSRF tokens made it a bit trickier. Can send it out if anyone is also looking for a solution.
  13. Thanks. I ended up replacing it. In general, wish it would prefer user share writes away from the disk to keep parity valid, although I guess it might be impossible to tell if the first write error that brought the disk down actually affected the data or not.
  14. Getting "no such device" and immediate exit with every version - have tried all the way back to 2.07