Hello,
this is my first topic on this forum, so dont be mad with me if anything is wrong with it. Even with grammar ;-) (not native speaker)
I'm running an ESXI Server with virtualized Debian 10 Linux.
On this virtual machine a USB3 device (HW Raid device) is attached running a raid5 with 5x4TB.
Irregular the device falls back into readonly mode.
Code:
[Mo Okt 28 19:41:35 2019] Aborting journal on device dm-3-8.
[Mo Okt 28 19:41:35 2019] Buffer I/O error on dev dm-3, logical block 1953005568, lost sync page write
[Mo Okt 28 19:41:35 2019] JBD2: Error -5 detected when updating journal superblock for dm-3-8.
[Mo Okt 28 19:41:35 2019] Buffer I/O error on dev dm-3, logical block 0, lost sync page write
[Mo Okt 28 19:41:35 2019] EXT4-fs error (device dm-3): ext4_journal_check_start:56: Detected aborted journal
[Mo Okt 28 19:41:35 2019] EXT4-fs (dm-3): Remounting filesystem read-only
[Mo Okt 28 19:41:35 2019] EXT4-fs (dm-3): previous I/O error to superblock detected
All harddisk are fine and are checked with their smart status.
After remounting them, all is working fine again for time x.
As Raid Cage i use a Sharkoon Raid Station. I allready changed the USB3 cable.
I guess it could be the chipset on the raid cage. it is a JMicron Chip JMB 393.
Anyone got an idea what i can do?
Kind regards
Michael