After updates, no boot
10.4 installed. upgraded kernel and added MySql and HTTP. Upon reboot get "invalid magic number. you need to load the kernel first. Failed to boot both default and failback entries."
I booted from the CD and was able to mount the volume and see all the files. fsck didn't show any problems. What do I do short of a full install.
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu grub2 Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- delance
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
I'm afraid it is not a grub2 issue.
Please, try previous kernel to check if it is a kernel issue.
You can try:
https:/
Are you in dual boot or do you use Wubi ?
Can you post result of "ls /boot/vmlinuz*" ?
Revision history for this message
|
#2 |
delance wrote:
> Your question #120905 on grub2 in ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> delance proposed the following answer:
> I'm afraid it is not a grub2 issue.
> Please, try previous kernel to check if it is a kernel issue.
> You can try:
> https:/
> Are you in dual boot or do you use Wubi ?
> Can you post result of "ls /boot/vmlinuz*" ?
>
>
I don't know how to try the previous kernel.
I do not dual boot.
I followed the instructions in the website, but still no boot and same
error.
ls -l shows linuz is a link to linuz-2.
Revision history for this message
|
#3 |
to try previous kernel please press shift at pc boot and select from the grub rows...
Revision history for this message
|
#4 |
I'm having this problem. The newest kernel, that becomes the grub-pc default, gives:
"Invalid magic number" and does not boot.
Not friendly.
Do not mess with your grub (2) like I did. Reinstalling GRUB 2 failed. I just now fixed my GRUB 2. It was hell. I can tell you the new kernel did not work with grub legacy either (old kernel does too).
I was getting "Bad magic number" after upgrade.
All I did was agree to the upgrade-manager.
GRUB legacy gave an Error 13 (on the new kernel *-24).
2.6.32-24-generic fails as described.
What's going on?
Revision history for this message
|
#5 |
"Space" to get grub rows produced zip! Same error "Bad magic number". Corrupt kernel?
Revision history for this message
|
#6 |
I'm not quite sure, but if I remember if you press <Shift> at boot, Grub2 should display a menu.
If it is the case, try previous kernel.
Else with Synaptic, you could remove least kernel (before, check you already have previous kernel).
Revision history for this message
|
#7 |
<Shift> does NOT display a menu.
Can I run Synaptic from the boot CD on the kernel on the mounted FS?
Revision history for this message
|
#8 |
I've just tried on a virtual machine, and it works, so could you try again.
No, you can't run Synaptic from the boot CD. If you try it, you will update in the pseudo HDD in RAM, and not in your real hard drive.
Revision history for this message
|
#9 |
Negative on <Shift> at boot, still "Bad Magic Number". Did the update trash the boot sector on the disk?
Revision history for this message
|
#10 |
It should not.
Are you using Wubi or is Ubuntu the single OS on this computer ?
You can try:
https:/
If you need help on reinstalling, please post result of "sudo parted -l".
Revision history for this message
|
#11 |
ubuntu is the ONLY OS on the computer.
Which of the methods should I follow?
I've already tried method "SIMPLEST"
/dev/sda, / is on sda1
Revision history for this message
|
#12 |
I have read Grub documentation. <Shift> is the normal way to get menu, but you can also use <Esc>.
Another way to get hand on Grub is to use Live CD, like in:
https:/
but you need method 3 (the most complicated)
Have a look in:
https:/
You have to edit file /etc/default/grub, and to add '#' before GRUB_HIDDEN_
Do this before step 8.
I will investigate on your error message this evening.
Revision history for this message
|
#13 |
<Esc> didn't work either. I'll look into the next steps later today.
Revision history for this message
|
#14 |
I went through Google. It seems Grub is unable to load specified kernel image.
So could you use Live CD and:
1) post section "### BEGIN /etc/grub.
2) post result of command "ls -l /boot/*vmlinuz*"
Don't forget I need files on real HDD, so you have to mount sda1 and search into it.
Revision history for this message
|
#15 |
OK, I'll try that first, but later today.
Revision history for this message
|
#16 |
As requested:
1)
### BEGIN /etc/grub.
menuentry 'Ubuntu, with Linux 2.6.32-308-ec2' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-308-ec2 (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
echo 'Loading Linux 2.6.32-308-ec2 ...'
linux /boot/vmlinuz-
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-307-ec2' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-307-ec2 (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
echo 'Loading Linux 2.6.32-307-ec2 ...'
linux /boot/vmlinuz-
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-306-ec2' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-306-ec2 (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
echo 'Loading Linux 2.6.32-306-ec2 ...'
linux /boot/vmlinuz-
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-305-ec2' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-305-ec2 (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
echo 'Loading Linux 2.6.32-305-ec2 ...'
linux /boot/vmlinuz-
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
echo 'Loading Linux 2.6.32-
linux /boot/vmlinuz-
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
echo 'Loading Linux 2.6.32-24-generic ...'
linux /boot/vmlinuz-
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-24-386' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-24-386 (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
echo 'Loading Linux 2.6.32-24-386 ...'
linux /boot/vmlinuz-
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
echo 'Loading Linux 2.6.32-
linux /boot/vmlinuz-
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-23-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-23-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
echo 'Loading Linux 2.6.32-23-generic ...'
linux /boot/vmlinuz-
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-23-386' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-23-386 (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
echo 'Loading Linux 2.6.32-23-386 ...'
linux /boot/vmlinuz-
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
echo 'Loading Linux 2.6.32-
linux /boot/vmlinuz-
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
echo 'Loading Linux 2.6.32-22-generic ...'
linux /boot/vmlinuz-
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-22-386' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-22-386 (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
echo 'Loading Linux 2.6.32-22-386 ...'
linux /boot/vmlinuz-
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
echo 'Loading Linux 2.6.32-
linux /boot/vmlinuz-
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-21-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-21-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
echo 'Loading Linux 2.6.32-21-generic ...'
linux /boot/vmlinuz-
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-21-386' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry 'Ubuntu, with Linux 2.6.32-21-386 (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set bc957427-
echo 'Loading Linux 2.6.32-21-386 ...'
linux /boot/vmlinuz-
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.
}
### END /etc/grub.
2)
-rw-r--r-- 1 root root 3976992 2010-04-16 13:41 boot/vmlinuz-
-rw-r--r-- 1 root root 4029792 2010-04-16 13:01 boot/vmlinuz-
-rw-r--r-- 1 root root 4159008 2010-04-16 13:21 boot/vmlinuz-
-rw-r--r-- 1 root root 3977216 2010-06-04 02:32 boot/vmlinuz-
-rw-r--r-- 1 root root 4030048 2010-06-04 01:56 boot/vmlinuz-
-rw-r--r-- 1 root root 4158816 2010-06-04 02:13 boot/vmlinuz-
-rw-r--r-- 1 root root 3983936 2010-06-11 13:35 boot/vmlinuz-
-rw-r--r-- 1 root root 4031552 2010-06-11 12:53 boot/vmlinuz-
-rw-r--r-- 1 root root 4164704 2010-06-11 13:14 boot/vmlinuz-
-rw-r--r-- 1 root root 3987200 2010-07-05 15:00 boot/vmlinuz-
-rw-r--r-- 1 root root 4033472 2010-07-05 14:19 boot/vmlinuz-
-rw-r--r-- 1 root root 4167616 2010-07-05 14:39 boot/vmlinuz-
-rw-r--r-- 1 root root 3120507 2010-04-15 05:12 boot/vmlinuz-
-rw-r--r-- 1 root root 3147464 2010-06-01 15:18 boot/vmlinuz-
-rw-r--r-- 1 root root 3148230 2010-06-18 11:36 boot/vmlinuz-
-rw-r--r-- 1 root root 3150301 2010-07-08 17:52 boot/vmlinuz-
Revision history for this message
|
#17 |
1)
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
linux /boot/vmlinuz-
2)
-rw-r--r-- 1 root root 3976992 2010-04-16 13:41 boot/vmlinuz-
-rw-r--r-- 1 root root 4029792 2010-04-16 13:01 boot/vmlinuz-
-rw-r--r-- 1 root root 4159008 2010-04-16 13:21 boot/vmlinuz-
-rw-r--r-- 1 root root 3977216 2010-06-04 02:32 boot/vmlinuz-
-rw-r--r-- 1 root root 4030048 2010-06-04 01:56 boot/vmlinuz-
-rw-r--r-- 1 root root 4158816 2010-06-04 02:13 boot/vmlinuz-
-rw-r--r-- 1 root root 3983936 2010-06-11 13:35 boot/vmlinuz-
-rw-r--r-- 1 root root 4031552 2010-06-11 12:53 boot/vmlinuz-
-rw-r--r-- 1 root root 4164704 2010-06-11 13:14 boot/vmlinuz-
-rw-r--r-- 1 root root 3987200 2010-07-05 15:00 boot/vmlinuz-
-rw-r--r-- 1 root root 4033472 2010-07-05 14:19 boot/vmlinuz-
-rw-r--r-- 1 root root 4167616 2010-07-05 14:39 boot/vmlinuz-
-rw-r--r-- 1 root root 3120507 2010-04-15 05:12 boot/vmlinuz-
-rw-r--r-- 1 root root 3147464 2010-06-01 15:18 boot/vmlinuz-
-rw-r--r-- 1 root root 3148230 2010-06-18 11:36 boot/vmlinuz-
-rw-r--r-- 1 root root 3150301 2010-07-08 17:52 boot/vmlinuz-
Revision history for this message
|
#18 |
You boot by default at a non standard Linux kernel:
Are you using Xen software ?
-------
http://
Ubuntu 9.10 Templates
Method Details
Default Kernel Will not boot <<<<<<<
XENPVOS Options
32 and 64-bit "vmlinuz-
"vmlinuz-
Pygrub Works
Ubuntu 10.04 Templates
Method Details
Default Kernel Will not boot <<<<<<<
XENPVOS Options "vmlinuz-
Pygrub Works
Revision history for this message
|
#19 |
I don't even know what a ZEN is. I just added http and MySQL. I may have agreed to have the kernel updateds added, don't remember. I used the terminal screen update tool to do the work.
Do I need to change the cfg file to point to the generic kernel or what?
Revision history for this message
|
#20 |
Look strange.
Make a backup of file /boot/grub/
Be careful, if it works, we will have other things to do, else problem could go back!
Revision history for this message
|
#22 |
delance wrote:
> Your question #120905 on grub2 in ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> delance proposed the following answer:
> Look strange.
> Make a backup of file /boot/grub/
> Be careful, if it works, we will have other things to do, else problem could go back!
>
deleted the "ec2" lines. Rebooted and now it comes up to the ubuntu
screen, the hardwired printer reacts and the dots on the screen go from
white to red and back again and that's all it does.
Revision history for this message
|
#23 |
1) Make a backup of file /boot/grub/grub.cfg
2) sudo grub-install
3) check grub has not added again "ec2" kernel. If it did, revert to backup file. If not, please mark question solved (and mark which answer solved the question).
Revision history for this message
|
#24 |
delance wrote:
> Your question #120905 on grub2 in ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> delance proposed the following answer:
> 1) Make a backup of file /boot/grub/grub.cfg
> 2) sudo grub-install
> 3) check grub has not added again "ec2" kernel. If it did, revert to backup file. If not, please mark question solved (and mark which answer solved the question).
>
>
The boot from the hard drive never completed. Can I run grub-install
from the CD boot and update the grub.cfg on the mounted disc?
Revision history for this message
|
#25 |
It will be easier to boot from hard disk in Ubuntu, and make "sudo grub-install".
But before upgrading grub, do a backup of grub.cfg.
After upgrading, check what is the first kernel image used.
If it is an ec2, restore from backup.
Else mark question as solved.
Revision history for this message
|
#26 |
delance wrote:
> Your question #120905 on grub2 in ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> delance proposed the following answer:
> It will be easier to boot from hard disk in Ubuntu, and make "sudo grub-install".
> But before upgrading grub, do a backup of grub.cfg.
> After upgrading, check what is the first kernel image used.
> If it is an ec2, restore from backup.
> Else mark question as solved.
>
>
It will NOT boot!!! It starts and then just sits there marching through
the dots on the initial Ubuntu boot screen!!!!
Revision history for this message
|
#27 |
Sorry, I misread. It seems you have a second problem.
When you the five dots, press key <Esc>, you should see a terminal.
What is the last displayed line (I will be not surprised it is "battery", which is just before graphic). ?
Revision history for this message
|
#28 |
delance wrote:
> Your question #120905 on grub2 in ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> delance proposed the following answer:
> Sorry, I misread. It seems you have a second problem.
> When you the five dots, press key <Esc>, you should see a terminal.
> What is the last displayed line (I will be not surprised it is "battery", which is just before graphic). ?
>
>
OK, will try later and post last line.
Revision history for this message
|
#29 |
delance wrote:
> Your question #120905 on grub2 in ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> delance proposed the following answer:
> Sorry, I misread. It seems you have a second problem.
> When you the five dots, press key <Esc>, you should see a terminal.
> What is the last displayed line (I will be not surprised it is "battery", which is just before graphic). ?
>
>
init: eucalyptus-network (lo) main process killed by TERM signal
I tried a different NIC on the computer, same error.
When booting from CD it accesses the network with no problems. It also
complained about not finding some kind of a path/file for what looked
like the printer port.
Are we getting to the point where I should just boot from the CD, save
any specific data, files, settings and just re-install.
I don't want to go through this again so is there a utility to make a
recovery disk with last known good configuration that can recover from
another one of these updates?
Revision history for this message
|
#30 |
1) "Are we getting to the point where I should just boot from the CD, save any specific data, files, settings and just re-install."
Perhaps, I have currently no idea what is the problem and we could have to investigate a lot. So a fresh install could be faster.
2) "is there a utility to make a recovery disk with last known good configuration that can recover from another one of these updates?"
Don't know such a tool, but a backup of directory "/boot" should be enough as Grub uses only this directory to launch Linux init.
Revision history for this message
|
#31 |
Is your problem solved ? If not I can try to help, else, please, could you mark question "Solved".
Revision history for this message
|
#32 |
I reinstalled ubuntu and almost have it to a satisfactory start point before I go on. I found a utility called "clonezilla" that is suppose to make a clone of the system and will restore the entire disc, I haven't tried it yet but I plan to do so shortly.
Revision history for this message
|
#33 |
See my Bug #613967 for the same as below. (In my case)
Summary:
I solved it, by turning off UDMA, in my computers BIOS; so that GRUB(2) would get the right UDMA mode, directly from my drive. I hear some BIOS(es) can be set to the WRONG UDMA mode, and that forces GRUB to get the right UDMA mode, and boot, instead of the error, "Invalid magic number". It was previously, "Bad magic number".
Some computer have this problem.
Grub(2) might solve it by checking with the drive.
Something about this kernel build must have been overlooked. It could be fixed there too; because other kernel worked; without my BIOS, UDMA adjustment.