Welcome, Guest. Please login or register.
April 19, 2014, 16:44:41 PM
Home Help Search Calendar Login Register
Show unread posts since last visit.
News: Let Pardus-Anka become #1: Pardus-Anka Bug ReportPardus-Anka World Google+ | The Pardus wiki  | Visit Pardus-Anka official website  | Register as forum member?  Email the moderator!

+  Pardus Worldforum
|-+  Assistance
| |-+  Bugs
| | |-+  could not find boot device reboot with initramfs=shell(noprobe)
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: could not find boot device reboot with initramfs=shell(noprobe)  (Read 4056 times)
Lisa
Pardus Guru
****
Posts: 841



View Profile
« on: May 20, 2011, 18:53:17 PM »

I wasn't sure how I should go about debugging this one as I have both Pardus 2011 and Pardus Corporate installed, but after installing both and doing all updates, I got an  initramfs error.
I also have Debian installed as well as  MoonOS. 
After a few reboots of each operating system, including XP  Wink  when I go to Pardus 2011 boot menu and select Pardus Kurumsal, it goes directly to the green blue start up screen with the twirling progress circle (it should first show briefly a black screen that says at top, booting into hd1,4 with uiid number, or something to that affect).  After the blue green boot up screen, it then shows a black prompt screen:
Could not find boot device
Reboot with initramfs=shell(noprobe) to debug, (I think is what was written.)

Well, I tried adding "initramfs=shell" and initramfs=shell(noprobe) to end of Corporate boot configuration at boot menu, but it didn't give me any further information.  I never thought of trying to log in as safe-mode.

Prior to this, Debian did a pre-login disk check (fscheck?) when I logged into Debian, but I doubt this had anything to do with it.

Doing a search for this error brought three hits, but I don't understand the translated text.  They are for Kurumsal Beta.
Google hits
I fixed this by reinstalling Pardus Kurumsal grub on MBR on first hard drive.  I'm not sure what caused it. Couldn't find any warnings or errors in logs that mentioned initramfs.  This isn't a big deal to me, as I like Corporate's boot menu, too, but wanted to mention it.
Lisa Marie
Logged
Lisa
Pardus Guru
****
Posts: 841



View Profile
« Reply #1 on: May 21, 2011, 17:43:21 PM »

After changing back to Pardus Kurusmal boot manager I noticed a second entry for Pardus Kurumsal, so I clicked on it.  It too had the same problem, leaving me at an initramfs prompt.  The only thing I noticed is the uuid numbers were different.  I don't know how these uuid numbers are generated during grub creation, randomly?  The top entry for Kurumsal works, but not the one down the list.  I must say, Pardus grub doesn't do the neatest job of finding other operating systems, as I have had this problem when I used Pardus 2009 (it would add extra repeat entries.  The only thing different with my setup this year is I am partitioning each operating system with a root partition and a home partition.  Otherwise, all is the same - first hard drive has two NTFS primary partitions, first of which is XP location, and second drive is first created as extended, then each partition for the four Linux distros is logical with a small middle partition for swap. 

This time to get rid of the initramfs error in the second Kurumsal entry, I edited Kurumsal's grub.conf and matched the uuid numbers. 

Since then, I have re-installed Pardus 2011 boot manager to try and debug it more, but both 2011 and Kurumsal grub.conf  files are pretty messy.  Here's 2011's dirty looking grub menu with ghost distros and wrong device locations:
Code:
default 0
gfxmenu /boot/grub/message
background 10333C
timeout 10

title Pardus 2011 [2.6.37.6]
uuid da16d524-a23c-4d5a-9668-f6dd24307695
kernel /boot/kernel-2.6.37.6 root=UUID=da16d524-a23c-4d5a-9668-f6dd24307695 resume=/dev/sdb9 quiet splash
initrd /boot/initramfs-2.6.37.6

title Windows on /dev/sda1
map (hd0) (hd0,0)
map (hd0,0) (hd0)
rootnoverify (hd0,0)
makeactive
chainloader +1

title Debian GNU/Linux, kernel 2.6.26-2-amd64 [ /dev/sdb13 ]
root (hd1,12)
kernel /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sdb13 ro quiet
initrd /boot/initrd.img-2.6.26-2-amd64

title Debian GNU/Linux, kernel 2.6.26-2-amd64 (single-user mode) [ /dev/sdb13 ]
root (hd1,12)
kernel /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sdb13 ro single
initrd /boot/initrd.img-2.6.26-2-amd64

title Other operating systems: [ /dev/sdb13 ]
root

title Microsoft Windows XP Professional [ /dev/sdb13 ]
root (hd1,12)
makeactive
chainloader +1
savedefault 5

title Debian GNU/Linux, kernel 2.6.26-2-amd64 [ /dev/sdb13 ] [ /dev/sdb7 ]
root (hd1,6)
kernel /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sdb13 ro quiet
initrd /boot/initrd.img-2.6.26-2-amd64

title Debian GNU/Linux, kernel 2.6.26-2-amd64 (single-user mode) [ /dev/sdb13 ] [ /dev/sdb7 ]
root (hd1,6)
kernel /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sdb13 ro single
initrd /boot/initrd.img-2.6.26-2-amd64

title Other operating systems: [ /dev/sdb13 ] [ /dev/sdb7 ]
root

title Microsoft Windows XP Professional [ /dev/sdb13 ] [ /dev/sdb7 ]
root (hd1,6)
makeactive
chainloader +1
savedefault 9

title Other operating systems: [ /dev/sdb5 ] [ /dev/sdb7 ]
root

title Pardus Kurumsal 2 [ /dev/sdb5 ] [ /dev/sdb7 ]
root (hd1,6)
kernel /boot/kernel-2.6.35.11 root=UUID=6bf09a43-0e29-4061-bdfd-45bfab8bfc5a resume=/dev/sdb9 splash splash quiet
initrd /boot/initramfs-2.6.35.11

title moonOS, with Linux 2.6.35-24 [ /dev/sdb11 ] [ /dev/sdb5 ] [ /dev/sdb7 ]
root (hd1,6)
kernel /boot/vmlinuz-2.6.35-24-generic root=UUID=0d2ef9e5-65d8-428c-bcd1-06649a26ee87 ro quiet splash
initrd /boot/initrd.img-2.6.35-24-generic

title Debian GNU/Linux, kernel 2.6.26-2-amd64 [ /dev/sdb13 ] [ /dev/sdb5 ] [ /dev/sdb7 ]
root (hd1,6)
kernel /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sdb13 ro quiet
initrd /boot/initrd.img-2.6.26-2-amd64

title Debian GNU/Linux, kernel 2.6.26-2-amd64 (single-user mode) [ /dev/sdb13 ] [ /dev/sdb5 ] [ /dev/sdb7 ]
root (hd1,6)
kernel /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sdb13 ro single
initrd /boot/initrd.img-2.6.26-2-amd64

title otheroptions
configfile /boot/grub/grub-alt.conf

I would like to see the utility "update grub" in Pardus as it seems to work well in other distros.  I did praise Pardus in past in how well it finds other distros during install, but on the other hand, it goes beyond and adds ditto entries with varying device locations. 
Lisa Marie

P.S.  One place one can find errors for grub is in yaliinstall.log where an excerpt from mine reads:
Code:
  partedDevice = <parted.device.Device object at 0x2b74690>
  removable = False  partedDevice = <parted.device.Device object at 0x2b741d0>
2011-05-10 15:37:02,804: DEBUG    Writing grub.conf and devicemap
2011-05-10 15:37:02,812: DEBUG    Step 'Writing bootloader...' finished with failure.
2011-05-10 15:37:03,313: DEBUG    Running Step : Stopping to D-Bus...
2011-05-10 15:37:03,314: INFO     Running chroot

« Last Edit: May 21, 2011, 18:02:26 PM by Lisa » Logged
Lisa
Pardus Guru
****
Posts: 841



View Profile
« Reply #2 on: May 21, 2011, 18:48:55 PM »

All is well after I cleaned up Pardus 2011's  /boot/grub/grub.conf to the following, of which I changed the UUID number for Kurumsal entry to first Kurumsal entry in kurumsal's grub.conf file. (and that's a lot of kurumsal's  Grin  )
Neat and and in the right order:
Code:
default 0
gfxmenu /boot/grub/message
timeout 10
background 10333C

title Pardus 2011 [2.6.37.6]
uuid da16d524-a23c-4d5a-9668-f6dd24307695
kernel /boot/kernel-2.6.37.6 root=UUID=da16d524-a23c-4d5a-9668-f6dd24307695 resume=/dev/sdb9 quiet splash
initrd /boot/initramfs-2.6.37.6

title Other operating systems:
root

title Windows on /dev/sda1
map (hd0) (hd0,0)
map (hd0,0) (hd0)
rootnoverify (hd0,0)
makeactive
chainloader +1

title Pardus Kurumsal 2 [ /dev/sdb7 ]
root (hd1,6)
kernel /boot/kernel-2.6.35.11 root=UUID=45c633cb-2eca-4def-ab08-4c5dea266999 resume=/dev/sdb9 splash splash quiet
initrd /boot/initramfs-2.6.35.11

title moonOS, with Linux 2.6.35-28 [ /dev/sdb11 ]
root (hd1,10)
kernel /boot/vmlinuz-2.6.35-28-generic root=UUID=0d2ef9e5-65d8-428c-bcd1-06649a26ee87 ro quiet splash
initrd /boot/initrd.img-2.6.35-28-generic

title Debian GNU/Linux, kernel 2.6.26-2-amd64 [ /dev/sdb13 ]
root (hd1,12)
kernel /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sdb13 ro quiet
initrd /boot/initrd.img-2.6.26-2-amd64

title Debian GNU/Linux, kernel 2.6.26-2-amd64 (single-user mode) [ /dev/sdb13 ]
root (hd1,12)
kernel /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sdb13 ro single
initrd /boot/initrd.img-2.6.26-2-amd64

title otheroptions
configfile /boot/grub/grub-alt.conf

I suppose I shall write a bug report for this, as there is always someone that is going to have more than one Linux distro installed on her or his computer.
P.S. Bug report here

« Last Edit: May 21, 2011, 23:26:04 PM by Lisa » Logged
Sojourner
Guest
« Reply #3 on: May 22, 2011, 02:02:03 AM »

I also noticed a problem with Kurumsal2 not playing nicely with other distros when booting, especially if theGrub .98 of Kurumsal was overwritten by Grub2 from Debian 6.1. Grub error 22 was a persistent presence until I rearranged some things. The Pardus array all end up with phantom locations and a menu-lst with lotsa junk. The same thing happened early on when LinuxMint "improved" Grub .98 with the gfx stuff and the unique partition identifier numbers (UUID) appeared. In fact, some of the older posts of Husse deal with that issue, particularly tracking down the UUID numbers..

Pardus-All would save a good bit of difficulty if they simply began using Grub1.98, as it is mature now and  is convenient to use for the MBR boot for all installed distros. I have LiLO, Grub .98 and 1.98 and using the new Grub is handy as it is very intuitive - except that it picks up all the Pardus "ghosts" from the menu.lst.

I didn't bother to analyze the details of the cockup but simply "rearranged" the installs. I like Pardus as it is stable and the Pisi system is quite good as it does not fracture things. Compared to the lengthy period when OpenSUSE couldn't come up with something that worked after they abandoned Yast. Pisi is a marvel of reliability. I've had a Pardus 2009 install running without incident, mostly 24/7 since it was released.

My only hitch with Pardus is having to install standalone browsers as they don't keep up with the security updates. That is a small chore, though.

I think the issue of the UUID cockup is inherent in trying to jazz up Grub .98 rather than simply moving on to 1.98 or, dropping the UUID junk and being satisfied with the old HD(0,0) stuff. LiLO works better than this current arrangement, and if one has to manually "cleanup", LiLO is as good as any for that.
Logged
atolboo
Pardus Guru
****
Posts: 2317



View Profile
« Reply #4 on: May 22, 2011, 09:22:40 AM »

Also Wiki: >Adding a GRUB 2 item in the boot-menu of Pardus (GRUB Legacy)< Grin
« Last Edit: May 22, 2011, 09:29:38 AM by atolboo » Logged
Lisa
Pardus Guru
****
Posts: 841



View Profile
« Reply #5 on: May 24, 2011, 16:12:49 PM »

Much appreciated Sojourner.  You have given me more things to ponder.  I was wondering if this was a Yali problem or just the Grub boot manager version Pardus uses.  I was looking over the READ ME's in /usr/share/doc/grub and seems the version Pardus uses doesn't support ext4 and that is what three of the Linux distro's I have are formatted as.  Debian is using ext3. 

I was tempted to install the latest Grub version to see how it worked - test it.  I was also looking at Grub for DOS, but it has small support and one Debian user had problems compiling it. 

So, there are hopes in future these problems will be resolved with updated Grub versions. 

P.S.  I did find out that update-grub is a Debian utility.  I assumed it was part of Grub.  It would be great to see Pardus come up with their own unique grub updater.

P.S.S. and thanks Atolboo for the link on installing grub2 distros in Pardus.  That how-to worked for me when installing MoonOS which uses Ubuntu grub2 version ?, as well as when I tried Kanotix. 

P.S.S.S.  Grin  Another handy command to use when using Pardus install disc to re-install it's grub to MBR is that instead of using:
root (    press TAB
to find possible partitions where Grub is located, to instead type:
find /boot/grub/stage1 press enter
you get better outputs.
Lisa Marie
Logged
atolboo
Pardus Guru
****
Posts: 2317



View Profile
« Reply #6 on: May 24, 2011, 16:28:04 PM »

...... and seems the version Pardus uses doesn't support ext4 .........
I think this is   as Pardus uses the ext4 filesystem, and thus highly
Logged
Lisa
Pardus Guru
****
Posts: 841



View Profile
« Reply #7 on: May 25, 2011, 16:20:53 PM »

I'm not exactly sure what you mean, atolboo, but it is probably because of my wording.  I should have said that GNU Grub version .97 goes as far as supporting ext2 according to their changelog.  Operating systems have had to create patches to use ext4 with Grub Legacy, which Pardus seems to have done because the ext4 entries are created in the menu.list.   

I had no idea that GNU Grub Legacy is no longer being updated, just bug fixes applied, as version .97 is from 2005.  All work has shifted to Grub2.
Lisa Marie
Logged
atolboo
Pardus Guru
****
Posts: 2317



View Profile
« Reply #8 on: May 25, 2011, 21:22:56 PM »

I'm not exactly sure what you mean, atolboo,
As far as I know there is >GRUB 2< and >GRUB Legacy<.
And as Pardus uses GRUB Legacy and the ext4 file system, it has to support ext4.
By the way, openSUSE 11.4 is also using GRUB Legacy and the ext4 file system. Wink
Logged
Sojourner
Guest
« Reply #9 on: May 26, 2011, 13:45:40 PM »

Most distros re-scripted Grub legacy to allow Ext4 by 2009. Initially, Ext 4 required a separate /boot partition. Now, brtfs is in somewhat the same position as was Ext4.

Naturally, conflicts may arise between Grub2 mixing with Legacy and perhaps also LiLO in multiboots because distros alter the scripting for their default bootloader as they see fit. Likewise with permissions policy, init schemes and the like. Compare fstab in Pardus 2009 and Pardus 2011. Two different worlds.

If there is a conflict, it is not necessarily a "bug", and may simply be a conflict - that is, bootloader versus bootloader, distro versus distro.

My earlier problem with K2 may have been a "wrong" device.map, as I found in another K2 install. Either the device.map was wrong at install or was modified by another install's Grub2 or even during an update of that Grub2. My suspicion is that a subsequent use of a Grub2 boot install after the K2 was installed may have rearranged K2 device.map. Now, K2 resides alone on the HD, elevated to Numero Uno!

The device.map likely will disappear as UUID and Grub2 become universally accepted, as UUID makes it redundant.

Of course, the devs cannot be held responsible for the hazards of multi-booting, which are generally self-inflicted wounds. With knowledgeable helpers like atolboo, such difficulties are quickly corrected.

I like K2 so much that I am planning on using it as the replacement for 2009, rather than 2011. I have been running 2009 since release and it has never had the first glitch or hiccup through all the upgrades. There are not many distros as reliable/stable, which is another way of saying that the Pardus devs are thoroughly professional and careful in their work. One could say that 2009 has been Enterprise-grade stable throughout its life, which is remarkable on the Desktop side of an Enterpise spin/Desktop spin distro, IMO.
Logged
Lisa
Pardus Guru
****
Posts: 841



View Profile
« Reply #10 on: May 28, 2011, 22:05:44 PM »

Of course, the devs cannot be held responsible for the hazards of multi-booting, which are generally self-inflicted wounds. With knowledgeable helpers like atolboo, such difficulties are quickly corrected.
Agreed.  That is why in the past I was reluctant to report this as a bug, besides the how-to's I have used work great on resolving the issue.
Boot Managers are like a mini operating system in themselves, so one certainly can't fault the os developers whether x number of other operating systems are found and added gracefully. 
Again, thank you both for your feeback.  Good reading.
Lisa Marie
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  


Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!