[SOLVED] Backup entire installed Beowulf w/software + configs + /home?

fsmithred · 2021-03-12 19:16:46

ComputerBob wrote:

The symlinks that I mentioned are all on the USB stick itself. In Thunar, running on my actual HD, I don't see ANY actual files on that stick.
ls /media/computerbob/liveiso
lists the following
isolinux  live  pkglist_snapshot-20210311_1353

The ls command is seeing what is on the usb stick correctly. If you run df -h there should be a line that looks like this:

/dev/sdb1               807M  807M     0 100% /media/computerbob/liveiso

with the size of your iso instead of mine.

maybe running locate boot.ini will tell us where that file really is.

You don't need to format the usb, but it can't hurt. Whether you use cat or dd to image the stick, make sure you write to the whole device (/dev/sdb) and not to a partition (/dev/sdb1).

fsmithred · 2021-03-12 19:18:05

Right. You need to find the problem with the initrd. Look in the log to see what went wrong in the iso build process.

ComputerBob · 2021-03-12 19:28:25

NO BOOT.INI?

root@robinson:/home/computerbob# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            5.9G     0  5.9G   0% /dev
tmpfs           1.2G  1.1M  1.2G   1% /run
/dev/sda1       8.6G  4.0G  4.2G  49% /
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           2.5G  924K  2.5G   1% /dev/shm
/dev/sda2       8.5G  3.0G  5.0G  38% /home
/dev/sda6       247G   98G  138G  42% /media/data
none            5.9G     0  5.9G   0% /run/user/1000
/dev/sdb1       1.6G  1.6G     0 100% /media/computerbob/liveiso
root@robinson:/home/computerbob# locate boot.ini
root@robinson:/home/computerbob#

I don't think I would be capable of finding what went wrong in the build process.

I hope that maybe what I posted above says enought - no boot.ini. Does that mean that I should start over and try to re-create the iso itself (the only RefractaSnapshot iso that's currently on my HD)?

Last edited by ComputerBob (2021-03-12 19:37:32)

fsmithred · 2021-03-12 19:51:13

What you posted is strong evidence that the usb was imaged correctly. Use the email link to send me /var/log/refractasnapshot.log and I will look at it.

ComputerBob · 2021-03-12 20:45:19

fsmithred wrote:

What you posted is strong evidence that the usb was imaged correctly. Use the email link to send me /var/log/refractasnapshot.log and I will look at it.

I just sent it to you.

fsmithred · 2021-03-12 21:32:12

I don't see anything helpful in the log. It all looks good. Are there any messages above the boot error other than the ones you posted?

Mount the usb and run

lsinitramfs /media/computerbob/liveiso/live/initrd.img | grep resume

to see if conf/conf.d/resume exists. It should not be there, and if it is, that may be the problem.

ralph.ronnquist · 2021-03-12 22:07:11

If you can come to the (initramfs) you're doing well: that prompt comes from having loaded the boot kernel and set up the initrd. That means that the machine has booted from the USB but it now runs into problems for "pivoting", i.e., on the attempt to transition the root file system point.

So at that prompt, you might be able to do soome "machine inspection" to figure out what is wrong. You might even create a fatter boot initrd to have more tools, eventually if necessary.

The first thing to do is to get an idea of the boot kernel's picture of the disks. Use df and fdisk -l for that.

Btw, you should be able to inspect that initrd init script on the system before (or when) writing the USB. It should be originating from the file /usr/share/initramfs-tools/init (or similar, if different with live-tools installed; @fsmithred might know)

ComputerBob · 2021-03-12 22:10:55

fsmithred wrote:

I don't see anything helpful in the log. It all looks good. Are there any messages above the boot error other than the ones you posted?
Mount the usb and run
lsinitramfs /media/computerbob/liveiso/live/initrd.img | grep resume
to see if conf/conf.d/resume exists. It should not be there, and if it is, that may be the problem.

computerbob@robinson:~$ su -
root@robinson:~# lsinitramfs /media/computerbob/liveiso/live/initrd.img | grep resume
conf/conf.d/zz-resume-auto
scripts/local-premount/resume
usr/bin/resume
root@robinson:~#

ComputerBob · 2021-03-12 22:14:43

ralph.ronnquist wrote:

If you can come to the (initramfs) you're doing well: that prompt comes from having loaded the boot kernel and set up the initrd. That means that the machine has booted from the USB but it now runs into problems for "pivoting", i.e., on the attempt to transition the root file system point.
So at that prompt, you might be able to do soome "machine inspection" to figure out what is wrong. You might even create a fatter boot initrd to have more tools, eventually if necessary.
The first thing to do is to get an idea of the boot kernel's picture of the disks. Use df and fdisk -l for that.
Btw, you should be able to inspect that initrd init script on the system before (or when) writing the USB. It should be originating from the file /usr/share/initramfs-tools/init (or similar, if different with live-tools installed; @fsmithred might know)

computerbob@robinson:~$ su -
Password: 
root@robinson:~# df
Filesystem     1K-blocks      Used Available Use% Mounted on
udev             6131508         0   6131508   0% /dev
tmpfs            1229144      1080   1228064   1% /run
/dev/sda1        8987368   4117432   4393676  49% /
tmpfs               5120         4      5116   1% /run/lock
tmpfs            2578500       924   2577576   1% /dev/shm
/dev/sda2        8813184   3119228   5226552  38% /home
/dev/sda6      258857292 102270356 144674464  42% /media/data
none             6145708         0   6145708   0% /run/user/1000
/dev/sdb1        1669504   1669504         0 100% /media/computerbob/liveiso
root@robinson:~#

root@robinson:~# fdisk -l
Disk /dev/sda: 279.5 GiB, 300069052416 bytes, 586072368 sectors
Disk model: WDC WD3000HLFS-7
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4ECAB59F-E177-402A-8228-77D09EB1E966

Device        Start       End   Sectors   Size Type
/dev/sda1      2048  18397183  18395136   8.8G Linux filesystem
/dev/sda2  18397184  36438015  18040832   8.6G Linux filesystem
/dev/sda3  36438016  37640191   1202176   587M Linux swap
/dev/sda6  57970688 586072063 528101376 251.8G Linux filesystem

Disk /dev/sdb: 3.7 GiB, 4004511744 bytes, 7821312 sectors
Disk model: Cruzer          
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x3d2c28bb

Device     Boot Start     End Sectors  Size Id Type
/dev/sdb1  *       64 3339071 3339008  1.6G 17 Hidden HPFS/NTFS
root@robinson:~#

/usr/share/initramfs-tools/init (in Mousepad)

#!/bin/sh

# Default PATH differs between shells, and is not automatically exported
# by klibc dash.  Make it consistent.
export PATH=/sbin:/usr/sbin:/bin:/usr/bin

[ -d /dev ] || mkdir -m 0755 /dev
[ -d /root ] || mkdir -m 0700 /root
[ -d /sys ] || mkdir /sys
[ -d /proc ] || mkdir /proc
[ -d /tmp ] || mkdir /tmp
mkdir -p /var/lock
mount -t sysfs -o nodev,noexec,nosuid sysfs /sys
mount -t proc -o nodev,noexec,nosuid proc /proc

# shellcheck disable=SC2013
for x in $(cat /proc/cmdline); do
    case $x in
    initramfs.clear)
        clear
        ;;
    quiet)
        quiet=y
        ;;
    esac
done

if [ "$quiet" != "y" ]; then
    quiet=n
    echo "Loading, please wait..."
fi
export quiet

# Note that this only becomes /dev on the real filesystem if udev's scripts
# are used; which they will be, but it's worth pointing out
mount -t devtmpfs -o nosuid,mode=0755 udev /dev
mkdir /dev/pts
mount -t devpts -o noexec,nosuid,gid=5,mode=0620 devpts /dev/pts || true

# Export the dpkg architecture
export DPKG_ARCH=
. /conf/arch.conf

# Set modprobe env
export MODPROBE_OPTIONS="-qb"

# Export relevant variables
export ROOT=
export ROOTDELAY=
export ROOTFLAGS=
export ROOTFSTYPE=
export IP=
export DEVICE=
export BOOT=
export BOOTIF=
export UBIMTD=
export break=
export init=/sbin/init
export readonly=y
export rootmnt=/root
export debug=
export panic=
export blacklist=
export resume=
export resume_offset=
export noresume=
export drop_caps=
export fastboot=n
export forcefsck=n
export fsckfix=

# Bring in the main config
. /conf/initramfs.conf
for conf in conf/conf.d/*; do
    [ -f "${conf}" ] && . "${conf}"
done
. /scripts/functions

# Parse command line options
# shellcheck disable=SC2013
for x in $(cat /proc/cmdline); do
    case $x in
    init=*)
        init=${x#init=}
        ;;
    root=*)
        ROOT=${x#root=}
        if [ -z "${BOOT}" ] && [ "$ROOT" = "/dev/nfs" ]; then
            BOOT=nfs
        fi
        ;;
    rootflags=*)
        ROOTFLAGS="-o ${x#rootflags=}"
        ;;
    rootfstype=*)
        ROOTFSTYPE="${x#rootfstype=}"
        ;;
    rootdelay=*)
        ROOTDELAY="${x#rootdelay=}"
        case ${ROOTDELAY} in
        *[![:digit:].]*)
            ROOTDELAY=
            ;;
        esac
        ;;
    nfsroot=*)
        # shellcheck disable=SC2034
        NFSROOT="${x#nfsroot=}"
        ;;
    initramfs.runsize=*)
        RUNSIZE="${x#initramfs.runsize=}"
        ;;
    ip=*)
        IP="${x#ip=}"
        ;;
    boot=*)
        BOOT=${x#boot=}
        ;;
    ubi.mtd=*)
        UBIMTD=${x#ubi.mtd=}
        ;;
    resume=*)
        RESUME="${x#resume=}"
        case $RESUME in
        UUID=*)
            RESUME="/dev/disk/by-uuid/${RESUME#UUID=}"
        esac
        ;;
    resume_offset=*)
        resume_offset="${x#resume_offset=}"
        ;;
    noresume)
        noresume=y
        ;;
    drop_capabilities=*)
        drop_caps="-d ${x#drop_capabilities=}"
        ;;
    panic=*)
        panic="${x#panic=}"
        case ${panic} in
        *[![:digit:].]*)
            panic=
            ;;
        esac
        ;;
    ro)
        readonly=y
        ;;
    rw)
        readonly=n
        ;;
    debug)
        debug=y
        quiet=n
        if [ -n "${netconsole}" ]; then
            log_output=/dev/kmsg
        else
            log_output=/run/initramfs/initramfs.debug
        fi
        set -x
        ;;
    debug=*)
        debug=y
        quiet=n
        set -x
        ;;
    break=*)
        break=${x#break=}
        ;;
    break)
        break=premount
        ;;
    blacklist=*)
        blacklist=${x#blacklist=}
        ;;
    netconsole=*)
        netconsole=${x#netconsole=}
        [ "x$debug" = "xy" ] && log_output=/dev/kmsg
        ;;
    BOOTIF=*)
        BOOTIF=${x#BOOTIF=}
        ;;
    fastboot|fsck.mode=skip)
        fastboot=y
        ;;
    forcefsck|fsck.mode=force)
        forcefsck=y
        ;;
    fsckfix|fsck.repair=yes)
        fsckfix=y
        ;;
    fsck.repair=no)
        fsckfix=n
        ;;
    esac
done

# Default to BOOT=local if no boot script defined.
if [ -z "${BOOT}" ]; then
    BOOT=local
fi

if [ -n "${noresume}" ] || [ "$RESUME" = none ]; then
    noresume=y
else
    resume=${RESUME:-}
fi

mount -t tmpfs -o "noexec,nosuid,size=${RUNSIZE:-10%},mode=0755" tmpfs /run
mkdir -m 0755 /run/initramfs

if [ -n "$log_output" ]; then
    exec >$log_output 2>&1
    unset log_output
fi

maybe_break top

# Don't do log messages here to avoid confusing graphical boots
run_scripts /scripts/init-top

maybe_break modules
[ "$quiet" != "y" ] && log_begin_msg "Loading essential drivers"
[ -n "${netconsole}" ] && modprobe netconsole netconsole="${netconsole}"
load_modules
[ "$quiet" != "y" ] && log_end_msg

if [ "$ROOTDELAY" ]; then
    sleep $ROOTDELAY
fi

maybe_break premount
[ "$quiet" != "y" ] && log_begin_msg "Running /scripts/init-premount"
run_scripts /scripts/init-premount
[ "$quiet" != "y" ] && log_end_msg

maybe_break mount
log_begin_msg "Mounting root file system"
# Always load local and nfs (since these might be needed for /etc or
# /usr, irrespective of the boot script used to mount the rootfs).
. /scripts/local
. /scripts/nfs
. /scripts/${BOOT}
parse_numeric "${ROOT}"
maybe_break mountroot
mount_top
mount_premount
mountroot
log_end_msg

if read_fstab_entry /usr; then
    log_begin_msg "Mounting /usr file system"
    mountfs /usr
    log_end_msg
fi

# Mount cleanup
mount_bottom
nfs_bottom
local_bottom

maybe_break bottom
[ "$quiet" != "y" ] && log_begin_msg "Running /scripts/init-bottom"
# We expect udev's init-bottom script to move /dev to ${rootmnt}/dev
run_scripts /scripts/init-bottom
[ "$quiet" != "y" ] && log_end_msg

# Move /run to the root
mount -n -o move /run ${rootmnt}/run

validate_init() {
    run-init -n "${rootmnt}" "${1}"
}

# Check init is really there
if ! validate_init "$init"; then
    echo "Target filesystem doesn't have requested ${init}."
    init=
    for inittest in /sbin/init /etc/init /bin/init /bin/sh; do
        if validate_init "${inittest}"; then
            init="$inittest"
            break
        fi
    done
fi

# No init on rootmount
if ! validate_init "${init}" ; then
    panic "No init found. Try passing init= bootarg."
fi

maybe_break init

# don't leak too much of env - some init(8) don't clear it
# (keep init, rootmnt, drop_caps)
unset debug
unset MODPROBE_OPTIONS
unset DPKG_ARCH
unset ROOTFLAGS
unset ROOTFSTYPE
unset ROOTDELAY
unset ROOT
unset IP
unset BOOT
unset BOOTIF
unset DEVICE
unset UBIMTD
unset blacklist
unset break
unset noresume
unset panic
unset quiet
unset readonly
unset resume
unset resume_offset
unset noresume
unset fastboot
unset forcefsck
unset fsckfix

# Move virtual filesystems over to the real filesystem
mount -n -o move /sys ${rootmnt}/sys
mount -n -o move /proc ${rootmnt}/proc

# Chain to real filesystem
# shellcheck disable=SC2086,SC2094
exec run-init ${drop_caps} "${rootmnt}" "${init}" "$@" <"${rootmnt}/dev/console" >"${rootmnt}/dev/console" 2>&1
echo "Something went badly wrong in the initramfs."
panic "Please file a bug on initramfs-tools."

Last edited by ComputerBob (2021-03-12 22:22:53)

ralph.ronnquist · 2021-03-12 22:16:10

Well, you should do those commands at the (initramfs) prompt rather.

ComputerBob · 2021-03-12 22:25:10

ralph.ronnquist wrote:

Well, you should do those commands at the (initramfs) prompt rather.

I'm sorry - I did the first two commands in a terminal, and I copied the init file's contents from Mousepad.

I really have no idea how to get the initramfs prompt.

ralph.ronnquist · 2021-03-12 22:31:24

Hmm .. maybe I misunderstood, but isin't that what you refer to at post #25; it's where you come when you try to boot from your iso?

ComputerBob · 2021-03-12 22:46:38

ralph.ronnquist wrote:

Hmm .. maybe I misunderstood, but isin't that what you refer to at post #25; it's where you come when you try to boot from your iso?

No, you understood correctly. Do you want me to boot up my faulty USB stick, wait for it to crash, and then run those commands from that "crashed" prompt? That's the only way I know how to get that prompt, but I thought you were implying that I should get it some direct way. Sorry.

ralph.ronnquist · 2021-03-12 22:49:39

Yes, that's right.

Basically I suspect that that kernel sees a slightly different device enumeation than the live-boot preparation code expected, and wrote in into the initrd boot procedure.

fsmithred · 2021-03-12 23:29:07

conf/conf.d/zz-resume-auto should have been removed but wasn't. I suspect you may have had conf/conf.d/resume as well, and that one did get removed. If so, I need to adjust the code in the snapshot script.

When you get back into the working installed system, please look inside the initramfs for that system.

lsinitramfs /initrd.img | grep resume

Thanks.

ComputerBob · 2021-03-12 23:29:42

ralph.ronnquist wrote:

Yes, that's right.
Basically I suspect that that kernel sees a slightly different device enumeation than the live-boot preparation code expected, and wrote in into the initrd boot procedure.

I ran the two commands, and wrote down what their results were, so that I could then reboot to my HD, and type it all below:

df
Filesystem        1K-blocks      Used       Available     Use%     Mounted on
udev                    6131464         0             6131464       0%            /dev
tmpfs                   1229144         36            1229108       0%            /run

fdisk -l
sh: fdisk: not found

ComputerBob · 2021-03-12 23:33:38

(embarrassed) Well, I have no idea what I'm doing, but you're giving me great instructions on how to do it all anyway, so I'm happy to (try to) do it!

root@robinson:~# lsinitramfs /initrd.img | grep resume
conf/conf.d/resume
conf/conf.d/zz-resume-auto
scripts/local-premount/resume
usr/bin/resume
root@robinson:~# lsinitramfs /initrd.img | grep resume

fsmithred · 2021-03-12 23:40:39

Perfect!!!

ComputerBob wrote:

(embarrassed) Well, I have no idea what I'm doing, but you're giving me great instructions on how to do it all anyway, so I'm happy to (try to) do it!
root@robinson:~# lsinitramfs /initrd.img | grep resume
conf/conf.d/resume
conf/conf.d/zz-resume-auto
scripts/local-premount/resume
usr/bin/resume
root@robinson:~# lsinitramfs /initrd.img | grep resume

Here's the fix.
1. Make a backup copy of /etc/initramfs-tools/conf.d/resume
If you don't ever hibernate your computer, this step is not really necessary.
2. As root, edit /etc/initramfs-tools/conf.d/resume so that it contains only the following:
RESUME=none
Save the file.
3. Run update-initramfs -u
4. Make a new snapshot.

5. (Optional) If you do use hibernate, you need to undo what you did. Copy the original resume file back to where it was and run 'update-initramfs -u' again. If you do that, you'll have to do this whole procedure every time you want to make a snapshot.

ralph.ronnquist · 2021-03-12 23:48:57

Ok. You'll need some disk reflection tool... mabe blkid or lsblk are included in the initrd, or I suppose an ls /dev would tell something ... all being tried at the (initramfs) prompt.

The deal is that at that time, the kernel has been loaded with the initrd as root file system, and then the init scripting cannot find the device where the "real live filesystem" is (that we know to be on the USB). This means in particular that the system has booted so far as to load the kernel and then, eventually, come to run the /bin/sh (typciallly a dash shell) of the initrd.

Since you can come that far, you should be able to recreate the USB with more utilities in the initrd; a task I'm hoping @fsmithred can guide you to...

EDIT: .. just saw the above post... you might follow @fsmithred's lead first; mine is more of fumbling in the dark.

ComputerBob · 2021-03-12 23:50:09

I never use hibernate, so I think that means I only have to run steps 2, 3, and 4 (on my HD, not on the USB stick).

THANK YOU SO MUCH, EVERYONE -- especially dice, ralph.ronnquist, and fsmithred!

I hope to do those "fix" steps ASAP tomorrow. My brain says that running them will require the use of at least 10 brain cells, and I'm down to having only 4 remaining brain cells tonight.

Last edited by ComputerBob (2021-03-13 00:21:42)

dice · 2021-03-12 23:56:27

Im getting the exact same issue using qemu as well as bare metal.

This is a fresh snapshot.

qemu command as mentioned by alphalpa earlier in thread.

sudo qemu-system-x86_64 -m 2560 --drive format=raw,file=/home/snapshot/snapshot.iso

scrot ...

/etc/initramfs-tools/conf.d/resume already has RESUME=none

would a boot.log help from the prompt? How would i extract that from the qemu?

Last edited by dice (2021-03-13 00:14:04)

fsmithred · 2021-03-13 00:52:44

You can probably read /boot.log from the initramfs prompt. Try more /boot.log I don't know a way to get it out of there.

And try this to boot the iso:

qemu-system-x86_64 -m 2560 -cdrom /home/snapshot/snapshot.iso

You don't need to be root or use sudo for that.

ralph.ronnquist · 2021-03-13 01:34:52

Note that those are two quite different machine emulations. You should both add the -serial mon:stdio argument pair so that you can operate the qemu monitor and inspect the emulation. The monitor is then connected to stdin/out of the temrinal where you typed the qemu-system-x86_64 ... command, and you will "wake it up" by the C-A c sequence, which gives you the qemu monitor prompt.

At there, @dice would see, by the info block command, that the emulated hardware includes a disk (hd0), a cdrom (cd0) without media, a floppy reader (fd0) without media and an sd card drive (sd0) without media, whereas @fsmithred would instead not see any hard disk, but cd0 with media and fd0 and sd0 without media.

Going back to to OP case, I am guessing that the hardware seen by that boot is as per @dice, which would mean that the boot USB gets set up as the primary disk rather than as a cdrom (which the live-boot expects).

dice · 2021-03-13 04:48:12

fsmithred wrote:

You can probably read /boot.log from the initramfs prompt. Try more /boot.log I don't know a way to get it out of there.
And try this to boot the iso:
qemu-system-x86_64 -m 2560 -cdrom /home/snapshot/snapshot.iso
You don't need to be root or use sudo for that.

boot.log is like over 1800 loc. I have no idea how to extract it or even if it would be useful. I do know that around 1 month ago the snapshots i was creating were ok and would load into the live session.

I dont understand it so i cant really be much help im sorry.

@ ralph, so the raw/file is like booting a hard disk as apposed to just giving it the cdrom flag to boot the iso?
either way both just go to initramfs. Im not a qemu user or a virtual disk user for that matter so will rtfm.

fsmithred · 2021-03-13 14:29:26

I tried dice's qemu command (without the sudo) and my iso boots as cdrom or as disk. I'm pretty sure the problem is in the initramfs.

dice, please run:

lsinitramfs /initrd.img | egrep "resume|cryptroot|crypttab|askpass"

file -L /initrd.img

The officially official Devuan Forum!

#26 2021-03-12 19:16:46

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#27 2021-03-12 19:18:05

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#28 2021-03-12 19:28:25

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#29 2021-03-12 19:51:13

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#30 2021-03-12 20:45:19

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#31 2021-03-12 21:32:12

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#32 2021-03-12 22:07:11

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#33 2021-03-12 22:10:55

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#34 2021-03-12 22:14:43

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#35 2021-03-12 22:16:10

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#36 2021-03-12 22:25:10

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#37 2021-03-12 22:31:24

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#38 2021-03-12 22:46:38

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#39 2021-03-12 22:49:39

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#40 2021-03-12 23:29:07

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#41 2021-03-12 23:29:42

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#42 2021-03-12 23:33:38

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#43 2021-03-12 23:40:39

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#44 2021-03-12 23:48:57

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#45 2021-03-12 23:50:09

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#46 2021-03-12 23:56:27

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#47 2021-03-13 00:52:44

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#48 2021-03-13 01:34:52

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#49 2021-03-13 04:48:12

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

#50 2021-03-13 14:29:26

Re: [SOLVED] Backup entire installed Beowulf w/software + configs + /home?

Board footer