Fix Cannot Determine Root Device. Assuming /dev/hda1 (Solved)

Home > Cannot Determine > Cannot Determine Root Device. Assuming /dev/hda1

Cannot Determine Root Device. Assuming /dev/hda1

On reboot after everything appeared to finish, I get these errors: Failed to allocate mem resource #6: ___________ for _______________ RAMDISK: ran out of compressed data invalid compressed format (err=1) Kernel I used the kernelcheck app to auto install last time, saves time this way. b) Could you please post your /boot/grub/menu.lst? Michael Flaig (mflaig) said on 2006-12-13: #2 Just some ideas to supply more information ... his comment is here

asked 3 months ago viewed 28 times Related 1Can't ssh or console to the guest using ubuntu-vm-builder2Swap partition is being corrupted by running Ubuntu from a USB stick0How to uninstall VMs Use the label, UUID, or friendly nameUUIDUUID means Universally Unique Identifier. Done Reading extended state information Initializing package states... I started from the top entry in GRUB and worked my way down through the different kernels, and still I get the error: Kernel Panic - not syncing: VFS: Unable to

Message #34 received at [email protected] (full text, mbox, reply): From: Kenshi Muto To: [email protected] Subject: Re: Bug#110431: update-grub always uses (hd0,0) and /dev/hda1 for root Date: Fri, 07 Feb 2003 Ask Ubuntu works best with JavaScript enabled Sign in | Register ›My developerWorks developerWorks Community ›My profile ›My communities ›Settings ›Sign out IBM Technical topics Evaluation software Community Events if [ -z "$rootp" ]; then !

  • It could take time to troubleshoot this problem and fix it.
  • Page 1 of 2 12 Last Jump to page: Results 1 to 10 of 20 Thread: new kernel not showing in Grub List Thread Tools Show Printable Version Subscribe to this
  • menu.lst contents: default 0 timeout 3 hiddenmenu title Ubuntu 9.04, kernel root (hd0,0) kernel /boot/vmlinuz- root=/dev/hda1 ro quiet splash $ initrd /boot/initrd.img- title Ubuntu 9.04, kernel (recovery mode) root

found: /boot/grub Cannot determine root device. I finally managed to restore the proprietary drivers, and get into ubuntu again. How can a Cleric be proficient in warhammers? dpkg: error processing linux-server (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.32-37-server linux-image-server linux-server After this APT upgrades would not work.

update-initramfs: Generating /boot/initrd.img-2.6.17-10-generic Not updating initrd symbolic links since we are being updated/reinstalled (2.6.17-10.33 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.17-10.33 As far as I can remember such errors started to occur after updating to Ubuntu 11.10 (Oneiric). not an expert ? read the full info here ronrafajko (ron-rafajko) said on 2006-12-13: #3 /boot is 29.19MB with only 23Kb free /swap is 431.43 MB / is 92.7 GB with 67.41GB free Can I shrink swap to 200MB and

Sorry I did not save the log file. asked 4 years ago viewed 373 times active 4 years ago Related 2Grub no longer boots after kernel update (second time now)5Windows 7 doesn't boot after Ubuntu install0Ubuntu 10.04 and fedora fi ! When I boot the 2.6.17-10-generic kernel I only get the fourth error, then the machine reboots.

You may have experienced the cannot mount rootfs error (followed by your Linux host getting a kernel panic) after you reboot your system. Done Preconfiguring packages ... (Reading database ... 114829 files and directories currently installed.) Preparing to replace linux-image-2.6.17-10-generic 2.6.17-10.33 (using .../linux-image-2.6.17-10-generic_2.6.17-10.33_amd64.deb) ... if [ -z "$rootk" ]; then ! Continuing as directed.

Done The following packages will be REINSTALLED: linux-image-2.6.17-10-generic 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. this content The given patch solves the problem I'm experiencing, so please upload a new grub package with this fix (we always puts / on the first partition). LILO can be positioned in the master boot record (MBR) or the boot sector of a partition; if you do the second option, something else must be placed in the MBR This bug must be fixed before grub can be a useful alternative in the new installer (debian-installer).

I tried ls -lt, and obtained a list of old files ... Browse other questions tagged 12.04 grub2 ati kernel 64-bit or ask your own question. I do not believe there is any simple, correct and automatic way to translate linux device names (/dev/sda1) to grub device names. weblink done Setting up linux-image-2.6.17-10-generic (2.6.17-10.33) ...

rootd=$(echo $rootk | awk '{ print substr($0, 1, match($0, "[0-9]+$") - 1) }') ! Assuming /dev/hda1 2016-07-11 02:42 INFO : This error is probably caused by an invalid /etc/fstab` /etc/fstab just shows LABEL=CLOUD / ext4 0 0 Attempting to mount /dev/pts: [email protected]:/# mount pts /dev/pts done ! !

found: /boot/grub/menu.lst Searching for splash image ...

Johnny Chadda (joch) said on 2007-01-14: #8 The easiest thing is to just ignore the /boot partition because of the small size and move everything to your root-partition. found: /boot/grub/menu.lst Searching for splash image ... Copy sent to Jason Thomas , [email protected] Message #24 received at [email protected] (full text, mbox, reply): From: Jason Thomas To: Petter Reinholdtsen , [email protected] Subject: Re: Bug#110431: update-grub always uses (hd0,0) and /dev/hda1 for root partitions Date:

Tank-Fighting Alien Why is this C++ code faster than my hand-written assembly for testing the Collatz conjecture? Is there a word for turning something into a competition? Full text and rfc822 format available. This patch is relative to 0.91-2.