Booting Puppy 'could not run etc/init.d/rcS'

Booting, installing, newbie
Post Reply
Message
Author
User avatar
iansl2000
Posts: 34
Joined: Thu 23 Mar 2006, 00:18
Location: UK

Booting Puppy 'could not run etc/init.d/rcS'

#1 Post by iansl2000 »

I have a windows pc that dual boots to puppy215 using the following files
menu.lst
boot.ini
grldr

My daughter has a machine that has the whole hard drive dedicated to puppy ie no windows.

In order to transfer her puppy install to the windows pc I copied her
initrd.gz
vmlinuz
pup_215.sfs
files to the c: drive of the windows pc
(I got to these by running the master cd creator thingy)

When the windows pc boots I can select to boot into puppy and get a message saying pup_215.sfs has been found but then I get the message

Code: Select all

Bummer, could not run 'etc/init.d/rcS'
No such file or directory
Press enter to activate this console
Does anyone know what the problem might be?

Thanks in advance for any help
Ian
User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#2 Post by mikeb »

I got to these by running the master cd creator thingy)
are you using a remastered pup_215.sfs?..maybe try the original.

Are you using the same boot method/menu.lst as the other machine?

regards

mike
Bruce B

Re: Booting Puppy 'could not run etc/init.d/rcS'

#3 Post by Bruce B »

iansl2000 wrote: In order to transfer her puppy install to the windows pc I copied her
initrd.gz
vmlinuz
pup_215.sfs
Ian,

Yes Mike is correct. I want to add . . .

1) the chances of introducing a problem exists when remastering.

2) you didn't copy your daughter's install, if you missed the pup_save.2fs file, but probably the core files were in the remaster, but I can't say for sure what you did and for the purpose of my post, it doesn't matter, because, I recommend . . .

3) Back to square one, all you need to is copy all her files, and make your computer bootable. Puppy should adjust itself to the different hardware on your computer. At which point you will have a virtually identical install as your daughter's with less chance of introducing a snag.

Bruce
User avatar
iansl2000
Posts: 34
Joined: Thu 23 Mar 2006, 00:18
Location: UK

#4 Post by iansl2000 »

Gents,
Thanks for the quick replies.
My daughters instal was taking up the whole hard drive ie not a frugal one.
When I looked on her machine I couldn't find the files
initrd.gz
vmlinuz
pup_215.sfs

The only way I could find of obtaining them was to do the cd remaster, store the iso and associated files in a folder and copy them from there.
Is there another method?

Incidentally I went ahead and burnt a cd of the iso but when I tried to boot from that alone I got the same message so you right that there is a problem with the remaster process.

Where would I find the files I need?

Thanks again
ian
User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#5 Post by mikeb »

I think I know the problem.......certain kernel modules are in initrd.gz as they are needed as for booting.....

You will probably find your remaster is missing those files

can't quite recall the exact way they get lost but this is the basic gist...when my memory returns I will post more.

mike
User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#6 Post by mikeb »

brain working again..ignore last post

remastering from a full install see here

http://www.murga-linux.com/puppy/viewtopic.php?t=38625

mike
Post Reply