Ubuntu Systemd Bad Entry
-
And the array is resilvering the now replaced disk.
As an FYI for anyone on software RAID, the drives are organized in a manner that aligns to the SATA connections on the board.
IE : USB boot device is SDA
SATA1 (or 0 however it is labeled) = SDB
SATA2 = SDC
and so on. -
Well at least for now, the I/O errors have stopped after I replaced the bad disk in the host array and reverted the VM.
I'll keep an eye on it and report back if the issue comes back.
-
And these are back.
-
Same disk?
-
On the guest OS there is only 1 disk (it's presented from the array).
I checked the smart stats on each drive and found no issues. MD was also fine.
-
-
-
Although on a separate note..... this is a shit desktop... that is acting as the hypervisor... so errors really shouldn't surprise me.
-
All disks in the host are marked as "Old_age" so there really isn't much that I can do besides assemble something else.
Hopefully out of newer equipment.
-
Maybe I'm reading this wrong.. Smart overall-health self-assessment is passed on all drives.
So maybe it's just a column saying "it'll fail here"
-
I'm performing long tests on each of the drives to confirm the information I have is accurate. I'll update in ~90 minutes.
-
-
@scottalanmiller said in Ubuntu Systemd Bad Entry:
You can watch this while you wait....
hahaha thanks...
You might as well have Rick Rolled me.
-
@DustinB3403 Rick Rolling the Moldovan way.
-
I'm curious as to why the VM is showing these issues, but the hypervisor isn't listing any issues at all.
-
@DustinB3403 said in Ubuntu Systemd Bad Entry:
I'm curious as to why the VM is showing these issues, but the hypervisor isn't listing any issues at all.
My guess is a driver issue. You are not getting errors from a disk but from an abstraction of the array. So you are two interfaces separated from the actual disks.
-
I'll just dump the VM, at this point it's been 4 days without a clean backup. It's only a Ubuntu VM with an NFS/SMB share.
-
So after building a new NFS/SMB vm (and deleting the old one) the new system seems fine.
Something must've got corrupted because of the smartctl errors.
