Debian :: 'INVALID Magic Number' - Grub2
May 6, 2011I get error 'invalid magic number' when using this
vmlinuz 2,417,247 bytes
if I use this:
vmlinuz 2,417,312 bytes
then later it complains about kernel mismatch
I get error 'invalid magic number' when using this
vmlinuz 2,417,247 bytes
if I use this:
vmlinuz 2,417,312 bytes
then later it complains about kernel mismatch
This has to be the sixth time I am going to have to reinstall Ubuntu (Can't get enough of that Linux greatness) in the past 6 months. I just don't understand what exactly is wrong, I don't install anything extra (but the ubuntu restricted extras) yet updates that ask me to reboot will take me to a GRUB command line screen and trying to boot through the command line interface gives me an, "Invalid Magic Number", error.
There should be an official tool for when problems like this come up, so that users like me can easily move their files off their HDD before reinstalling. I didn't come here to rant but, does anyone know what may be causing this everytime, how it can be avoided maybe even how to deal with the Magic Number error and boot in (I wouldn't mind typing in the commands every time BTW)?
My system
Hp Compaq 6730s
2.0Ghz 575 Celeron
4GB RAM
Intel X4500MHD
Broadcom 802.11b/g
I've compiled and added a kernel in Gentoo before. It doesn't seem to go quite as smoothly in Kubuntu 9.10 These are the steps I followed: I unpacked the kernel in /usr/src and ran make && make modules_install succesfully. Then I copied the kernel in arch/x86/boot/bzImage to /boot/bzImage-2.6.32 This entry is the one given by Kubuntu:
Code:
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
[code]....
I just read the script that update grub uses. Changed the name of the kernel from xyz to vmlinuz-2.6.32-generic and it worked.
i wanted to see the red hat side of things and do some virtualization with CentOS, so i am trying to dual boot ubuntu 10.04 LTS and CentOS 5.5. the machine is a laptop, toshiba A100 series. what I did was to create the following partitioning scheme via Ubuntu LiveCd
Code:
Device Boot Start End Blocks Id System
/dev/sda1 * 1 19457 156288290+ 5 Extended
/dev/sda5 1 2103 16892284+ 83 Linux
/dev/sda6 2104 9988 63336231 83 Linux
/dev/sda7 9995 12623 21117411 83 Linux
/dev/sda8 12624 18800 49616721 83 Linux
/dev/sda9 18801 19457 5277321 82 Linux swap / Solaris
created an extended partition and in there have made sda5 and sda6 as / and home for ubuntu and sda7 and sda8 as / and home for CentOS. and sda9 as swap. I installed ubuntu first and then installed CentOS with no bootloader. Run sudo update-grub through ubuntu and now i have both Ubuntu and CentOS available. But when i select CentOS, i have an error which reads "invalid magic number".
I have grub2 installed, haven't downgraded or done anything to it and the ubuntu install is fresh, one week since i updated to 10.04 from scratch. I have found much contradictory stuff on google, but not something that provides a definite solution and also this post but the second command provided in the solution is one i cannot understand very well and it doesn't seem to work. what I am doing wrong here and how to make this work. I would prefer to do things via Ubuntu since debian stuff is what i am comfortable with and i am installing CentOS to learn not to do work on it.
I tried the steps usually offered (modifying the grub.cfg file, replacing the wubildr files), it still wouldn't boot.
I booted in with the LiveCD to try to chroot into the environment and try running 'update-grub'. However, whenever I tried to chroot, it said it could not execute /bin/bash!
Trying to modify the grub commands manually (which originally gave the error: you need to load the kernal first), in the end said "invalid magic number"
There are some configuration things set in this installation I would like to not lose. Is it hopeless?
i recently moved from Ubuntu to Debian(squeeze).. i am very pleased with squeeze except for this bug..I have this python script i wrote to change my wallpaper (through Gconf), the script would be called by cron from time to time.The problem i am facing in Debian is that this script stopped working.I am exporting the $DISPLAY=:0 in Cron, (this is how it worked in Ubuntu)..the cron job i used is below:
-----------
* * * * * export DISPLAY=:0 && /path/to/my/script.py
--------
so the above was not running...I redirected the output and this is what i got as error:
-------------
Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: /usr/bin/dbus-launch terminated abnormally with the following error: Invalid MIT-MAGIC-COOKIE-1 keyAutolaunch error: X11 initialization failed.)
-------------
[code].....
I have /dev/sda with Squeeze and Win 7 on it, and /dev/sdb with Squeeze. I've managed to get Grub 2 to boot from /dev/sdb1, but only by disabling /dev/sda from being a boot option in the BIOS. When it is available to boot, and lower priority than /dev/sdb, grub does not recognize the UUIds of the disks. So, I've disabled it for now and can boot from /dev/sdb no problems. Trouble is I cannot get Win7 to boot. Grub prints:
error: no such device: f0903a3a903a081c
error: invalid signature
When I boot into Squeeze and run 'blkid' I can see that:
/dev/sda1: LABEL="System Reserved" UUID="F0903A3A903A081C" TYPE="ntfs"
The Grub entry for Win 7 is:
menuentry "Windows 7 (loader) (on /dev/sda1)" {
insmod ntfs
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f0903a3a903a081c
chainloader +1
}
I don't understand how Grub 2 cannot recognize the UUIds. Can Grub 2 to be made to work with volume labels or just plain old /dev/... descriptions? Maybe I should give grub-legacy a go.
I've been setting up a number of netbooks for friends in a group I belong to. I am installing Ubuntu 10.04 and/or Linux Mint 9 on all of the netbooks. The netbooks are all identical. Everything has seemed OK until yesterday. I tried to set the label on the new disk using: # e2label /dev/sda newlabel The error is Bad magic number in super-block while trying to open /dev/sda. Couldn't find valid filesystem superblock.
But the filesystem seems fine. It is mounted. It booted up without errors. But all the e2* tools give the same error. So I checked another netbook with an identical fresh install of Ubuntu 10.04 32-bit. It gives the same error although the system appears to work fine. Next I went and checked my own netbook. It is identical except I swapped out the HDD for an OCZ Vertex SSD. I aligned the partitions and prepared that drive carefully. It seems to work great. But when I ran e2label on it I got the same error message.
All the other installs are fresh, clean, standard installs where I let the installer use the whole disk and do the partitioning automatically. All are using ext4. I did a fresh install of Linux Mint 9 and it has the same error as Ubuntu 10.04. Kubuntu 10.04 on my desktop gives the same error too.
I have two SAS RAID controller cards in a Dell server in slots 2 & 3, both with an array hanging off them. I went to install a third card into slot 1, but then when it boots it says two of my sd's have bad magic number in the super-block and it wants me to create an alternative one, which I don't want to do. If i remove the new card, the server boots perfectly like it did before I added the new card. Is the new card trying to control stuff that isn't hooked up to it because its in slot 1, so its confusing RHEL?
View 5 Replies View RelatedI'm working on a midrange NAS system basically running on Linux and I got to do some great testing today. The step-by-step lead me to using fsdb to corrupt the magic number on a file system in order to corrupt it / test the script that should fix it.
View 1 Replies View RelatedAfter several crashes during videos it seemed like a good idea to fsck root. Downloaded the latest systemrescuecd and ran it at boot. The error message was 'bad magic number, corrupt superblock' with a suggested command to try another superblock. That failed with the same message. Tried tune2fs to force fsck at boot and got the same message. The drive is less than 6 months old and the installed system is working more or less ok. The command I used was 'fsck.ext4 /dev/sdc2'. What am I doing wrong?
View 9 Replies View RelatedI am trying to run Wattch simulator in linux.But it is giving the error below. what is this error and what do I do about it?
fatal: bad magic number in executable `prime' (not an executable?)
I loaded all required files inside the Innovate ARM board.When It starts booting from that location it is showing a error "Bad magic number" How I can get out of this error.
View 1 Replies View Related# sudo dpkg -i vasre-se-1.1.1~Debian_5-i386.deb dpkg: error processing vasre-se-1.1.1~Debian_5-i386.deb (--install):
parse error, in file '/var/lib/dpkg/tmp.ci/control' near line 2 package 'vasre-se':
error in Version string '1.1.1~Debian_5': invalid character in version number
Errors were encountered while processing:
vasre-se-1.1.1~Debian_5-i386.deb
I did install same package ok in 10.4 but now after I upgrade to 10.10 I am getting this error. I have already tried:
# sudo dpkg --clear-avail
# sudo aptitude update
# sudo aptitude upgrade
Impossible to install the Lotus Notes 8.5.2 FP2
Code:
I installed Debian 5.03 Lenny successfully on my machine. I got this error during boot: ACPI : invalid PBLK length [5]. After that the Operating System boots properly and starts normally. What does this error statement mean? Is it safe to work with this installation despite this error?
View 1 Replies View RelatedI've created USB bootable image of my Squeeze using live-magic and had the massage "Installation Finished".Now if I try to boot my system using this USB stick, I get the message:"Insert system disk in drive.Press any key when ready..."
View 2 Replies View RelatedParted Magic doesn't detect the SSD for some reason. I've been trying to install ANY form of Linux onto my chromebook, wiping the SSD first and then installing Linux to it. For the last few months actively trying to do so, all has failed. I decided to get an m.2 connector that plugins into a gpu slot to connect it to my desktop (the SSD is micro-sized...) and it fits perfectly, but when opening Parted Magic from a simple USB drive, all my devices show up except my SSD.
Previously, the installations of Linux onto my Chromebook have always failed with a "not enough memory" message, trying all solutions found online and responding to other's posts, they suggested me to do this since they can't see the problem either. I never knew a basic wipe on an SSD, and installation of Linux would be so difficult. Everyone online says "it's so easy even without crouton" and is plug-in-play essentially. No, it is not.
Trying simply to insert into table. Have succeeded in doing this but now want to correct user use of invalid characters. If I'm understanding correctly, Real-escape-string seems to correct these, so I've been trying to figure out how to use it. A short, test code version gives me a syntax error at INSERT VALUES, which--because it still has the single quotes in the text--tells me the real-escape-string didn't work. The code below gives me a parseing error with invalid $END at </body>.
Insert Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' VALUES (UTC_TIMESTAMP,'What's happen' bra?')' at line 1 Parse error: syntax error, unexpected $end in /home/powere15/public_html/DB/exercises_insert_record.php on line 94
<html><head><title>Exercise Catalog Insert Record</title></head>
<body>
<?
/* Change db and connect values if using online */
[Code]....
Is there any guestimate of the total number of debian users or debian computers world wide?What about total GNU/Linux users (any distro)?
View 2 Replies View RelatedI just installed Debian Jessie (3.16.0-4-amd64) on a desktop box I intend to use as a server in our home office. During installation I included the web server and SSH server options. I have a user account, 'mitchell' set up in addition to root. Everything is working great except that I am unable to log in via SSH from other machines, such as a Windows desktop also on the office LAN (using PuTTY). From the PuTTY terminal it looks like the user name is accepted because the password is requested, but after entering the password it says "Access denied".
Back on the Debian box in I see:
Code: Select allNov 26 14:12:02 DebianDevP6TSE sshd[2278]: Invalid user mitchell from 192.168.1.96
Nov 26 14:12:02 DebianDevP6TSE sshd[2278]: input_userauth_request: invalid user mitchell [preauth]
Nov 26 14:12:07 DebianDevP6TSE sshd[2278]: pam_unix(sshd:auth): check pass; user unknown
Nov 26 14:12:07 DebianDevP6TSE sshd[2278]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=rmbiserv.attlocal.net
Nov 26 14:12:10 DebianDevP6TSE sshd[2278]: Failed password for invalid user mitchell from 192.168.1.96 port 60010 ssh2
So I am guessing I need to set up either the SSHD server, or maybe something in PAM, to authorized users for SSH access?
As a note, "mitchell" is the user name I use to log on to Debian, and I am entering the same user name and password when trying to log in via SSH.
If I try to log in via SSH as "root" I get the following in the log:
Code: Select allNov 26 14:17:01 DebianDevP6TSE CRON[2329]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 26 14:17:02 DebianDevP6TSE CRON[2329]: pam_unix(cron:session): session closed for user root
Nov 26 14:29:59 DebianDevP6TSE sshd[2383]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=rmbiserv.attlocal.net user=root
Nov 26 14:30:01 DebianDevP6TSE sshd[2383]: Failed password for root from 192.168.1.96 port 60132 ssh2
i just installed Debian 5.0.5 ! and i used guided partition (option one) while installing BUT immediately i cannot access my Windows drives C & D. if i click it , it says "Invalid mount option when attempting to mount the volume C " how to fix it?
View 9 Replies View RelatedI'm using NetworkManager for networking.After a big Debian upgrade I had a new problem.Every boot it create a new (invalid) "eth0" connection, and NetworkManager connect automatically to it.As expected, the connection is invalid, and I'm not connection to the Internet.
What I do to fix this every boot is manually remove this wrong "eth0" connection and NetworkManager automatically connect to my good eth0 connection.
Note: If I boot my machine N times without deleting connections, I see N same and invalid "eth0" connections.I think this happen because /etc / network / interfaces conflicts with NetworkManager, but I don't know what trigger this. Here is my relevant configuration:
/etc/network/interfaces:
Code: Select all# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
[code]....
* No "/etc/NetworkManager/system-connections/eth0" connection is created in configuration, but it's displayed.
I had to do a hard shut down on my linux computer. Every since then it is not working properly and I get an invalid certificate on every page.I have never upgraded Debian since I installed it two years ago. With my experience with Gentoo I have found that upgrades can be a problem and it worked fine so I never messed with it.
View 9 Replies View RelatedWhen i upgrade my packages with aptitude in testing, I am starting to get this error.
Also I get this from cron now and then.
I have just installed the newest Debian Stable 7.8 release on my new notebook. Before installation I had to free some disk space from the preinstalled Windows7 with ntfsresize and fdisk. In addition to the existing three primary partitions I created an extended one with three logical partitions for /(root) /home and swap, see the output of 'fdisk -lu'
Code: Select allDisk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x196585ba
[Code] ....
Partition table entries are not in disk order
For some reason I put a bootable flag on sda7, and the only small concern during installation was that some BIOS systems might not work with boot-flag no logical drives. Now, every time I boot I get this "Invalid partition table!' message which I must 'enter" away before I get to the GRUB menu.
i can not enter to my partition when i try that thing , i got this message:
1- Invalid mount option when attempting to mount the volume.
2 - You are not privileged to mount this volume.
first message it is about entering (( Windows OS partition )) (( NTFS ))
second message it is about entering other partiton with (( FAT32 ))
I got the Raspberry pi 2 Model B. I flashed my sdcard with raspberian Jessie kernel 4.1 (latest).Also tried wheezy and NOOBS, same behavior.With a ethernet cable (known working), I tried connecting my Pi to my home router, and I got a invalid ip address 169.254.xxx.xxx, and therefore no linkup. I got the same results by connecting my Pi directly to my modem (wired).
I know that /etc/dhcpd.conf is the new /etc/network/interfaces for network configurations.So I tried the debug option, and I noticed that the router doesn't seems to response to the DISCOVER command from the Pi (dhcp v4 protocol).Here's a dump of by /var/log/syslog | grep dhcp
Code: Select allDec 28 12:00:02 raspberrypi systemd[1]: Starting dhcpcd on all interfaces...
Dec 28 12:00:02 raspberrypi dhcpcd[349]: version 6.7.1 starting
Dec 28 12:00:02 raspberrypi dhcpcd[349]: udev: starting
Dec 28 12:00:02 raspberrypi dhcpcd[349]: dev: loaded udev
Dec 28 12:00:02 raspberrypi dhcpcd[349]: eth0: disabling kernel IPv6 RA support
[code]...
ANd if i use raspbian flesh out of installation, I get this when i run
dhcpcd -k
dhcpcd eth0
eth0: probing for an IPv4ALL address
eth0: using IPv4ALL address 169.154.202.224
Seems like my home router TP-link (default setup) doesn't send a response to the dhcp request.
During boot (and in dmesg) I get the following message:
[6.782835] ACPI: Invalid PBLK length [7]
Also possibly related, whenever I close my laptop lid, kacpi_notify and kacpid eat up the cpu, and the screen doesn't actually blank.
This error is very difficult to solve, but also appears widespread across the Debian universe and also others like Arch and Fedora. I use a Canon LiDE 110 scanner and it has always worked very well under Linux. This same problem affects many other scanners not just the 110. Run any front end like xSane and after initially appearing to be OK it will fail with an Invalid Argument error.
But, it does not happen to everyone. I have several machines to experiment with so I did. I also used Debian Testing and Sid, Ubuntu 14.04 and 14.10 and various Mint versions and desktops.
The error is all to do with USB3. Plugging the scanner into a USB2 port does not in and of itself solve the issue. Nor does running the scanner through a hub. On my older laptop without USB3 hardware my scanner works like a charm using any modern Linux. On my very old spare desktop it also works fine despite having USB3.
But, on my shiny new Intel i5 on an ASUS H97I Plus it all falls apart. After much reading of forums and many dead ends we find the problem is modern machines with Intel xHCI Mode in the BIOS. It has to be off, not enabled, auto nor super auto. But when you turn it off you turn off USB3 support and your system falls back to USB2 only. My old spare machine has an AMD chipset and USB3 enabled does not cause this error.
So if you need to use your scanner and get this error then xHCI mode is the workaround. Fine if you have no real need for USB3, but most definitely a temporary solution.
Where in the system does this error come from? Too hard for me. Is it in Sane or in the libusb sub system or all the way up to the kernel? However if you have any USB device that has stopped working this setting in your BIOS has got to be worth a try. It is nothing to do with permissions or firmware.
sane-utils updated to 1.0.24-5 in sid (Dec 12, 2014) problem still exists.