TerraMaster Forum

I installed a new virtual machine with Home Assistant from scratch (by importing an .ova file) in TOS6. After that, I restored a backup of my HA version. Now, once or twice a day, this version of the virtual machine crashes with a "Buffer I/O error on device sda" error. After restarting, it works for a while (several hours), and then crashes again with the same error.
What could be causing this, and how can I fix it?
I also installed the same version of HA a year ago on the same version F6-424 MAX, and I didn't get any such errors.

Image uploads to the forum aren't working. Here are the error logs:

ha >
[32311.892387] sd 0:0:0:0: rejecting I/O to offline device
[32311.892650] I/O error, dev sda, sector 251272096 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
[32311.892877] Buffer I/O error on device sda8, logical block 2968080
[32311.893037] I/O error, dev sda, sector 251272120 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
[32311.893254] Buffer I/O error on device sda8, logical block 2968083
[32311.893409] I/O error, dev sda, sector 251274232 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
[32311.893659] Buffer I/O error on device sda8, logical block 2968122
[32311.893899] I/O error, dev sda, sector 251255044 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
[32311.894122] Buffer I/O error on device sda8, logical block 2968131
[32311.894294] I/O error, dev sda, sector 251276116 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
[32311.894511] Buffer I/O error on device sda8, logical block 2968145
[32311.894668] I/O error, dev sda, sector 251277192 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
[32311.894879] Buffer I/O error on device sda8, logical block 2968157
[32311.895029] I/O error, dev sda, sector 253346448 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
[32311.895255] Buffer I/O error on device sda8, logical block 2986624
[32311.895407] I/O error, dev sda, sector 253366000 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
[32311.895627] Buffer I/O error on device sda8, logical block 2986843
[32311.895776] I/O error, dev sda, sector 253367520 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
[32311.895988] Buffer I/O error on device sda8, logical block 2988662
[32311.896137] I/O error, dev sda, sector 253369004 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
[32311.896348] Buffer I/O error on device sda8, logical block 2988681
[32311.896800] Buffer I/O error on dev sda7, logical block 293, lost async page write
[32311.897500] Aborting journal on device sda8-8.
[32311.897795] EXT4-fs error (device sda8): ext4_reserve_inode_write:5862: Journal has aborted
[32311.898273] EXT4-fs error (device sda8): ext4_dirty_inode:6066: inode #394948: comm node: mark_inode_dirty error
[32311.898407] EXT4-fs error (device sda8): ext4_journal_check_start:84: comm systemd-journal: Detected aborted journal
[32311.898450] EXT4-fs error (device sda8) in ext4_dirty_inode:6067: Journal has aborted
[32359.806503] Aborting journal on device sda7-8.
[32360.172491] scsi target0:0:0:0: mptspi: ioc0: mpt_config failed
[32428.694183] scsi target0:0:0:0: mptspi: ioc0: mpt_config failed
[32427.860997] scsi target0:0:0:0: Domain Validation Initial Inquiry Failed
[32428.055051] scsi target0:0:0:0: mptspi: ioc0: mpt_config failed
[32428.074134] scsi target0:0:0:0: mptspi: ioc0: mpt_config failed
[32428.046095] EXT4-fs error (device sda7): ext4_reserve_inode_write:5862: IO failure
[32428.047921] EXT4-fs error (device sda7): ext4_dirty_inode:6066: inode #43: comm systemd-timesyn: mark_inode_dirty error
[32428.048509] EXT4-fs error (device sda7): ext4_dirty_inode:6067: IO failure
[32428.051291] EXT4-fs (sda8): Remounting filesystem read-only
[32432.989185] systemd-coredump[2295]: Process 105 (systemd-journal) of user 0 terminated abnormally without generating a coredump.
[32448.986325] EXT4-fs error (device sda7): ext4_journal_check_start:84: comm systemd-timesyn: Detected aborted journal
[32448.986455] EXT4-fs (sda7): Remounting filesystem read-only

This bug is associated with a bug in the operation of the btrfs system. The decision was made here - viewtopic.php?t=9215

This is possible. The load of BTRFS quota (btrfs-transact + btrfs-cleaner) may be very high, which could cause abnormal operation of the program from the day before yesterday. It is not recommended to run important programs while BTRFS quota is running.