Error Symbol Not Found Grub_divmod64_full Grub Rescue
Contents |
18 people Affects Status Importance Assigned to Milestone Software Updater Edit Invalid Undecided Unassigned Edit You need to log in to change this bug's status.
Grub Rescue Commands
Affecting: Software Updater Filed here by: Nick Semenkovich When: 2011-08-29 Completed: ubuntu grub rescue 2011-10-19 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix
Super Grub Disk
tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Invalid Undecided Assigned to Nobody Me Remote Watch None, the status of the bug is http://forums.debian.net/viewtopic.php?f=5&t=104756 updated manually. None, the status of the bug is updated manually. URL: The information about this bug in Launchpad is automatically pulled daily from the remote bug. Comment on this change (optional) Email me about changes to this bug report grub2 (Ubuntu) Edit Invalid High Unassigned Edit You need to log in to change this bug's status. Affecting: https://bugs.launchpad.net/bugs/836378 grub2 (Ubuntu) Filed here by: Nick Semenkovich When: 2011-08-29 Completed: 2011-10-19 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Invalid High Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description Upgraded from Natty to Oneiric on a machine with a two-drive RAID 1 md0 using do-release-upgrade -d The upgrade went fine, but on reboot, the machine simply hangs at: error: symbol not found: 'grub_divmod64_full'. grub rescue> Trying to recover and grab logs now. Add tags Tag help Nick Semenkovich (semenko) wrote on 2011-08-29: #1 [The md device was checked before the upgrade via sync_action] grub rescue> ls (md1) (hd0) (hd0,msdos1) (hd1) (hd1,msdos1) grub rescue> ls (md1)/boot [ Shows boot dir] grub rescue> ls (hd0,msdos1)/boot [ Shows boot dir] grub rescue> ls (hd1,msdos1)/boot [ Shows boot dir] grub rescue> insmod linux error:
not found: ‘grub_divmod64_full' Posted on August 25, 2012 by Paul Berruti After fighting to upgrade my system from Debian Squeeze (Stable) to Wheezy (Testing), I thought I was finally in the free and clear once I had installed all of http://paulberruti.net/2012/08/grub-error-symbol-not-found-grub_divmod64_full/ the packages so I rebooted. After taking a YouTube break, I tried to SSH back into the machine. Timed out. I made the long trek to the other room and turned on the TV the machine is https://forums.linuxmint.com/viewtopic.php?t=74821 connected to and was faced with: error: symbol not found: 'grub_divmod64_full' Excellent. Luckily this one wasn't quite as bad as my apt-get adventures and recovery is fairly well documented. My steps varied a bit because my system not found is running RAID, so I'm expanding the steps a bit for any [software mdadm] RAID users. Boot to your favorite Linux live CD and add the kernel parameter "nodmraid". This was needed for my raid because dmraid kept accessing my disks and wouldn't assemble the RAID properly and locked the disks so I couldn't use mdadm. As far as the live CD is concerned, I ended up using Ubuntu because I couldn't get Knoppix to error symbol grub boot to 64 bit and bitness is important since we'll be using chroot. First, assemble and mount the RAID arrays (replace drives and partitions as necessary.) For me /dev/md0 is /boot and /dev/md1 is my root filesystem, /. mdadm --activate /dev/md0 /dev/sda1 /dev/sdb1 mdadm --activate /dev/md1 /dev/sda3 /dev/sdb3 mkdir /mnt/target mount /dev/md1 /mnt/target mount /dev/md0 /mnt/target/boot Next we'll need to populate the dynamic areas of the filesystem (e.g. /dev, /proc) and then change our shell into that environment: mount --bind /proc /mnt/target/proc mount --bind /run /mnt/target/run mount --bind /sys /mnt/target/sys mount --bind /dev /mnt/target/dev mount --bind /dev/pts /mnt/target/dev/pts chroot /mnt/target /bin/bash Now a few easy commands to reinstall Grub 2: apt-get install --reinstall grub-pc dpkg-reconfigure grub-pc I opted to install Grub to both of my physical drives, /dev/sda and /dev/sdb for safety. Ctrl+D to exit the chroot, reboot, and you should be all set! Now I've got a fully upgraded system running Debian Testing and since I'm using "testing" in sources.list, I'll never have to do a major dist-upgrade again since packages roll in over time. It's a versionless OS and that's just wonderful! -Paul This entry was posted in Computers. Bookmark the permalink. ← Could not perform immediate configuration on ‘default-jre' Building a Bass Effects Pedal: Five Knob Compressor → 7 Responses to Grub error: symbol not found: ‘grub_divmod64_full