Good Day,
I've been trying to create a bootable recovery disk with no success. I've used the command . /make_recovery -A -d /dev/rmt/1m and get the command HP-UX System Recovery returned, and after about a minute an error is returned:
/var: write failed, file system is full
/var/tmp/uxinstlf.recovery: No space left on device
./make_recovery(226) prealloc failed. At least 32MB disk space needed.
./make_recovery(228) make_recovery(1m) encountered a fatal error.
./make_recovery(230) Please fix errors and try again.
Cleanup
So I've tried to erase the disk to create space, using the commands:
but all these attempts have the "unknown command" error returned to me.
I've tried tar -cvf /dev/rmt/1mn with no luck either.
I then tried mediainit -v /dev/rmt/1mn which was accepted and worked, however, when I once again tried the ./make_recovery -A -d /dev/rmt/1m command, I still got the same error again(no space).
Okay, you're trying to create a mag tape that you can boot from? Yes?
One point is that most such scripts (creating bootable media of any type) stage themselves off working disk space so you'll need to ensure that the filesystem that the script wants to use as working space is not nearly full.
Come on guys! Where are the HP-UX experts who really know how this works?
Dunno. Try taking a look at the script "make_recovery" and see what it's doing and where it tries to put stuff.
NOTE TO MODERATORS: Although the OP has posted this in dummies it's not such a dumb question. Can we move the thread to HP-UX please where the right guys will see it. Thanks.
If it is /var/temp directory you need to know what filesystem that is on. Are any of your filesystems filling up? Of course, if it's an old system with small drives and you are trying to create a full system image, I guess that could be a problem. Try running it again and from another terminal run
df -v
repeatedly and see if a filesystem hits the top when you get the error.
I would start by giving more information on your system, is it (hopefully...) a server if so what model...
next we would need the ouput of bdf in order to tell you if it makes sense to use -A option and why your system is complaining (/var full? is it so?)
Hi All, thanks for the input so far. Okay, so I've got the info you've asked for, I hope this is what you wanted, new to unix, so apologies in advance.
#
df -v
/home (/dev/vg00/lvol5 ) : 1 % used blocks
606 used blocks
39116 free blocks
/opt (/dev/vg00/lvol6 ) : 81 % used blocks
385330 used blocks
85240 free blocks
/tmp (/dev/vg00/lvol4 ) : 0 % used blocks
44 used blocks
61150 free blocks
/users (/dev/vg00/lvol7 ) : 87 % used blocks
91158 used blocks
12436 free blocks
/usr (/dev/vg00/lvol8 ) : 80 % used blocks
535280 used blocks
126906 free blocks
/var (/dev/vg00/lvol9 ) : 89 % used blocks
350384 used blocks
41482 free blocks
/stand (/dev/vg00/lvol1 ) : 17 % used blocks
16494 used blocks
79164 free blocks
/ (/dev/vg00/lvol3 ) : 48 % used blocks
80516 used blocks
86950 free blocks
Yeah but the command isn't recognised on this system.
Find below the info you've requested:
# vgdisplay vg00
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 9
Open LV 9
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 2000
VGDA 2
PE Size (Mbytes) 4
Total PE 1023
Alloc PE 284
Free PE 739
Total PVG 0
# vgdisplay -v vg00
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 9
Open LV 9
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 2000
VGDA 2
PE Size (Mbytes) 4
Total PE 1023
Alloc PE 284
Free PE 739
Total PVG 0
--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 48
Current LE 12
Allocated PE 12
Used PV 1
LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 128
Current LE 32
Allocated PE 32
Used PV 1
LV Name /dev/vg00/lvol3
LV Status available/syncd
LV Size (Mbytes) 84
Current LE 21
Allocated PE 21
Used PV 1
LV Name /dev/vg00/lvol4
LV Status available/syncd
LV Size (Mbytes) 32
Current LE 8
Allocated PE 8
Used PV 1
LV Name /dev/vg00/lvol5
LV Status available/syncd
LV Size (Mbytes) 20
Current LE 5
Allocated PE 5
Used PV 1
LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 236
Current LE 59
Allocated PE 59
Used PV 1
LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 52
Current LE 13
Allocated PE 13
Used PV 1
LV Name /dev/vg00/lvol8
LV Status available/syncd
LV Size (Mbytes) 332
Current LE 83
Allocated PE 83
Used PV 1
LV Name /dev/vg00/lvol9
LV Status available/syncd
LV Size (Mbytes) 204
Current LE 51
Allocated PE 51
Used PV 1
--- Physical volumes ---
PV Name /dev/dsk/c0t6d0
PV Status available
Total PE 1023
Free PE 739
# swapinfo -tam
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 128 0 128 0% 0 - 1 /dev/vg00/lvol2
reserve - 54 -54
memory 41 7 34 17%
total 169 61 108 36% - 0 -
Do you know how to go single user with this box? Is it using X11? If so do you know a minimum of command line in text more if you find yourself without windowing system, and hopefully in from of what should be a console tty, or better it has a dedicated console attached...
Just checked, depending of how it was installed OnlineJFS may not show up with the given command, only when you try... If You have a GUI then as root try to launch sam: sam & go to disks and filesystems, choose logical volumes, and click on lvol9 then in the top menubar choose Action-> Increase size and int the new window enter 500
I know how to interrupt the Autoboot, and change the Mode Configuration from 'OEM' to 'USER'. I don't know what X11 is, or how to check it. And the third sentence you've got me completely lost:o
X11 is the unix graphical environment (windowing system...).
I have no idea what a 743 looks like only that it used similar boards and CPU as 712/715 that I had long ago... (but never migrated to 10.20 and left them in 9.5...)
So I should ask more: What kind of terminal are you working on...
Addendum:
What I wanted to know is can you execute the above, and if so what happend (did the system complain or did it do what was asked ( LVM extension...)
If you dont have GUI (yes pretty colors X system...) then we are to do all in command line from the console as root...
Okay I've tried to increase the size using sam, but it requires the services to be stopped, and the guys here will only allow me to try that on Monday.
Check out this link for the 743 board: Agilent / HP 743 - In Stock, We Buy Sell Repair, Price Quote
OK so you have seen what you can do then... If you had OnlineJFS it would have done the job...
Did you use sam in graphic mode or was it a vague txt gui?
I will explain a bit more:
You could have from command line as root extended the logical volume:
lvextend -L 500 /dev/vg00/lvol9
but to increase the filesystem's size you are to have nobody using it in order to unmount it, only problem is many things use /var especially all the logging systems in /var/adm so the only chance it to go single user ( boot and no filesystem mounted or just /...) mount what you need : / , /stand should be there, /usr for the commands but you cannot use sam anymore because sam uses /var...
Either you go savage way like init s
then
umount /var
#or
umount /dev/vg00/lvol9
# then extend the filesystem:
extendfs /dev/vg00/rlvol9 # Very important the "r" for raw device
# then lazy way to mount all:
mount -a
#now save the configuration:
vgcfgbackup vg00
I think I havent forgotten anything, but its difficult to imagine like the in front of a PC what you are to do on a box ..
Reboot or check behaviour :
init 2
init 3
Dont think you use 4 ( but I do... so check in /etc/inittab : the init default value...)
