Ubuntu Server 16.04.5 LTS (Xenial) EXT4-fs I/O error on dev dm-0
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
.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
16.04 server
add a comment |Â
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
16.04 server
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
add a comment |Â
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
16.04 server
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
16.04 server
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
add a comment |Â
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
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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