View Single Post
Old 07-01-2012, 10:59 AM   #87
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by eureka View Post
It's also [obviously] OK and safe to boot into main, manually mount diags and dump diags to /mnt/us.

Just clarifying things.
Perhaps by the time that you have an SSH shell. But in my experience, backups made by a RUNME.sh script (run DURING startup) can cause corrupt partitions. So it all depends on WHEN you do it. From a RUNME.sh, the safest way is to dump a partition after booting from the OTHER partition (a bit hard to do on a K3).

I like to tell people a fairly simple way that should always work. Originally, I wanted 5.1.1 backups that were virgin (not hacked -- only data.tar.gz and RUNME.sh that do not modify anything but the USB drive and /var/local, but should not be done from a booted partition to prevent corruption.)

Yes, when running SSH prompt AFTER the framework has finished loading, you are probably safe to dump both partitions, but again, I have gotten corrupt partitions a bit too often for comfort and just stick with "dump the OTHER partition" (which always works). I like methods that ALWAYS work.
geekmaster is offline   Reply With Quote