plymouth message after changing hdd to other machine

[melodie]

Hi,
The HDD was on a Dell as slave and is now on another Dell (same brand and model) as master. The output yells at me:

While installing package plymouth-0.8.3-1pclos2010:

sh: -c: line 0: syntax error near unexpected token `hd0,6'
sh: -c: line 0: `/bin/zcat (hd0,6)/boot/initrd.img 2> /dev/null | /bin/cpio -t &> /dev/null'
can't open (hd0,6)/boot/initrd.img: No such file or directory
/usr/share/bootsplash/scripts/make-boot-splash-raw: line 49: (hd0,6)/boot/initrd.img: No such file or directory
sh: -c: line 0: syntax error near unexpected token `hd0,6'
sh: -c: line 0: `/bin/zcat (hd0,6)/boot/initrd-2.6.33.5-pclos1.bfs.img 2> /dev/null | /bin/cpio -t &> /dev/null'
can't open (hd0,6)/boot/initrd-2.6.33.5-pclos1.bfs.img: No such file or directory
/usr/share/bootsplash/scripts/make-boot-splash-raw: line 49: (hd0,6)/boot/initrd-2.6.33.5-pclos1.bfs.img: No such file or directory

I suppose I will reinstall the kernel, then the plymouth package.

What else could I do ?

[Neal ManBear]

Melodie,
Renstalling the kernel shouldn't be necessary. Just reboot.
After that, open the plymouth themes directory and run switch-themes. If the error has persisted, it will show up in the output. If there is no output, you're fine.

[kjpetrie]

Sorry, Neal. I think my previous post (now deleted) misled you into thinking melodie's problem was the same as mine. She has actually moved her install and rebooted in the process, and plymouth complained because the drive had actually moved from slave to master, so her problem was probably permanent. Three days later she has probably already reinstalled the packages.

Once I realised there was another post and that it was not a problem in my case I removed my irrelevant contribution.

[melodie]

Yes, and also it was taking a whole additional minute to boot : it was seeking for it's partition and for the swap partition as well. (then timout then boot). Strange that it needs to look at that, while booting, and not very convenient. Couldn't that be done differently ? The distro is SO stable that you won't move it !

[Neal ManBear]

kjpetrie,
I see.

Melodie,
Couldn't you edit fstab and menu.list?

[kjpetrie]

It looks for the swap partition to see whether it needs to resume after a suspend to disc.

[melodie]

It looks for the swap partition to see whether it needs to resume after a suspend to disc.

Yes : it was looking at the wrong / and swap partitions though : the namings that it had when it was slave on the other machine. ;-)

Neal : I thought it was in the initrd : isn't it in the initrd ? When I changed for a new kernel, it didn't search at the wrong place afterwards.

[John Bee]

Yes : it was looking at the wrong / and swap partitions though : the namings that it had when it was slave on the other machine. ;-)

Neal : I thought it was in the initrd : isn't it in the initrd ? When I changed for a new kernel, it didn't search at the wrong place afterwards.

Hi Melodie;

 Please see the following thread for some insite into this long wait at boot waiting for drives to show up.

Waiting for device sda6 to appear (timeout 1min)" notice after cloning HDD
http://www.pclinuxos.com/forum/index.php/topic,74051.0.html

[Neal ManBear]

It looks for the swap partition to see whether it needs to resume after a suspend to disc.

Yes : it was looking at the wrong / and swap partitions though : the namings that it had when it was slave on the other machine. ;-)

Neal : I thought it was in the initrd : isn't it in the initrd ? When I changed for a new kernel, it didn't search at the wrong place afterwards.

Yes, you should 'redo' initrd, too. Should have said, shouldn't I?

[melodie]

It looks for the swap partition to see whether it needs to resume after a suspend to disc.

Yes : it was looking at the wrong / and swap partitions though : the namings that it had when it was slave on the other machine. ;-)

Neal : I thought it was in the initrd : isn't it in the initrd ? When I changed for a new kernel, it didn't search at the wrong place afterwards.

Yes, you should 'redo' initrd, too. Should have said, shouldn't I?

Re-install the kernel, or install one seemed to me the easy solution to get a new initrd. Then at one try, I realised that if I was purely reinstalling the same kernel, this wild unteamed system would not redo the initrd (the problem after reboot was still the same). Only the install of a new kernel did the trick...

What is the command line to redo an initrd ? "mkinitrd -g -k ?something?"

[Neal ManBear]

I believe that would be

Code: [Select]

mkinitrd -v -f initrd-<kernel version>.img
You may want to check on that just to be sure.

[John Bee]

What is the command line to redo an initrd ? "mkinitrd -g -k ?something?"

Hi Melodie;

An example (the -f tells mkinitrd to replace the existing initrd.img file)

mkinitrd -f /boot/initrd-2.6.33.4-pclos1.pae.img 2.6.33.4-pclos1.pae

replace with whatever kernel you want to update.

[Old-Polack]

melodie:

If you cd to /boot then do mv initrd-2.6.33.4-pclos1.pae.img initrd-2.6.33.4-pclos1.pae.img-old before reinstalling the same kernel, it should then make the initrd for the kernel also. If you've already installed a new kernel, you could uninstall the old one through Synaptic, then do a fresh install of the older kernel, to get the initrd image for sure.

[pags]

What is the command line to redo an initrd ? "mkinitrd -g -k ?something?"

Hi Melodie;

An example (the -f tells mkinitrd to replace the existing initrd.img file)

mkinitrd -f /boot/initrd-2.6.33.4-pclos1.pae.img 2.6.33.4-pclos1.pae

replace with whatever kernel you want to update.

Code: [Select]

mkinitrd -f /boot/initrd-`uname -r`.img `uname -r`That should take care of handling the appropriate kernel

old-polack has a point, also.

melodie:

If you cd to /boot then do mv initrd-2.6.33.4-pclos1.pae.img initrd-2.6.33.4-pclos1.pae.img-old before reinstalling the same kernel, it should then make the initrd for the kernel also. If you've already installed a new kernel, you could uninstall the old one through Synaptic, then do a fresh install of the older kernel, to get the initrd image for sure.

Copy (or move) your current initrd (if for no other reason than to have a fall back that can be restored from the LiveCD, should something go amiss)

[John Bee]

Code: [Select]

mkinitrd -f /boot/initrd-`uname -r`.img `uname -r`
That should take care of handling the appropriate kernel

Most elegant and functional.

This one goes into my Important Stuff.txt file.

Thanks.