chronic issue with boot into read-only
Clash Royale CLAN TAG#URR8PPP up vote
1
down vote
favorite
I have a bit of a problem with my non-dual 16.04 Ubuntu computer. I recently booted and tried to do some of my usual computer things which didn't really work. I figured out that I was mounted in read-only, so I rebooted and got stuck at an initramfs screen. I ran fsck -y /dev/sda1 and reboot and managed to boot into a writable desktop. Unfortunately, the problem wasn't resolved by that; I sometimes have to go through this procedure up to three times per boot to get into a writable system, and sometimes a writable system will just become read-only for no reason apparent to me.
I would be pretty happy if someone could help me to work out a solution for this issue that is, in all honesty, a bit inconvenient.
boot fsck read-only
edited Mar 30 at 13:39
sudodus
20.2k32667
asked Mar 29 at 22:57
Selim Weissenstein
62
add a comment |Â
up vote
1
down vote
favorite
I have a bit of a problem with my non-dual 16.04 Ubuntu computer. I recently booted and tried to do some of my usual computer things which didn't really work. I figured out that I was mounted in read-only, so I rebooted and got stuck at an initramfs screen. I ran fsck -y /dev/sda1 and reboot and managed to boot into a writable desktop. Unfortunately, the problem wasn't resolved by that; I sometimes have to go through this procedure up to three times per boot to get into a writable system, and sometimes a writable system will just become read-only for no reason apparent to me.
I would be pretty happy if someone could help me to work out a solution for this issue that is, in all honesty, a bit inconvenient.
boot fsck read-only
edited Mar 30 at 13:39
sudodus
20.2k32667
asked Mar 29 at 22:57
Selim Weissenstein
62
2
Maybe your disk hardware is dying? Can you check their SMART status/health report and maybe run a self-test? Depending on the desktop environment you use, there should be a "Disks" (gnome-disks) application that has a menu button in the top right which contains these options.
– Byte Commander
Mar 29 at 23:02
The self-test failed, which I take is a bad sign. The last overall assessment was 'Disk is OK, one bad sector'.
– Selim Weissenstein
Mar 30 at 10:43
1
Could you edit your question and add a screenshot of the SMART window including the attributes table and the test results?
– Byte Commander
Mar 30 at 12:23
I suggest that you clone from this failing drive to a new drive of at least the same size. You can useddrescuefor that purpose. Then you can do whatever recovery work you need on the cloned copy in order to save the files that you cannot afford to lose. See this link, Repair the partition table and file system. Scroll down to ' Advanced repair of a partition table, file system and/or recovery of files'
– sudodus
Mar 30 at 13:35
Thank you. I will try to do this in the coming days & I will report back with the issues I am sure I will encounter.
– Selim Weissenstein
Apr 6 at 23:28
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have a bit of a problem with my non-dual 16.04 Ubuntu computer. I recently booted and tried to do some of my usual computer things which didn't really work. I figured out that I was mounted in read-only, so I rebooted and got stuck at an initramfs screen. I ran fsck -y /dev/sda1 and reboot and managed to boot into a writable desktop. Unfortunately, the problem wasn't resolved by that; I sometimes have to go through this procedure up to three times per boot to get into a writable system, and sometimes a writable system will just become read-only for no reason apparent to me.
I would be pretty happy if someone could help me to work out a solution for this issue that is, in all honesty, a bit inconvenient.
boot fsck read-only
edited Mar 30 at 13:39
sudodus
20.2k32667
asked Mar 29 at 22:57
Selim Weissenstein
62
I have a bit of a problem with my non-dual 16.04 Ubuntu computer. I recently booted and tried to do some of my usual computer things which didn't really work. I figured out that I was mounted in read-only, so I rebooted and got stuck at an initramfs screen. I ran fsck -y /dev/sda1 and reboot and managed to boot into a writable desktop. Unfortunately, the problem wasn't resolved by that; I sometimes have to go through this procedure up to three times per boot to get into a writable system, and sometimes a writable system will just become read-only for no reason apparent to me.
I would be pretty happy if someone could help me to work out a solution for this issue that is, in all honesty, a bit inconvenient.
boot fsck read-only
boot fsck read-only
edited Mar 30 at 13:39
sudodus
20.2k32667
asked Mar 29 at 22:57
Selim Weissenstein
62
edited Mar 30 at 13:39
sudodus
20.2k32667
asked Mar 29 at 22:57
Selim Weissenstein
62
edited Mar 30 at 13:39
sudodus
20.2k32667
edited Mar 30 at 13:39
sudodus
20.2k32667
edited Mar 30 at 13:39
sudodus
20.2k32667
20.2k32667
asked Mar 29 at 22:57
Selim Weissenstein
62
asked Mar 29 at 22:57
Selim Weissenstein
62
asked Mar 29 at 22:57
Selim Weissenstein
62
62
2
Maybe your disk hardware is dying? Can you check their SMART status/health report and maybe run a self-test? Depending on the desktop environment you use, there should be a "Disks" (gnome-disks) application that has a menu button in the top right which contains these options.
– Byte Commander
Mar 29 at 23:02
The self-test failed, which I take is a bad sign. The last overall assessment was 'Disk is OK, one bad sector'.
– Selim Weissenstein
Mar 30 at 10:43
1
Could you edit your question and add a screenshot of the SMART window including the attributes table and the test results?
– Byte Commander
Mar 30 at 12:23
I suggest that you clone from this failing drive to a new drive of at least the same size. You can useddrescuefor that purpose. Then you can do whatever recovery work you need on the cloned copy in order to save the files that you cannot afford to lose. See this link, Repair the partition table and file system. Scroll down to ' Advanced repair of a partition table, file system and/or recovery of files'
– sudodus
Mar 30 at 13:35
Thank you. I will try to do this in the coming days & I will report back with the issues I am sure I will encounter.
– Selim Weissenstein
Apr 6 at 23:28
add a comment |Â
2
Maybe your disk hardware is dying? Can you check their SMART status/health report and maybe run a self-test? Depending on the desktop environment you use, there should be a "Disks" (gnome-disks) application that has a menu button in the top right which contains these options.
– Byte Commander
Mar 29 at 23:02
The self-test failed, which I take is a bad sign. The last overall assessment was 'Disk is OK, one bad sector'.
– Selim Weissenstein
Mar 30 at 10:43
1
Could you edit your question and add a screenshot of the SMART window including the attributes table and the test results?
– Byte Commander
Mar 30 at 12:23
I suggest that you clone from this failing drive to a new drive of at least the same size. You can useddrescuefor that purpose. Then you can do whatever recovery work you need on the cloned copy in order to save the files that you cannot afford to lose. See this link, Repair the partition table and file system. Scroll down to ' Advanced repair of a partition table, file system and/or recovery of files'
– sudodus
Mar 30 at 13:35
Thank you. I will try to do this in the coming days & I will report back with the issues I am sure I will encounter.
– Selim Weissenstein
Apr 6 at 23:28
2
2
Maybe your disk hardware is dying? Can you check their SMART status/health report and maybe run a self-test? Depending on the desktop environment you use, there should be a "Disks" (
gnome-disks) application that has a menu button in the top right which contains these options.– Byte Commander
Mar 29 at 23:02
Maybe your disk hardware is dying? Can you check their SMART status/health report and maybe run a self-test? Depending on the desktop environment you use, there should be a "Disks" (
gnome-disks) application that has a menu button in the top right which contains these options.– Byte Commander
Mar 29 at 23:02
The self-test failed, which I take is a bad sign. The last overall assessment was 'Disk is OK, one bad sector'.
– Selim Weissenstein
Mar 30 at 10:43
The self-test failed, which I take is a bad sign. The last overall assessment was 'Disk is OK, one bad sector'.
– Selim Weissenstein
Mar 30 at 10:43
1
1
Could you edit your question and add a screenshot of the SMART window including the attributes table and the test results?
– Byte Commander
Mar 30 at 12:23
Could you edit your question and add a screenshot of the SMART window including the attributes table and the test results?
– Byte Commander
Mar 30 at 12:23
I suggest that you clone from this failing drive to a new drive of at least the same size. You can use
ddrescue for that purpose. Then you can do whatever recovery work you need on the cloned copy in order to save the files that you cannot afford to lose. See this link, Repair the partition table and file system. Scroll down to ' Advanced repair of a partition table, file system and/or recovery of files'– sudodus
Mar 30 at 13:35
I suggest that you clone from this failing drive to a new drive of at least the same size. You can use
ddrescue for that purpose. Then you can do whatever recovery work you need on the cloned copy in order to save the files that you cannot afford to lose. See this link, Repair the partition table and file system. Scroll down to ' Advanced repair of a partition table, file system and/or recovery of files'– sudodus
Mar 30 at 13:35
Thank you. I will try to do this in the coming days & I will report back with the issues I am sure I will encounter.
– Selim Weissenstein
Apr 6 at 23:28
Thank you. I will try to do this in the coming days & I will report back with the issues I am sure I will encounter.
– Selim Weissenstein
Apr 6 at 23:28
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%2f1020402%2fchronic-issue-with-boot-into-read-only%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
2
Maybe your disk hardware is dying? Can you check their SMART status/health report and maybe run a self-test? Depending on the desktop environment you use, there should be a "Disks" (
gnome-disks) application that has a menu button in the top right which contains these options.– Byte Commander
Mar 29 at 23:02
The self-test failed, which I take is a bad sign. The last overall assessment was 'Disk is OK, one bad sector'.
– Selim Weissenstein
Mar 30 at 10:43
1
Could you edit your question and add a screenshot of the SMART window including the attributes table and the test results?
– Byte Commander
Mar 30 at 12:23
I suggest that you clone from this failing drive to a new drive of at least the same size. You can use
ddrescuefor that purpose. Then you can do whatever recovery work you need on the cloned copy in order to save the files that you cannot afford to lose. See this link, Repair the partition table and file system. Scroll down to ' Advanced repair of a partition table, file system and/or recovery of files'– sudodus
Mar 30 at 13:35
Thank you. I will try to do this in the coming days & I will report back with the issues I am sure I will encounter.
– Selim Weissenstein
Apr 6 at 23:28