Unable to Boot: error couldn't read file
I have installed Ubuntu 12.04 LTS on an IBM Thinkpad T41.
Up until Linux 3.2.0-30
generic everything was working fine. I accept all the software update.
With 3.2.0-31
generic the machine freezes and I get the error:
error couldn't read file
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
With 3.2.0-32
, the
error: Cannot read the Linux header
then the machine returns to the Grub menu
3.2.0-30
still works fine if I select that.
12.04 boot
bumped to the homepage by Community♦ 6 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have installed Ubuntu 12.04 LTS on an IBM Thinkpad T41.
Up until Linux 3.2.0-30
generic everything was working fine. I accept all the software update.
With 3.2.0-31
generic the machine freezes and I get the error:
error couldn't read file
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
With 3.2.0-32
, the
error: Cannot read the Linux header
then the machine returns to the Grub menu
3.2.0-30
still works fine if I select that.
12.04 boot
bumped to the homepage by Community♦ 6 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have installed Ubuntu 12.04 LTS on an IBM Thinkpad T41.
Up until Linux 3.2.0-30
generic everything was working fine. I accept all the software update.
With 3.2.0-31
generic the machine freezes and I get the error:
error couldn't read file
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
With 3.2.0-32
, the
error: Cannot read the Linux header
then the machine returns to the Grub menu
3.2.0-30
still works fine if I select that.
12.04 boot
I have installed Ubuntu 12.04 LTS on an IBM Thinkpad T41.
Up until Linux 3.2.0-30
generic everything was working fine. I accept all the software update.
With 3.2.0-31
generic the machine freezes and I get the error:
error couldn't read file
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
With 3.2.0-32
, the
error: Cannot read the Linux header
then the machine returns to the Grub menu
3.2.0-30
still works fine if I select that.
12.04 boot
12.04 boot
edited Oct 28 '12 at 11:36
Peachy
4,92672843
4,92672843
asked Oct 28 '12 at 9:26
Will WatsonWill Watson
1112
1112
bumped to the homepage by Community♦ 6 hours 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♦ 6 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Having the same error message on an old PC after a kernel update; 3.2.0-69 still works, 3.2.0-70 does not.
I suspect it is caused by the fact that the 3.2.0-70 files in folder /boot
are located above the 128 GB limit imposed by many an old BIOS.
I used filefrag
to get an idea about the physical location on disk of the files involved.
Just guessing here: with a block size of 4KB, a value of 32,000,000 in column physical
suggests the file is located near the 128 GB boundary.
Notice how the 3.2.0-69 files are well below that value, whereas the 3.2.0-70 files are above.
$ filefrag -v /boot/*{69,70}*
Filesystem type is: ef53
File size of /boot/abi-3.2.0-69-generic-pae is 805150 (197 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 7548416 197 eof
/boot/abi-3.2.0-69-generic-pae: 1 extent found
File size of /boot/config-3.2.0-69-generic-pae is 147622 (37 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 7542592 37 eof
/boot/config-3.2.0-69-generic-pae: 1 extent found
File size of /boot/initrd.img-3.2.0-69-generic-pae is 16593585 (4052 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 26466304 4052 eof
/boot/initrd.img-3.2.0-69-generic-pae: 1 extent found
open: Permission denied
open: Permission denied
File size of /boot/abi-3.2.0-70-generic-pae is 805201 (197 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 38547712 197 eof
/boot/abi-3.2.0-70-generic-pae: 1 extent found
File size of /boot/config-3.2.0-70-generic-pae is 147652 (37 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 38550848 37 eof
/boot/config-3.2.0-70-generic-pae: 1 extent found
File size of /boot/initrd.img-3.2.0-70-generic-pae is 16592761 (4051 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 38588416 4051 eof
/boot/initrd.img-3.2.0-70-generic-pae: 1 extent found
open: Permission denied
open: Permission denied
So how to relocate the files to a safer zone? You might try these steps:
- Clean up your HDD; delete some big, old files in an attempt to make room for the boot files.
- Copy each boot file.
- Delete the original boot files.
- Rename/move the copied files to match the names of the original files.
A more reliable and structural solution is to repartion your HDD; make sure folder /boot
is in a partition that is located below the 128 GB boundary.
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%2f207565%2funable-to-boot-error-couldnt-read-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Having the same error message on an old PC after a kernel update; 3.2.0-69 still works, 3.2.0-70 does not.
I suspect it is caused by the fact that the 3.2.0-70 files in folder /boot
are located above the 128 GB limit imposed by many an old BIOS.
I used filefrag
to get an idea about the physical location on disk of the files involved.
Just guessing here: with a block size of 4KB, a value of 32,000,000 in column physical
suggests the file is located near the 128 GB boundary.
Notice how the 3.2.0-69 files are well below that value, whereas the 3.2.0-70 files are above.
$ filefrag -v /boot/*{69,70}*
Filesystem type is: ef53
File size of /boot/abi-3.2.0-69-generic-pae is 805150 (197 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 7548416 197 eof
/boot/abi-3.2.0-69-generic-pae: 1 extent found
File size of /boot/config-3.2.0-69-generic-pae is 147622 (37 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 7542592 37 eof
/boot/config-3.2.0-69-generic-pae: 1 extent found
File size of /boot/initrd.img-3.2.0-69-generic-pae is 16593585 (4052 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 26466304 4052 eof
/boot/initrd.img-3.2.0-69-generic-pae: 1 extent found
open: Permission denied
open: Permission denied
File size of /boot/abi-3.2.0-70-generic-pae is 805201 (197 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 38547712 197 eof
/boot/abi-3.2.0-70-generic-pae: 1 extent found
File size of /boot/config-3.2.0-70-generic-pae is 147652 (37 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 38550848 37 eof
/boot/config-3.2.0-70-generic-pae: 1 extent found
File size of /boot/initrd.img-3.2.0-70-generic-pae is 16592761 (4051 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 38588416 4051 eof
/boot/initrd.img-3.2.0-70-generic-pae: 1 extent found
open: Permission denied
open: Permission denied
So how to relocate the files to a safer zone? You might try these steps:
- Clean up your HDD; delete some big, old files in an attempt to make room for the boot files.
- Copy each boot file.
- Delete the original boot files.
- Rename/move the copied files to match the names of the original files.
A more reliable and structural solution is to repartion your HDD; make sure folder /boot
is in a partition that is located below the 128 GB boundary.
add a comment |
Having the same error message on an old PC after a kernel update; 3.2.0-69 still works, 3.2.0-70 does not.
I suspect it is caused by the fact that the 3.2.0-70 files in folder /boot
are located above the 128 GB limit imposed by many an old BIOS.
I used filefrag
to get an idea about the physical location on disk of the files involved.
Just guessing here: with a block size of 4KB, a value of 32,000,000 in column physical
suggests the file is located near the 128 GB boundary.
Notice how the 3.2.0-69 files are well below that value, whereas the 3.2.0-70 files are above.
$ filefrag -v /boot/*{69,70}*
Filesystem type is: ef53
File size of /boot/abi-3.2.0-69-generic-pae is 805150 (197 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 7548416 197 eof
/boot/abi-3.2.0-69-generic-pae: 1 extent found
File size of /boot/config-3.2.0-69-generic-pae is 147622 (37 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 7542592 37 eof
/boot/config-3.2.0-69-generic-pae: 1 extent found
File size of /boot/initrd.img-3.2.0-69-generic-pae is 16593585 (4052 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 26466304 4052 eof
/boot/initrd.img-3.2.0-69-generic-pae: 1 extent found
open: Permission denied
open: Permission denied
File size of /boot/abi-3.2.0-70-generic-pae is 805201 (197 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 38547712 197 eof
/boot/abi-3.2.0-70-generic-pae: 1 extent found
File size of /boot/config-3.2.0-70-generic-pae is 147652 (37 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 38550848 37 eof
/boot/config-3.2.0-70-generic-pae: 1 extent found
File size of /boot/initrd.img-3.2.0-70-generic-pae is 16592761 (4051 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 38588416 4051 eof
/boot/initrd.img-3.2.0-70-generic-pae: 1 extent found
open: Permission denied
open: Permission denied
So how to relocate the files to a safer zone? You might try these steps:
- Clean up your HDD; delete some big, old files in an attempt to make room for the boot files.
- Copy each boot file.
- Delete the original boot files.
- Rename/move the copied files to match the names of the original files.
A more reliable and structural solution is to repartion your HDD; make sure folder /boot
is in a partition that is located below the 128 GB boundary.
add a comment |
Having the same error message on an old PC after a kernel update; 3.2.0-69 still works, 3.2.0-70 does not.
I suspect it is caused by the fact that the 3.2.0-70 files in folder /boot
are located above the 128 GB limit imposed by many an old BIOS.
I used filefrag
to get an idea about the physical location on disk of the files involved.
Just guessing here: with a block size of 4KB, a value of 32,000,000 in column physical
suggests the file is located near the 128 GB boundary.
Notice how the 3.2.0-69 files are well below that value, whereas the 3.2.0-70 files are above.
$ filefrag -v /boot/*{69,70}*
Filesystem type is: ef53
File size of /boot/abi-3.2.0-69-generic-pae is 805150 (197 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 7548416 197 eof
/boot/abi-3.2.0-69-generic-pae: 1 extent found
File size of /boot/config-3.2.0-69-generic-pae is 147622 (37 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 7542592 37 eof
/boot/config-3.2.0-69-generic-pae: 1 extent found
File size of /boot/initrd.img-3.2.0-69-generic-pae is 16593585 (4052 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 26466304 4052 eof
/boot/initrd.img-3.2.0-69-generic-pae: 1 extent found
open: Permission denied
open: Permission denied
File size of /boot/abi-3.2.0-70-generic-pae is 805201 (197 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 38547712 197 eof
/boot/abi-3.2.0-70-generic-pae: 1 extent found
File size of /boot/config-3.2.0-70-generic-pae is 147652 (37 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 38550848 37 eof
/boot/config-3.2.0-70-generic-pae: 1 extent found
File size of /boot/initrd.img-3.2.0-70-generic-pae is 16592761 (4051 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 38588416 4051 eof
/boot/initrd.img-3.2.0-70-generic-pae: 1 extent found
open: Permission denied
open: Permission denied
So how to relocate the files to a safer zone? You might try these steps:
- Clean up your HDD; delete some big, old files in an attempt to make room for the boot files.
- Copy each boot file.
- Delete the original boot files.
- Rename/move the copied files to match the names of the original files.
A more reliable and structural solution is to repartion your HDD; make sure folder /boot
is in a partition that is located below the 128 GB boundary.
Having the same error message on an old PC after a kernel update; 3.2.0-69 still works, 3.2.0-70 does not.
I suspect it is caused by the fact that the 3.2.0-70 files in folder /boot
are located above the 128 GB limit imposed by many an old BIOS.
I used filefrag
to get an idea about the physical location on disk of the files involved.
Just guessing here: with a block size of 4KB, a value of 32,000,000 in column physical
suggests the file is located near the 128 GB boundary.
Notice how the 3.2.0-69 files are well below that value, whereas the 3.2.0-70 files are above.
$ filefrag -v /boot/*{69,70}*
Filesystem type is: ef53
File size of /boot/abi-3.2.0-69-generic-pae is 805150 (197 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 7548416 197 eof
/boot/abi-3.2.0-69-generic-pae: 1 extent found
File size of /boot/config-3.2.0-69-generic-pae is 147622 (37 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 7542592 37 eof
/boot/config-3.2.0-69-generic-pae: 1 extent found
File size of /boot/initrd.img-3.2.0-69-generic-pae is 16593585 (4052 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 26466304 4052 eof
/boot/initrd.img-3.2.0-69-generic-pae: 1 extent found
open: Permission denied
open: Permission denied
File size of /boot/abi-3.2.0-70-generic-pae is 805201 (197 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 38547712 197 eof
/boot/abi-3.2.0-70-generic-pae: 1 extent found
File size of /boot/config-3.2.0-70-generic-pae is 147652 (37 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 38550848 37 eof
/boot/config-3.2.0-70-generic-pae: 1 extent found
File size of /boot/initrd.img-3.2.0-70-generic-pae is 16592761 (4051 blocks, blocksize 4096)
ext logical physical expected length flags
0 0 38588416 4051 eof
/boot/initrd.img-3.2.0-70-generic-pae: 1 extent found
open: Permission denied
open: Permission denied
So how to relocate the files to a safer zone? You might try these steps:
- Clean up your HDD; delete some big, old files in an attempt to make room for the boot files.
- Copy each boot file.
- Delete the original boot files.
- Rename/move the copied files to match the names of the original files.
A more reliable and structural solution is to repartion your HDD; make sure folder /boot
is in a partition that is located below the 128 GB boundary.
answered Oct 11 '14 at 21:33
Ruud HeldermanRuud Helderman
32127
32127
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.
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%2f207565%2funable-to-boot-error-couldnt-read-file%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