Halo,
Minta bantuannya, dedicated server tiba-tiba crash, dan setelah reboot semua file system jadi read-only.
Jul 24 06
36 server kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 24 06
36 server kernel: sd 0:0:0:0: [sda] Sense Key : Aborted Command [current] [descriptor]
Jul 24 06
36 server kernel: sd 0:0:0:0: [sda] Add. Sense: No additional sense information
Jul 24 06
36 server kernel: sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 21 91 b3 10 00 01 78 00
Jul 24 06
37 server kernel: Aborting journal on device sda8-8.
Jul 24 06
37 server kernel: EXT4-fs error (device sda8): ext4_journal_start_sb:
Jul 24 06
37 server kernel: EXT4-fs error (device sda8): ext4_journal_start_sb: Detected aborted journal
Jul 24 06
37 server kernel: EXT4-fs (sda8): Remounting filesystem read-only
Jul 24 06
37 server kernel: EXT4-fs (sda8): delayed block allocation failed for inode 12329117 at logical offset 0 with max blocks 7 with error -30
Jul 24 06
37 server kernel: EXT4-fs (sda8): ext4_da_writepages: jbd2_start: 992 pages, ino 12329117; err -30
Saya coba fsck /dev/sda8 tidak bisa di umount karena busy, kalau saya matikan prosesnya saya otomatis log out dari SSH.
Minta bantuannya, dedicated server tiba-tiba crash, dan setelah reboot semua file system jadi read-only.
Jul 24 06

Jul 24 06

Jul 24 06

Jul 24 06

Jul 24 06

Jul 24 06

Jul 24 06

Jul 24 06

Jul 24 06

Jul 24 06

Saya coba fsck /dev/sda8 tidak bisa di umount karena busy, kalau saya matikan prosesnya saya otomatis log out dari SSH.