Ask Your Question

routine "I/O error while writing superblock"

asked 2018-10-13 09:12:08 -0500

updated 2018-10-13 09:12:48 -0500

I am not sure how to figure out what goes wrong. Often, after minutes, sometimes after hours, the system hangs. I get an

EXT4-fs error (device dm-2): ext4_find_entry:1438: inode #10448989: comm gdm-session-wor: reading directory lblock: 0
Buffer I/O error on dev dm-2, logical block 0, lost sync page write
EXT4-fs  (device dm-2): I/O error while writing superblock

dm-2 is my lvm root / device on an ssd.

Any suggestion on how to research this is welcome. I guess the question is: can I prevent the cause of this error?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2018-10-13 12:33:06 -0500

ed209 gravatar image
Buffer I/O error on dev

means your storage is dying. You could try to run e2fsck on your / partition from, say, a live image in order to try to fix the error, but quite probably yor disk/ssd/whatever won't last very long. Backup and replace the drive as soon as possible.

edit flag offensive delete link more


thank you; this made me investigate further with smartctl. I now recognise that the device is a decrypted partition. if I run smartctl on the ssd underlying it, I cannot identify any problem. can you point me to a way of verifying that the storage is dying? backups are in place, of course :) cheers

ingli gravatar imageingli ( 2018-10-13 14:01:04 -0500 )edit

The best thing is to use diagnostics from the maker of your ssd. Usually they give an iso file for a bootable cd. As far as I can remember smart was unable to recognise a patently failing drive even once. Next to useless. There is also a tiny possibility that cable or sata interface are the problem, but I wouldn't bet on it.

ed209 gravatar imageed209 ( 2018-10-15 05:56:00 -0500 )edit

Question Tools

1 follower


Asked: 2018-10-13 09:12:08 -0500

Seen: 1,973 times

Last updated: Oct 13 '18