It looks like the floppy drive was the culprit, I removed and blacklisted the driver and now I am not getting those errors. Now on to making sure these second hand disks are worth using (smartctl and smartd to the rescue). I was heading in the direction of disabling it in the BIOS but the driver was easier. Thanks Russell
On Sat, Jul 15, 2023 at 10:26 PM Russell Senior <russ...@personaltelco.net> wrote: > It might be unrelated. Or maybe somehow touching a disk is triggering a > probe of the floppy. Just wild speculation. Trying to disable the drive in > bios or rmmod'ing the floppy driver might change the behavior. > > On Sat, Jul 15, 2023, 22:23 Michael Ewan <michaelewa...@gmail.com> wrote: > > > I did think of removing the floppy in BIOS, but the question still > presents > > itself, why do I get errors when accessing a mounted disk? > > > > On Sat, Jul 15, 2023 at 10:15 PM Russell Senior < > russ...@personaltelco.net > > > > > wrote: > > > > > This might be relevant: > > > > > > > > > > > > https://unix.stackexchange.com/questions/53513/linux-disable-dev-fd0-floppy > > > > > > -- > > > Russell > > > > > > On Sat, Jul 15, 2023 at 9:28 PM Michael Ewan <michaelewa...@gmail.com> > > > wrote: > > > > > > > > I am setting up a file server, currently Ubuntu Server 22.04. I have > > > three > > > > 1TB data disks, two act normally, the third is telling me there are > > > errors > > > > on the floppy device. Could someone shed some light on this? > Thanks. > > > > The disks are in an LVM volume group, the logical volumes are > specified > > > as > > > > the whole disk to isolate one from the other. They have an XFS file > > > > system. I was running Bonnie++ to exercise the disks. Here is the > > dmesg > > > > output. > > > > This is repeatable. > > > > > > > > [105001.499913] xfs filesystem being mounted at /data2 supports > > > timestamps > > > > until 2038 (0x7fffffff) > > > > [111473.198440] floppy0: disk absent or changed during operation > > > > [111473.198449] print_req_error: 4 callbacks suppressed > > > > [111473.198451] blk_update_request: I/O error, dev fd0, sector 0 op > > > > 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 > > > > [111473.198526] floppy0: disk absent or changed during operation > > > > [111473.198529] blk_update_request: I/O error, dev fd0, sector 0 op > > > > 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 > > > > [111473.198543] Buffer I/O error on dev fd0, logical block 0, async > > page > > > > read > > > > [111475.418535] floppy0: disk absent or changed during operation > > > > [111475.418543] blk_update_request: I/O error, dev fd0, sector 0 op > > > > 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 > > > > [111475.418627] floppy0: disk absent or changed during operation > > > > [111475.418630] blk_update_request: I/O error, dev fd0, sector 0 op > > > > 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 > > > > [111475.418645] Buffer I/O error on dev fd0, logical block 0, async > > page > > > > read > > > > [111476.023674] floppy0: disk absent or changed during operation > > > > [111476.023682] blk_update_request: I/O error, dev fd0, sector 0 op > > > > 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 > > > > [111476.023812] floppy0: disk absent or changed during operation > > > > [111476.023815] blk_update_request: I/O error, dev fd0, sector 0 op > > > > 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 > > > > [111476.023825] Buffer I/O error on dev fd0, logical block 0, async > > page > > > > read > > > > > >
