Skip Navigation

Posts
0
Comments
391
Joined
3 yr. ago

Living 20 minutes into the future. Eccentric weirdo. Virtual Adept. Time traveler. Thelemite. Technomage. Hacker on main. APT 3319. Not human. 30% software and implants. H+ - 0.4 on the Berram-7 scale. Furry adjacent. Pan/poly. Burnout.

I try to post as sincerely as possible.

  • That is not the case. In the context of btrfs, RAID-1 means "ensure that two copies of every data block are available in the running volume," not "ensure that every bit of both of these drives is identical at all times." For example, I have a btrfs volume in my server with six drives in it (14 TB each) set up as a RAID-1/1 (both data and metadata are mirrored). It doesn't really matter which two drives of the six have copies of a given data block, only that two copies exist at all.

    Compare it to... three RAID-1 metadevices (mdadm), with LVM over top, and ext4 (let's say) on top of that. When a file is created in the filesystem (ext4), LVM ensures that it doesn't matter on which pair of drives it was written, and mdadm's RAID-1 functionality ensures that there are always two identical copies of the file (on two identical copies of a drive).

  • There's no reason you couldn't; btrfs is pretty stable.

    Edit: Going on five years of using btrfs on production servers (storing and processing data on a 24x7 basis).

  • Hmm.

    Not being able to select boot order in BIOS suggests something very strange is going on, because it suggests that the BIOS can't see all the drives. That has to happen before the bootloader can be evoked.

    It sounds like GRUB is installed on the WD Black. BIOS -> drives it can see -> boot loader

    What was the specific error that the Arch boot attempt threw? How did os-prober work for you?

  • What boot loader are you using? That is what allows you to pick between what OS (in your case, drive) to boot at power-on.

    Are you using UEFI for this?

  • I'm not seeing anything relevant to lockups or crashes in there. Pretty boring logs.

  • I'm going to be building out a third wireless access point with OpenWRT to get better wireless coverage in the house.

  • Yeah, that should be fine.

    Anything in the kernel message buffer? dmesg -T | less

  • A classic! Way back when it used to be recommended on #linux as a good introductory text (until O'Reilly started publishing books on Linux, anyway).

  • Are you keeping an eye on system temperature?

  • Removed

    Thoughts on this?

    Jump
  • Neither do I. I've had a sensor net watching for Wayland news (because sooner or later I'm going to have to migrate to it, just want to know when) but so far there hasn't been any executive summary.

  • That is simple. About as simple as it gets. The more complex method involves figuring out what VPN software Mullvad really uses, figuring out your keying material, fighting with NetworkManager...

    tl;dr - Follow the directions.

  • A lot of folks don't know that you can do this. They just stick with the default install for whatever distro they're using. Articles like this aren't really for seasoned users, they're for relative newbies who didn't know.

  • I agree. Some of the Linux servers I used to run at work in the early 00's were 12 to 16 core monsters (for the time) and the kernel didn't even blink.

  • Agreed. Solid out of the box.