[opensuse] urgent desaster recover - need to revive a system or reinstall, still have access to etc and config files
Hi fellow lists participants, I have a hardware breakdown of an old HDD, and I need to revive a system/functionality really quick. I am a noob unfortunately when it comes to backuping/restore suse in simple ways especially with keeping config, users etc. I can still read kind of okay the old /etc/ and basically the root partition. I have already a new SSD at hand so I could quickly setup a clean leap 15.1 but how to make use of old config files instead of configuring all over again. especially keeping network interfaces information, some dhcp server config, some usernames. Cloning/rescuing the whole old HDD currently is estimated via clonezilla for another 3hours or more, so thats why I am wondering if i could just make use of the /etc/ folder and maybe others you guys hint that I would need. Can leap 15.1 installer make use of /etc/ and other dirs when they would be present even if the system would be incomplete Thanks for urgent help. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 14/01/2020 à 16:11, cagsm a écrit :
Hi fellow lists participants, I have a hardware breakdown of an old HDD,
what is on the broken hdd? What are the main apps that you really use
ways especially with keeping config, users etc.
keeping users is a matter of keeping /etc/password and /etc/shadow
I can still read kind of okay the old /etc/ and basically the root partition.
if so copy them to the new disk, only edit /etc/fstab
especially keeping network interfaces information,
if the hardware don't change, nothing have to be changed
Cloning/rescuing the whole old HDD currently is estimated via clonezilla for another 3hours or more, so thats why I am wondering if i could just make use of the /etc/ folder and maybe others you guys hint that I would need.
clonezilla is only really useful if you swap directly the two disks :-( better then have a backup of the system and an other backup of the data/users home (for next time :-() jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 14/01/2020 16.11, cagsm wrote: | Hi fellow lists participants, I have a hardware breakdown of an | old HDD, and I need to revive a system/functionality really quick. | I am a noob unfortunately when it comes to backuping/restore suse | in simple ways especially with keeping config, users etc. | | I can still read kind of okay the old /etc/ and basically the root | partition. I have already a new SSD at hand so I could quickly | setup a clean leap 15.1 but how to make use of old config files | instead of configuring all over again. | | especially keeping network interfaces information, some dhcp | server config, some usernames. | | | Cloning/rescuing the whole old HDD currently is estimated via | clonezilla for another 3hours or more, so thats why I am wondering | if i could just make use of the /etc/ folder and maybe others you | guys hint that I would need. Frankly, it is easier and more reliable to restore the image. If the backup is not fresh, you can copy on top those files you recovered, comparing if they are newer. | | Can leap 15.1 installer make use of /etc/ and other dirs when they | would be present even if the system would be incomplete No. It recovers just a few files, like the list of users and passwords, and fstab. The only method I know would be to do a fresh install with the same packages, and then copy the "other files" on top. Might not work well. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXh3uiQAKCRC1MxgcbY1H 1QyGAKCFLJ9tI88UlAoB0xKfXj/iOhSsngCfTrnIASBCnG3YWwf4IBlEESWBsas= =94CU -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Good afternoon! ...and then cagsm said... % % Hi fellow lists participants, I have a hardware breakdown of an old % HDD, and I need to revive a system/functionality really quick. I am a Ouch! Bummer :-( % noob unfortunately when it comes to backuping/restore suse in simple % ways especially with keeping config, users etc. I bet you'll do a better job after this ;-) % % I can still read kind of okay the old /etc/ and basically the root % partition. I have already a new SSD at hand so I could quickly setup a % clean leap 15.1 but how to make use of old config files instead of % configuring all over again. [snip] You're best off just doing a fresh install; you very definitely don't want to try blending the two. BUT what I would do (and have for other upgrades or migrations) is copy the old /etc tree off to a working temp tree to have it handy and then diff files such as group, passwd, shadow plus sshd keys (yes, I'm that lazy!) and smb config and such. Sometimes you can drop the old file into place (but back up the new one first, like by copying the new /etc tree also out to another safe place), and sometimes you can apply some diffs. Good luck :-) :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Thanks for all the info in this thread, eventually I installed a clean leap 15.1 on a new SSD. During the clean install, around the root user/password dialogue, leap 15.1 installer yast featured a button called something like import public keys, where i could even navigate some temporarily mounted paths pointing to the slowly dying old HDD and there I showed it the /etc/sshd/ path I think and there it listed some files, and I needed to select one, guess it did the correct thing and imported everything there needed to be. I think there was even a checkbox about importing sshd configuration as well. To make it short, the resulting final system when connecting to it via some old connected machines, never complained about changed public keys or anything, so I guess the installer / yast handled that import situation properly. TY. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 16/01/2020 à 17:06, cagsm a écrit :
anything, so I guess the installer / yast handled that import situation properly. TY.
glad you solved your problem :-) jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
cagsm -
Carlos E. R. -
David T-G -
jdd＠dodin.org