sgtsquiggs

Seeing this today - I can reliably reproduce it by manually running a kometa scan against my media library. Running 6.12.14

Ugh i'm an idiot... thanks I didn't notice this before bc you couldn't click it when it was marked "REBOOT" and when mounted it linked to the file manager.

I never specified a mount point for either - I never saw the option. When I look at the details for the two targets I see a mount point specified but there's no option to change it: I feel like I missed a step somewhere. The iSCSI Initator plugin doesn't have any options aside from connection info for the target.

Attached - if more is needed I can enable debug logging and reboot to get a clean slate. I am not sure why the wrong information is shown in the screenshot below: tower-diagnostics-20231210-0016.zip

I have two iscsi targets on a remote machine. I can mount one of them but the other has always had the REBOOT button where MOUNT should be. How do I fix this?

How screwed am I? I have a 1TB cache pool and I am adding 2x 4TB drives to it: Nov 25 07:21:33 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdf1 errs: wr 201835, rd 223, flush 3930, corrupt 0, gen 0 Nov 25 07:21:33 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdf1 errs: wr 201836, rd 223, flush 3930, corrupt 0, gen 0 Nov 25 07:21:33 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdf1 errs: wr 201837, rd 223, flush 3930, corrupt 0, gen 0 Nov 25 07:21:33 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdf1 errs: wr 201838, rd 223, flush 3930, corrupt 0, gen 0 Nov 25 07:21:33 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdf1 errs: wr 201839, rd 223, flush 3930, corrupt 0, gen 0 Nov 25 07:21:33 Tower kernel: BTRFS error (device nvme0n1p1): error writing primary super block to device 2 Nov 25 07:21:33 Tower kernel: BTRFS error (device nvme0n1p1): error writing primary super block to device 2 Nov 25 07:21:35 Tower kernel: BTRFS info (device nvme0n1p1): found 12057 extents, stage: move data extents Nov 25 07:21:35 Tower kernel: BTRFS error (device nvme0n1p1): error writing primary super block to device 2 Nov 25 07:21:36 Tower kernel: BTRFS error (device nvme0n1p1): error writing primary super block to device 2 Nov 25 07:21:36 Tower kernel: BTRFS error (device nvme0n1p1): error writing primary super block to device 2 Nov 25 07:21:36 Tower kernel: BTRFS info (device nvme0n1p1): found 12057 extents, stage: update data pointers Nov 25 07:21:37 Tower kernel: btrfs_end_super_write: 17 callbacks suppressed Nov 25 07:21:37 Tower kernel: BTRFS warning (device nvme0n1p1): lost page write due to IO error on /dev/sdf1 (-5) Nov 25 07:21:37 Tower kernel: BTRFS warning (device nvme0n1p1): lost page write due to IO error on /dev/sdf1 (-5) Nov 25 07:21:37 Tower kernel: BTRFS warning (device nvme0n1p1): lost page write due to IO error on /dev/sdf1 (-5) Nov 25 07:21:37 Tower kernel: BTRFS error (device nvme0n1p1): error writing primary super block to device 2 Nov 25 07:21:37 Tower kernel: BTRFS warning (device nvme0n1p1): lost page write due to IO error on /dev/sdf1 (-5) Nov 25 07:21:37 Tower kernel: BTRFS warning (device nvme0n1p1): lost page write due to IO error on /dev/sdf1 (-5) Nov 25 07:21:37 Tower kernel: BTRFS warning (device nvme0n1p1): lost page write due to IO error on /dev/sdf1 (-5) Nov 25 07:21:37 Tower kernel: BTRFS error (device nvme0n1p1): error writing primary super block to device 2 Nov 25 07:21:37 Tower kernel: BTRFS warning (device nvme0n1p1): lost page write due to IO error on /dev/sdf1 (-5) Nov 25 07:21:37 Tower kernel: BTRFS warning (device nvme0n1p1): lost page write due to IO error on /dev/sdf1 (-5) Nov 25 07:21:37 Tower kernel: BTRFS warning (device nvme0n1p1): lost page write due to IO error on /dev/sdf1 (-5) Nov 25 07:21:37 Tower kernel: BTRFS error (device nvme0n1p1): error writing primary super block to device 2 Nov 25 07:21:37 Tower kernel: BTRFS info (device nvme0n1p1): relocating block group 1093099585536 flags data Nov 25 07:21:37 Tower kernel: BTRFS warning (device nvme0n1p1): lost page write due to IO error on /dev/sdf1 (-5) Nov 25 07:21:37 Tower kernel: BTRFS error (device nvme0n1p1): error writing primary super block to device 2 Nov 25 07:21:38 Tower kernel: btrfs_dev_stat_print_on_error: 1804 callbacks suppressed Nov 25 07:21:38 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdf1 errs: wr 203635, rd 223, flush 3939, corrupt 0, gen 0 Nov 25 07:21:38 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdf1 errs: wr 203636, rd 223, flush 3939, corrupt 0, gen 0 Nov 25 07:21:38 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdf1 errs: wr 203637, rd 223, flush 3939, corrupt 0, gen 0 Nov 25 07:21:38 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdf1 errs: wr 203638, rd 223, flush 3939, corrupt 0, gen 0 Nov 25 07:21:38 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdf1 errs: wr 203639, rd 223, flush 3939, corrupt 0, gen 0 Nov 25 07:21:38 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdf1 errs: wr 203639, rd 223, flush 3940, corrupt 0, gen 0 Nov 25 07:21:38 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdf1 errs: wr 203640, rd 223, flush 3940, corrupt 0, gen 0 Nov 25 07:21:38 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdf1 errs: wr 203641, rd 223, flush 3940, corrupt 0, gen 0 Edit: Found the issue - poor connection on one of the SSDs.