When i was updating with updimgr.sh my eon image my ssh session closed and i get a corrupted x86.eon file corrupted.
I' have tried to run it again and i get:
/usr/bin/updimg.sh /mnt/eon0/boot/x86.eon
Updating files in /mnt/eon0/.backup to x86.eon
backup in /mnt/eon0/boot/x86.eon.1
/mnt/eon0/.backup: OK
gzcat /mnt/eon0/boot/x86.eon > /tmp/x86.1947
gzcat: /mnt/eon0/boot/x86.eon: unexpected end of file
lofiadm -a /tmp/x86.1947 /dev/lofi/1
lofiadm: size of /tmp/x86.1947 is not a multiple of 512
mounting ... /dev/lofi/1 /mnt/upd
mount: /dev/lofi/1 or /mnt/upd, no such file or directory
I'm afraid of loosing my storage on a restart, can someone help me.
Thanks
I renamed the x86.eon and then copied x86.eon.1 to x86.eon.
Run updimgr.sh and every thing went perfect.
storagenode1:15:/mnt/eon0/boot#/usr/bin/updimg.sh /mnt/eon0/boot/x86.eon
Updating files in /mnt/eon0/.backup to x86.eon
backup in /mnt/eon0/boot/x86.eon.1
/mnt/eon0/.backup: OK
gzcat /mnt/eon0/boot/x86.eon > /tmp/x86.2420
lofiadm -a /tmp/x86.2420 /dev/lofi/1
mounting ... /dev/lofi/1 /mnt/upd
copying /etc/svc/repository.db
umounting ... /mnt/upd
lofiadm -d /dev/lofi/1
mv -f /mnt/eon0/boot/x86.eon.0 /mnt/eon0/boot/x86.eon.1
mv -f /mnt/eon0/boot/x86.eon /mnt/eon0/boot/x86.eon.0
gzip -f -9 -c /tmp/x86.2420 > /mnt/eon0/boot/x86.eon
/mnt/eon0/boot/x86.eon: OK
I have to reboot the storage to confirm that everything is ok.
Regards