Busybox initramfs again and again
Clash Royale CLAN TAG#URR8PPP up vote
1
down vote
favorite
I have ubuntu 16.04 installed.. whenever I boot the system and try to run ubuntu, busy box pops up. I do a manual check ---fsck -yf /dev/sda12--- and then reboot.. now the ubuntu boots properly but then after few minutes i am not able to save/write anything on ubuntu(says the the disk is read only) nor can i open my other partitions which i was able to access few minutes ago. I again restart my system and the same busybox appears. The cycle goes on and on. What should i do.. is my hard drive completely corrupted?
boot initramfs busybox
asked Mar 31 at 16:37
Mohit Kurani
85
add a comment |Â
up vote
1
down vote
favorite
I have ubuntu 16.04 installed.. whenever I boot the system and try to run ubuntu, busy box pops up. I do a manual check ---fsck -yf /dev/sda12--- and then reboot.. now the ubuntu boots properly but then after few minutes i am not able to save/write anything on ubuntu(says the the disk is read only) nor can i open my other partitions which i was able to access few minutes ago. I again restart my system and the same busybox appears. The cycle goes on and on. What should i do.. is my hard drive completely corrupted?
boot initramfs busybox
asked Mar 31 at 16:37
Mohit Kurani
85
See my recent answer to askubuntu.com/questions/1019790/… and see if it applies to your situation.
– heynnema
Mar 31 at 17:55
I have already done that.. also i did not install any windows driver
– Mohit Kurani
Apr 1 at 10:54
What kind of primary disk do you use... hard disk or SSD? Open theDisksapplication and look at the SMART data to see if you're having a hardware problem. Do any of your other installed OS's have a problem also?
– heynnema
Apr 1 at 12:31
A mistake from my side.. i did not run the command in recovery mode but in the normal mode... everything works perfectly now... thanks for the help, you are great :D
– Mohit Kurani
Apr 1 at 15:20
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have ubuntu 16.04 installed.. whenever I boot the system and try to run ubuntu, busy box pops up. I do a manual check ---fsck -yf /dev/sda12--- and then reboot.. now the ubuntu boots properly but then after few minutes i am not able to save/write anything on ubuntu(says the the disk is read only) nor can i open my other partitions which i was able to access few minutes ago. I again restart my system and the same busybox appears. The cycle goes on and on. What should i do.. is my hard drive completely corrupted?
boot initramfs busybox
asked Mar 31 at 16:37
Mohit Kurani
85
I have ubuntu 16.04 installed.. whenever I boot the system and try to run ubuntu, busy box pops up. I do a manual check ---fsck -yf /dev/sda12--- and then reboot.. now the ubuntu boots properly but then after few minutes i am not able to save/write anything on ubuntu(says the the disk is read only) nor can i open my other partitions which i was able to access few minutes ago. I again restart my system and the same busybox appears. The cycle goes on and on. What should i do.. is my hard drive completely corrupted?
boot initramfs busybox
boot initramfs busybox
asked Mar 31 at 16:37
Mohit Kurani
85
asked Mar 31 at 16:37
Mohit Kurani
85
asked Mar 31 at 16:37
Mohit Kurani
85
asked Mar 31 at 16:37
Mohit Kurani
85
asked Mar 31 at 16:37
Mohit Kurani
85
85
See my recent answer to askubuntu.com/questions/1019790/… and see if it applies to your situation.
– heynnema
Mar 31 at 17:55
I have already done that.. also i did not install any windows driver
– Mohit Kurani
Apr 1 at 10:54
What kind of primary disk do you use... hard disk or SSD? Open theDisksapplication and look at the SMART data to see if you're having a hardware problem. Do any of your other installed OS's have a problem also?
– heynnema
Apr 1 at 12:31
A mistake from my side.. i did not run the command in recovery mode but in the normal mode... everything works perfectly now... thanks for the help, you are great :D
– Mohit Kurani
Apr 1 at 15:20
add a comment |Â
See my recent answer to askubuntu.com/questions/1019790/… and see if it applies to your situation.
– heynnema
Mar 31 at 17:55
I have already done that.. also i did not install any windows driver
– Mohit Kurani
Apr 1 at 10:54
What kind of primary disk do you use... hard disk or SSD? Open theDisksapplication and look at the SMART data to see if you're having a hardware problem. Do any of your other installed OS's have a problem also?
– heynnema
Apr 1 at 12:31
A mistake from my side.. i did not run the command in recovery mode but in the normal mode... everything works perfectly now... thanks for the help, you are great :D
– Mohit Kurani
Apr 1 at 15:20
See my recent answer to askubuntu.com/questions/1019790/… and see if it applies to your situation.
– heynnema
Mar 31 at 17:55
See my recent answer to askubuntu.com/questions/1019790/… and see if it applies to your situation.
– heynnema
Mar 31 at 17:55
I have already done that.. also i did not install any windows driver
– Mohit Kurani
Apr 1 at 10:54
I have already done that.. also i did not install any windows driver
– Mohit Kurani
Apr 1 at 10:54
What kind of primary disk do you use... hard disk or SSD? Open the
Disks application and look at the SMART data to see if you're having a hardware problem. Do any of your other installed OS's have a problem also?– heynnema
Apr 1 at 12:31
What kind of primary disk do you use... hard disk or SSD? Open the
Disks application and look at the SMART data to see if you're having a hardware problem. Do any of your other installed OS's have a problem also?– heynnema
Apr 1 at 12:31
A mistake from my side.. i did not run the command in recovery mode but in the normal mode... everything works perfectly now... thanks for the help, you are great :D
– Mohit Kurani
Apr 1 at 15:20
A mistake from my side.. i did not run the command in recovery mode but in the normal mode... everything works perfectly now... thanks for the help, you are great :D
– Mohit Kurani
Apr 1 at 15:20
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Update #1: running fsck in recovery mode fixed the problem. I document this here to give the complete answer.
Lets first check your file system for errors.
To check the file system on your Ubuntu partition...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f / - repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted - open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Apr 1 at 16:07
heynnema
15.5k21946
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Update #1: running fsck in recovery mode fixed the problem. I document this here to give the complete answer.
Lets first check your file system for errors.
To check the file system on your Ubuntu partition...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f / - repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted - open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Apr 1 at 16:07
heynnema
15.5k21946
add a comment |Â
up vote
1
down vote
accepted
Update #1: running fsck in recovery mode fixed the problem. I document this here to give the complete answer.
Lets first check your file system for errors.
To check the file system on your Ubuntu partition...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f / - repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted - open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Apr 1 at 16:07
heynnema
15.5k21946
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Update #1: running fsck in recovery mode fixed the problem. I document this here to give the complete answer.
Lets first check your file system for errors.
To check the file system on your Ubuntu partition...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f / - repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted - open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Apr 1 at 16:07
heynnema
15.5k21946
Update #1: running fsck in recovery mode fixed the problem. I document this here to give the complete answer.
Lets first check your file system for errors.
To check the file system on your Ubuntu partition...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f / - repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted - open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Apr 1 at 16:07
heynnema
15.5k21946
answered Apr 1 at 16:07
heynnema
15.5k21946
answered Apr 1 at 16:07
heynnema
15.5k21946
answered Apr 1 at 16:07
heynnema
15.5k21946
15.5k21946
add a comment |Â
add a comment |Â
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%2f1020872%2fbusybox-initramfs-again-and-again%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
See my recent answer to askubuntu.com/questions/1019790/… and see if it applies to your situation.
– heynnema
Mar 31 at 17:55
I have already done that.. also i did not install any windows driver
– Mohit Kurani
Apr 1 at 10:54
What kind of primary disk do you use... hard disk or SSD? Open the
Disksapplication and look at the SMART data to see if you're having a hardware problem. Do any of your other installed OS's have a problem also?– heynnema
Apr 1 at 12:31
A mistake from my side.. i did not run the command in recovery mode but in the normal mode... everything works perfectly now... thanks for the help, you are great :D
– Mohit Kurani
Apr 1 at 15:20