how can I fix error: hd0 out of disk?
I am running Ubuntu 12.04 on a netbook - Acer AS 1410.
After a download session, I restarted the computer and it said:
error: hd0 out of disk. Press any key to continue...
I pressed everything, but it's just frozen there.
Any idea what's wrong with it and what I can do to fix it? I haven't been able to run my computer at all since it's frozen like that. Help please!
I booted the live cd and ran sudo fdisk -lu
into terminal, and here's what it gave me:
Disk /dev/sda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x9a696263
Device Boot Start End Blocks Id System
/dev/sda3 2048 117229567 58613760 5 Extended
/dev/sda5 * 71647232 109039615 18696192 83 Linux
/dev/sda6 109041664 117229567 4093952 82 Linux swap / Solaris
/dev/sda7 4096 71645183 35820544 83 Linux
Partition table entries are not in disk order
I am somewhat of a beginner in this, so don't know what this means. any ideas?
Thanks!
boot grub2
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
|
show 2 more comments
I am running Ubuntu 12.04 on a netbook - Acer AS 1410.
After a download session, I restarted the computer and it said:
error: hd0 out of disk. Press any key to continue...
I pressed everything, but it's just frozen there.
Any idea what's wrong with it and what I can do to fix it? I haven't been able to run my computer at all since it's frozen like that. Help please!
I booted the live cd and ran sudo fdisk -lu
into terminal, and here's what it gave me:
Disk /dev/sda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x9a696263
Device Boot Start End Blocks Id System
/dev/sda3 2048 117229567 58613760 5 Extended
/dev/sda5 * 71647232 109039615 18696192 83 Linux
/dev/sda6 109041664 117229567 4093952 82 Linux swap / Solaris
/dev/sda7 4096 71645183 35820544 83 Linux
Partition table entries are not in disk order
I am somewhat of a beginner in this, so don't know what this means. any ideas?
Thanks!
boot grub2
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
So it doesn't open a command line, it just freezes and you cannot input anything, right?
– edwin
Jun 23 '13 at 23:54
Boot the livecd and runsudo fdisk -lu
and edit your question to show the output.
– psusi
Jun 24 '13 at 1:47
Try rebooting into recovery mode and select repair packages.
– Mitch♦
Jun 24 '13 at 5:35
@edwin , that's right.
– rux
Jun 24 '13 at 22:35
1
Could please start a live DVD/USB, mount all the internal file systems, rundf -h
anddf -i
and include the output in your question? That should provide more insight into what exactly might be "full" here.
– David Foerster
Sep 8 '16 at 18:20
|
show 2 more comments
I am running Ubuntu 12.04 on a netbook - Acer AS 1410.
After a download session, I restarted the computer and it said:
error: hd0 out of disk. Press any key to continue...
I pressed everything, but it's just frozen there.
Any idea what's wrong with it and what I can do to fix it? I haven't been able to run my computer at all since it's frozen like that. Help please!
I booted the live cd and ran sudo fdisk -lu
into terminal, and here's what it gave me:
Disk /dev/sda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x9a696263
Device Boot Start End Blocks Id System
/dev/sda3 2048 117229567 58613760 5 Extended
/dev/sda5 * 71647232 109039615 18696192 83 Linux
/dev/sda6 109041664 117229567 4093952 82 Linux swap / Solaris
/dev/sda7 4096 71645183 35820544 83 Linux
Partition table entries are not in disk order
I am somewhat of a beginner in this, so don't know what this means. any ideas?
Thanks!
boot grub2
I am running Ubuntu 12.04 on a netbook - Acer AS 1410.
After a download session, I restarted the computer and it said:
error: hd0 out of disk. Press any key to continue...
I pressed everything, but it's just frozen there.
Any idea what's wrong with it and what I can do to fix it? I haven't been able to run my computer at all since it's frozen like that. Help please!
I booted the live cd and ran sudo fdisk -lu
into terminal, and here's what it gave me:
Disk /dev/sda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x9a696263
Device Boot Start End Blocks Id System
/dev/sda3 2048 117229567 58613760 5 Extended
/dev/sda5 * 71647232 109039615 18696192 83 Linux
/dev/sda6 109041664 117229567 4093952 82 Linux swap / Solaris
/dev/sda7 4096 71645183 35820544 83 Linux
Partition table entries are not in disk order
I am somewhat of a beginner in this, so don't know what this means. any ideas?
Thanks!
boot grub2
boot grub2
edited Oct 12 '15 at 14:37
Thomas Ward♦
43.6k23120173
43.6k23120173
asked Jun 23 '13 at 23:23
ruxrux
23125
23125
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
So it doesn't open a command line, it just freezes and you cannot input anything, right?
– edwin
Jun 23 '13 at 23:54
Boot the livecd and runsudo fdisk -lu
and edit your question to show the output.
– psusi
Jun 24 '13 at 1:47
Try rebooting into recovery mode and select repair packages.
– Mitch♦
Jun 24 '13 at 5:35
@edwin , that's right.
– rux
Jun 24 '13 at 22:35
1
Could please start a live DVD/USB, mount all the internal file systems, rundf -h
anddf -i
and include the output in your question? That should provide more insight into what exactly might be "full" here.
– David Foerster
Sep 8 '16 at 18:20
|
show 2 more comments
So it doesn't open a command line, it just freezes and you cannot input anything, right?
– edwin
Jun 23 '13 at 23:54
Boot the livecd and runsudo fdisk -lu
and edit your question to show the output.
– psusi
Jun 24 '13 at 1:47
Try rebooting into recovery mode and select repair packages.
– Mitch♦
Jun 24 '13 at 5:35
@edwin , that's right.
– rux
Jun 24 '13 at 22:35
1
Could please start a live DVD/USB, mount all the internal file systems, rundf -h
anddf -i
and include the output in your question? That should provide more insight into what exactly might be "full" here.
– David Foerster
Sep 8 '16 at 18:20
So it doesn't open a command line, it just freezes and you cannot input anything, right?
– edwin
Jun 23 '13 at 23:54
So it doesn't open a command line, it just freezes and you cannot input anything, right?
– edwin
Jun 23 '13 at 23:54
Boot the livecd and run
sudo fdisk -lu
and edit your question to show the output.– psusi
Jun 24 '13 at 1:47
Boot the livecd and run
sudo fdisk -lu
and edit your question to show the output.– psusi
Jun 24 '13 at 1:47
Try rebooting into recovery mode and select repair packages.
– Mitch♦
Jun 24 '13 at 5:35
Try rebooting into recovery mode and select repair packages.
– Mitch♦
Jun 24 '13 at 5:35
@edwin , that's right.
– rux
Jun 24 '13 at 22:35
@edwin , that's right.
– rux
Jun 24 '13 at 22:35
1
1
Could please start a live DVD/USB, mount all the internal file systems, run
df -h
and df -i
and include the output in your question? That should provide more insight into what exactly might be "full" here.– David Foerster
Sep 8 '16 at 18:20
Could please start a live DVD/USB, mount all the internal file systems, run
df -h
and df -i
and include the output in your question? That should provide more insight into what exactly might be "full" here.– David Foerster
Sep 8 '16 at 18:20
|
show 2 more comments
2 Answers
2
active
oldest
votes
I believe you've upgraded many times, and you have a lot of old linux kernals filling up your grub partition.
I think you're going to have to boot from a live DVD or USB, mount the HDs boot partition, see if it is indeed full, and if that's the case, manually delete a couple of old kernals.
If you haven't got a backup, you might copy your ~/ to a safe place first.
This is grub saying that the filesystem extends beyond the end of the disk and thus can not be read, not that it is full.
– psusi
Jun 24 '13 at 1:48
@marc, how do i mount the HDs boot partition and manually delete kernals?
– rux
Jun 25 '13 at 21:21
add a comment |
Start with a Live-Usb.
Completed load session:
Open a terminal.
Press Ctrl+Alt+T
Run it:
sudo -i
umount /dev/sda5
fsck -y /dev/sda5
umount /dev/sda6
fsck -y /dev/sda6
mount /dev/sda5 /mnt
mount --bind /dev /mnt/dev
mount --bind /dev/pts /mnt/dev/pts
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
chroot /mnt
apt-get update
apt-get autoremove
apt-get clean
UNUSCONF=$(dpkg -l|grep "^rc"|awk '{print $2}')
apt-get remove --purge $UNUSCONF
NEWKERNEL=$(uname -r|sed 's/-*[a-z]//g'|sed 's/-386//g')
ADDKERNEL="linux-(image|headers|ubuntu-modules|restricted-modules)"
METAKERNEL="linux-(image|headers|restricted-modules)-(generic|i386|server|common|rt|xen)"
UNUSKERNELS=$(dpkg -l|awk '{print $2}'|grep -E $ADDKERNEL |grep -vE $METAKERNEL|grep -v $NEWKERNEL)
apt-get remove --purge $UNUSKERNELS
grub-install --root-directory=/mnt /dev/sda
grub-install --recheck /dev/sda
umount /mnt
reboot
add a comment |
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',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f311925%2fhow-can-i-fix-error-hd0-out-of-disk%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I believe you've upgraded many times, and you have a lot of old linux kernals filling up your grub partition.
I think you're going to have to boot from a live DVD or USB, mount the HDs boot partition, see if it is indeed full, and if that's the case, manually delete a couple of old kernals.
If you haven't got a backup, you might copy your ~/ to a safe place first.
This is grub saying that the filesystem extends beyond the end of the disk and thus can not be read, not that it is full.
– psusi
Jun 24 '13 at 1:48
@marc, how do i mount the HDs boot partition and manually delete kernals?
– rux
Jun 25 '13 at 21:21
add a comment |
I believe you've upgraded many times, and you have a lot of old linux kernals filling up your grub partition.
I think you're going to have to boot from a live DVD or USB, mount the HDs boot partition, see if it is indeed full, and if that's the case, manually delete a couple of old kernals.
If you haven't got a backup, you might copy your ~/ to a safe place first.
This is grub saying that the filesystem extends beyond the end of the disk and thus can not be read, not that it is full.
– psusi
Jun 24 '13 at 1:48
@marc, how do i mount the HDs boot partition and manually delete kernals?
– rux
Jun 25 '13 at 21:21
add a comment |
I believe you've upgraded many times, and you have a lot of old linux kernals filling up your grub partition.
I think you're going to have to boot from a live DVD or USB, mount the HDs boot partition, see if it is indeed full, and if that's the case, manually delete a couple of old kernals.
If you haven't got a backup, you might copy your ~/ to a safe place first.
I believe you've upgraded many times, and you have a lot of old linux kernals filling up your grub partition.
I think you're going to have to boot from a live DVD or USB, mount the HDs boot partition, see if it is indeed full, and if that's the case, manually delete a couple of old kernals.
If you haven't got a backup, you might copy your ~/ to a safe place first.
edited Jun 24 '13 at 0:06
answered Jun 23 '13 at 23:46
MarcMarc
5,93321227
5,93321227
This is grub saying that the filesystem extends beyond the end of the disk and thus can not be read, not that it is full.
– psusi
Jun 24 '13 at 1:48
@marc, how do i mount the HDs boot partition and manually delete kernals?
– rux
Jun 25 '13 at 21:21
add a comment |
This is grub saying that the filesystem extends beyond the end of the disk and thus can not be read, not that it is full.
– psusi
Jun 24 '13 at 1:48
@marc, how do i mount the HDs boot partition and manually delete kernals?
– rux
Jun 25 '13 at 21:21
This is grub saying that the filesystem extends beyond the end of the disk and thus can not be read, not that it is full.
– psusi
Jun 24 '13 at 1:48
This is grub saying that the filesystem extends beyond the end of the disk and thus can not be read, not that it is full.
– psusi
Jun 24 '13 at 1:48
@marc, how do i mount the HDs boot partition and manually delete kernals?
– rux
Jun 25 '13 at 21:21
@marc, how do i mount the HDs boot partition and manually delete kernals?
– rux
Jun 25 '13 at 21:21
add a comment |
Start with a Live-Usb.
Completed load session:
Open a terminal.
Press Ctrl+Alt+T
Run it:
sudo -i
umount /dev/sda5
fsck -y /dev/sda5
umount /dev/sda6
fsck -y /dev/sda6
mount /dev/sda5 /mnt
mount --bind /dev /mnt/dev
mount --bind /dev/pts /mnt/dev/pts
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
chroot /mnt
apt-get update
apt-get autoremove
apt-get clean
UNUSCONF=$(dpkg -l|grep "^rc"|awk '{print $2}')
apt-get remove --purge $UNUSCONF
NEWKERNEL=$(uname -r|sed 's/-*[a-z]//g'|sed 's/-386//g')
ADDKERNEL="linux-(image|headers|ubuntu-modules|restricted-modules)"
METAKERNEL="linux-(image|headers|restricted-modules)-(generic|i386|server|common|rt|xen)"
UNUSKERNELS=$(dpkg -l|awk '{print $2}'|grep -E $ADDKERNEL |grep -vE $METAKERNEL|grep -v $NEWKERNEL)
apt-get remove --purge $UNUSKERNELS
grub-install --root-directory=/mnt /dev/sda
grub-install --recheck /dev/sda
umount /mnt
reboot
add a comment |
Start with a Live-Usb.
Completed load session:
Open a terminal.
Press Ctrl+Alt+T
Run it:
sudo -i
umount /dev/sda5
fsck -y /dev/sda5
umount /dev/sda6
fsck -y /dev/sda6
mount /dev/sda5 /mnt
mount --bind /dev /mnt/dev
mount --bind /dev/pts /mnt/dev/pts
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
chroot /mnt
apt-get update
apt-get autoremove
apt-get clean
UNUSCONF=$(dpkg -l|grep "^rc"|awk '{print $2}')
apt-get remove --purge $UNUSCONF
NEWKERNEL=$(uname -r|sed 's/-*[a-z]//g'|sed 's/-386//g')
ADDKERNEL="linux-(image|headers|ubuntu-modules|restricted-modules)"
METAKERNEL="linux-(image|headers|restricted-modules)-(generic|i386|server|common|rt|xen)"
UNUSKERNELS=$(dpkg -l|awk '{print $2}'|grep -E $ADDKERNEL |grep -vE $METAKERNEL|grep -v $NEWKERNEL)
apt-get remove --purge $UNUSKERNELS
grub-install --root-directory=/mnt /dev/sda
grub-install --recheck /dev/sda
umount /mnt
reboot
add a comment |
Start with a Live-Usb.
Completed load session:
Open a terminal.
Press Ctrl+Alt+T
Run it:
sudo -i
umount /dev/sda5
fsck -y /dev/sda5
umount /dev/sda6
fsck -y /dev/sda6
mount /dev/sda5 /mnt
mount --bind /dev /mnt/dev
mount --bind /dev/pts /mnt/dev/pts
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
chroot /mnt
apt-get update
apt-get autoremove
apt-get clean
UNUSCONF=$(dpkg -l|grep "^rc"|awk '{print $2}')
apt-get remove --purge $UNUSCONF
NEWKERNEL=$(uname -r|sed 's/-*[a-z]//g'|sed 's/-386//g')
ADDKERNEL="linux-(image|headers|ubuntu-modules|restricted-modules)"
METAKERNEL="linux-(image|headers|restricted-modules)-(generic|i386|server|common|rt|xen)"
UNUSKERNELS=$(dpkg -l|awk '{print $2}'|grep -E $ADDKERNEL |grep -vE $METAKERNEL|grep -v $NEWKERNEL)
apt-get remove --purge $UNUSKERNELS
grub-install --root-directory=/mnt /dev/sda
grub-install --recheck /dev/sda
umount /mnt
reboot
Start with a Live-Usb.
Completed load session:
Open a terminal.
Press Ctrl+Alt+T
Run it:
sudo -i
umount /dev/sda5
fsck -y /dev/sda5
umount /dev/sda6
fsck -y /dev/sda6
mount /dev/sda5 /mnt
mount --bind /dev /mnt/dev
mount --bind /dev/pts /mnt/dev/pts
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
chroot /mnt
apt-get update
apt-get autoremove
apt-get clean
UNUSCONF=$(dpkg -l|grep "^rc"|awk '{print $2}')
apt-get remove --purge $UNUSCONF
NEWKERNEL=$(uname -r|sed 's/-*[a-z]//g'|sed 's/-386//g')
ADDKERNEL="linux-(image|headers|ubuntu-modules|restricted-modules)"
METAKERNEL="linux-(image|headers|restricted-modules)-(generic|i386|server|common|rt|xen)"
UNUSKERNELS=$(dpkg -l|awk '{print $2}'|grep -E $ADDKERNEL |grep -vE $METAKERNEL|grep -v $NEWKERNEL)
apt-get remove --purge $UNUSKERNELS
grub-install --root-directory=/mnt /dev/sda
grub-install --recheck /dev/sda
umount /mnt
reboot
answered May 31 '15 at 16:39
kyodakekyodake
9,66011932
9,66011932
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f311925%2fhow-can-i-fix-error-hd0-out-of-disk%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
So it doesn't open a command line, it just freezes and you cannot input anything, right?
– edwin
Jun 23 '13 at 23:54
Boot the livecd and run
sudo fdisk -lu
and edit your question to show the output.– psusi
Jun 24 '13 at 1:47
Try rebooting into recovery mode and select repair packages.
– Mitch♦
Jun 24 '13 at 5:35
@edwin , that's right.
– rux
Jun 24 '13 at 22:35
1
Could please start a live DVD/USB, mount all the internal file systems, run
df -h
anddf -i
and include the output in your question? That should provide more insight into what exactly might be "full" here.– David Foerster
Sep 8 '16 at 18:20