On Sat 11 Jun 2022 at 19:41:34 (-0400), gene heskett wrote:
On Saturday, 11 June 2022 13:32:54 EDT gene heskett wrote:
On Saturday, 11 June 2022 11:47:46 EDT gene heskett wrote:
Let me go look at synaptic on the remote machine I've been using to
see if its installable. yes, but it tab-less, no menus at all. but I
just discovered whatever terminal is std in that bullseye install,
xfce I think, CAN use the mouse to copy text so I'll use that for
the next remote screen install. The drive is partitioned, but
partition mount points have not been defined.
And I'm back from install 28, booted to the old install, the bios
cannot see the drive I just installed to. So whats next? update the
bios? I'll make mnt points and look at it. but the install went
nicely. It just won't even see it to boot it. Can I shut down and
swap cables to make this drive the first plug rather than the 5th of 6
mainboard plugs?
Actually I did better than that, I shut down and ripped it out to a table
and re-arranged ALL the drive cables and got rid of 3 drives and about 5
feet of power cable splitters but lost 3 fans cuz their 3 pin plugs
aren't compat with the 4 pinners on this 2 yo mobo. I also moved the raid
drives which were in a place in the rack w/o any cooling, about a foot
higher in the tower in a 4 slot cage with a big fan for a front door.
And while it will boot from the selected drive, I'm still running on the
old ibstall because I cannot mount /dev/md0p1 over the home diretory when
booted to the latest install. claims the mount is already done which it
isn't, or the mount point is busy. Presumably because I'm logged into the
non-raid /home/gene on the booted drive. I cobbled up a UUID based mount
line in /etc/fstab, but apparently the raid10 will not assemble.
I can mount the new drive from this boot, so what should I look at to get
it to pre-assemble and mount /dev/md0p1 and ditto for md1, the swap thats
on the raid10 too, all before I log in so its not busy?
In case you hadn't noticed, root doesn't have $HOME on /home
(unless you've adopted the Easthope scheme). I don't know what
the sudo-exclusive people do. For decrypting /home remotely,
I set up a special user that only performs that task (in order
to avoid logging in as myself or root).
Thanks all, I think I'm making progress. But apparently I'm a new bee at
raid stuff. Hmmm, I just noted that htop is showing zero swap. Checking
fstab against blkid, shows swap with a totally different blkid.
I'll see if I can do a copy paste to fix that. Yup, a root swapon -av and
now I have swap. And /opt was missing too, its on the raid but empty so
that was added by copy/paste. A simple mount /opt fixes that.
Now, are these bklid's stable enough I can mount the bigger drive and
just copy this fstab over the existing one?
AFAIK, blkid is a command that lists attributes or messes up your
system. Hence this, in bold, from its man page:
It is recommended to use lsblk(8) command to get information about
block devices, or lsblk --fs to get an overview of filesystems, or
findmnt(8) to search in already mounted filesystems.
So it's the attributes that should concern you, like LABELs and UUIDs.
In your narrative above, you'll probably lose swap each time you
reinstall, because you've set a swap in the partitioner. I always
avoid that. Any 21st century PC should be able to install with
needing to swap.