No space left on device - error

[dictum9]

Trying to build a system via Golden Image, booting off the Ignite Server, getting this error message:


.cpan/build/libnet-1.22/blib/man3/Net::libnetFAQ.3 : No space left on device
pax_iux: .cpan/build/libnet-1.22/blib/man3/Net::Domain.3 : No space left on device
pax_iux: .cpan/build/libnet-1.22/blib/man3/Net::Cmd.3 : No space left on device
pax_iux: .cpan/build/libnet-1.22/blib/man3/Net::FTP.3 : No space left on device
pax_iux: .cpan/build/libnet-1.22/blib/man3/Net::Netrc.3 : No space left on device
pax_iux: .cpan/build/libnet-1.22/blib/man3/Net::NNTP.3 : No space left on device
pax_iux: .cpan/build/libnet-1.22/blib/man3/Net::Time.3 : No space left on device
pax_iux: .cpan/build/libnet-1.22/Makefile : No space left on device
pax_iux: .cpan/build/libnet-1.22/pm_to_blib : No space left on device
pax_iux: .cpan/histfile : No space left on device
ERROR: Cannot load OS archive (HP-UX 11.23 CDE - 64 Bit OS)

The configuration process has incurred an error, would you like
to push a shell for debugging purposes? (y/[n]):

[James R. Ferguson · Accepted solution]

Hi:

And your question is? Are you sure you are booting what you think you are? Is the target disk large enough?

Regards!

...JRF...

[dictum9]

It has 3-73GB drives. I think it only picks up 2 during the install. And I think the original image encompassed 3 disks. that's my theory, I have to double check that.

Yes, I am certain I am booting the right machine.

[dictum9]

correction, the source machine (Where the Golden Image was taken) has only 2x73GB drives, so not sure what's going on.

[TTr]

It's probably stuffing the entire image (2 disks) in a signle disk.

You should interrupt the ignite process and go in the configuration screens and add another disk as needed.

[Steven E. Protter]

Shalom,

Step back.

What is the size of the image?

I don't care what the disk size of the imaged system is, that is meaningless.

What is the bdf output of the source system?

That is a good measure, at least for the volume groups in the image for how much target space is needed.

Ignite has an interface that lets you as part of recovery change file system sizes to adjust for different disk environments.

Your golden image configuration file on the Ignite server needs to include information on the disk size and layout for the target/client system.

You seem to be the victim of your own lack of planning at this point.

SEP

[Scot Bean]

Part of the golden image setup is to run ' /opt/ignite/lbin/archive_impact -t -g ' on your image and save the results in your config file.

Did you do this?

If you did, Ignite should know how big your image is and prevent you from trying to install it on a target that is too small.

[dictum9]

Yes I did ran archive_impact -t -g

and put the results in /var/opt/ignite/data/Rel*23/core_archive.cfg


Not only that but added all 3 73GB drives to the pool during the install. The original image had 2 73GB drives.

Still blows up during the install due to "No space left on device". How is that possible?

[dictum9]

Could this be because I did not run save_config?

[Scot Bean]

Perhaps. Incorporating some save_config syntax in your golden image config can help replicate disk volumes as they were setup on the original machine.

Without that, you'd need to setup your disks, volumes, and filsystems interactively on install in the "File System" tab.

[Steven E. Protter]

Shalom,

How the golden image transfers does depend on the original system layout.

Having the previous steps done and built into the Ignite image configuration will help.

However, what you are reporting should not happen.

Take a look at vgdisplay -v vg00 and lvdisplay -v on each logical volume on the source system. You should be able to find the issue and adjust the Golden Image configuration on the server side to compensate.

Remember, the process is guided by booting off the Ignite server, transferring the image file, and laying out the system as specified in your configuration file, on the server.

SEP

[Jase1]

Increasing the Ram Simm Chips Memory be a simpler solution.

[Dennis Handly]

>Increasing the RAM memory be a simpler solution.

Not hardly, we are talking about disk space, not memory.