Ubuntu Server 16.04.5 LTS (Xenial) EXT4-fs I/O error on dev dm-0

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP


.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
0
down vote

favorite












I have a Unifi NVR running on Ubuntu Server 16.04.5 LTS (Xenial) that runs for about a day before falling over. When I check the console I see pages of error text like this:



[136429.061821] EXT4-fs (dm-0): previous I/O error to superblock detected
[136429.065607] Buffer I/O error on dev dm-0, logical block 0, lost sync page write
[136429.068814] Core dump to |/usr/share/apport/apport 7415 7 0 1 7415 pipe failed
[136462.996124] systemd-journald[434]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[136489.073364] EXT4-fs error (device dm-0): __ext4_get_inode_loc:4116: inode #1314111: block 524311123: comm kworker/u128:3: unable to read itable block


link to screenshot



dm-0 is not a valid volume, so I assume it's some sort of cache. How do we figure out what's breaking it? Sorry, very new to Linux.



Thanks,



Trevor







share|improve this question





















  • In the end it was far quicker to create a new VM, import the video data and NVR configuration, rather than figure this out.
    – TrevorX
    18 hours ago
















up vote
0
down vote

favorite












I have a Unifi NVR running on Ubuntu Server 16.04.5 LTS (Xenial) that runs for about a day before falling over. When I check the console I see pages of error text like this:



[136429.061821] EXT4-fs (dm-0): previous I/O error to superblock detected
[136429.065607] Buffer I/O error on dev dm-0, logical block 0, lost sync page write
[136429.068814] Core dump to |/usr/share/apport/apport 7415 7 0 1 7415 pipe failed
[136462.996124] systemd-journald[434]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[136489.073364] EXT4-fs error (device dm-0): __ext4_get_inode_loc:4116: inode #1314111: block 524311123: comm kworker/u128:3: unable to read itable block


link to screenshot



dm-0 is not a valid volume, so I assume it's some sort of cache. How do we figure out what's breaking it? Sorry, very new to Linux.



Thanks,



Trevor







share|improve this question





















  • In the end it was far quicker to create a new VM, import the video data and NVR configuration, rather than figure this out.
    – TrevorX
    18 hours ago












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have a Unifi NVR running on Ubuntu Server 16.04.5 LTS (Xenial) that runs for about a day before falling over. When I check the console I see pages of error text like this:



[136429.061821] EXT4-fs (dm-0): previous I/O error to superblock detected
[136429.065607] Buffer I/O error on dev dm-0, logical block 0, lost sync page write
[136429.068814] Core dump to |/usr/share/apport/apport 7415 7 0 1 7415 pipe failed
[136462.996124] systemd-journald[434]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[136489.073364] EXT4-fs error (device dm-0): __ext4_get_inode_loc:4116: inode #1314111: block 524311123: comm kworker/u128:3: unable to read itable block


link to screenshot



dm-0 is not a valid volume, so I assume it's some sort of cache. How do we figure out what's breaking it? Sorry, very new to Linux.



Thanks,



Trevor







share|improve this question













I have a Unifi NVR running on Ubuntu Server 16.04.5 LTS (Xenial) that runs for about a day before falling over. When I check the console I see pages of error text like this:



[136429.061821] EXT4-fs (dm-0): previous I/O error to superblock detected
[136429.065607] Buffer I/O error on dev dm-0, logical block 0, lost sync page write
[136429.068814] Core dump to |/usr/share/apport/apport 7415 7 0 1 7415 pipe failed
[136462.996124] systemd-journald[434]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[136489.073364] EXT4-fs error (device dm-0): __ext4_get_inode_loc:4116: inode #1314111: block 524311123: comm kworker/u128:3: unable to read itable block


link to screenshot



dm-0 is not a valid volume, so I assume it's some sort of cache. How do we figure out what's breaking it? Sorry, very new to Linux.



Thanks,



Trevor









share|improve this question












share|improve this question




share|improve this question








edited 2 days ago
























asked 2 days ago









TrevorX

11




11











  • In the end it was far quicker to create a new VM, import the video data and NVR configuration, rather than figure this out.
    – TrevorX
    18 hours ago
















  • In the end it was far quicker to create a new VM, import the video data and NVR configuration, rather than figure this out.
    – TrevorX
    18 hours ago















In the end it was far quicker to create a new VM, import the video data and NVR configuration, rather than figure this out.
– TrevorX
18 hours ago




In the end it was far quicker to create a new VM, import the video data and NVR configuration, rather than figure this out.
– TrevorX
18 hours ago















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1062068%2fubuntu-server-16-04-5-lts-xenial-ext4-fs-i-o-error-on-dev-dm-0%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1062068%2fubuntu-server-16-04-5-lts-xenial-ext4-fs-i-o-error-on-dev-dm-0%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491