I have two disks: nvme0n1 and nvme1n1. I was planning on using Logical Volume Manager? 2 and someone else told be BTRFS was better, so I looked into it, and sure enough, it looked better for my use-case. I created the btrfs file systems for each partition pair (/nvme0n1p3 and /nvme1n1p3) and 4. Now, I am trying to get to the next step of installation, in which I mount my partitions / volumes and then install the necessary linux packages.
#/sbin/init not found...
656 messages · Page 1 of 1 (latest)
Hi, what setup are you trying to achieve? Do you want to put everything (/, /home) in one partition as subvolumes then use the 2nd partition just for storage or split them etc / in one partition and /home in the other partition? Are you also planning to use btrfs snapshots? Have a look in https://wiki.archlinux.org/title/Btrfs .
Within a btrfs partition, you can create subvolumes to put traditional Linux partitions (etc /, /home) https://wiki.archlinux.org/title/Btrfs#Subvolumes .
Usual setup on a single btrfs partition is to create subvolumes for / and /home so that you can snapshot / without including /home data. You usually mount the btrfs partition to /mnt then create subvolumes in /mnt etc btrfs su cr /mnt/@home && mkdir -p /mnt/home. You then umount /mnt and mount root subvol then other subvol with the folder path etc mount -o compress=zstd,subvol=@home /dev/nvme0n1p2 /mnt/home/. After mounting all subvolumes you would mount esp (mount --mkdir /dev/efi_system_partition /mnt/efi) then continue with your arch install.
By bindings do you mean mount options? See https://man.archlinux.org/man/btrfs.5#MOUNT_OPTIONS
ESP setup is independent of btrfs and is the same process for all filesystems (just need to mount esp and install bootloader to it in chroot).
Also in order to boot into a btrfs root subvolume, you need to use this kernel parameter rootflags=subvol=/path/to/subvolume (this step is commonly missed) https://wiki.archlinux.org/title/Btrfs#Mounting_subvolume_as_root
trying to evenly storage split them. i have /boot for my first partition, /swap for my second partition, / for my third partition, and /home for my fourth partition. When I refer to bindings I mean taking two partitions and treating them as one using BTRFS
I don't really care about subvolumes or snapping unless they help me achieve making two partitions into one
also please ping me when you have a response so I know to check here
@hexed isle sorry I'm not familair with mutli-disk setups but I believe it should be pretty much the same process where you just treat the 2 disks as partitions (can mount / to a partition disk 1, /home to a partition disk 2). Grub/systemd-boot/uki can all boot into /boot in btrfs so you don't really need a separate /boot partition. Also on btrfs a swapfile is generally recommend to be used over a swap partition. If you're not planning to use subvolumes I think you just need mount the path without subvol etc mount -o compress=zstd /dev/nvme0n1p1 /mnt/home/. If you want to evenly split data across 2 disks (treat 2 disks as a single btrfs partition), have a look into raid 0 ( I'm not familiar with it) https://wiki.archlinux.org/title/Btrfs#Multi-device_file_system
why not a swap partition?
how am i supposed to limit the RAM a swap file takes up?
you can use swap partition, swapfile is just more flexiable (can resize easier)
it will be as large as the swapfile size you set it to be
are you planning to use swap for hibernation? If you don't need hibernation you could try using zram instead if your ram is not too little
yeah i would like to hibernate idk how to set that up though
to hibernate i think you have to use a swap partition
you set the kernel parameter resume=UUID=<UUID of swap partition>
Not sure what you mean by "bindings". If you mean what gets mounted where, that's managed in /etc/fstab.
You mount BTRFS partitions like any other filesystem. mount /dev/<partition> <mountpoint>; if you want to mount a specific subvolume on that partition, then you pass it as a mount option. You can use the subvolume ID, path, or both. example: mount /dev/<partition> <mountpoint> -o subvol=my-subvol (if the subvolume is called my-subvol)
The ESP has to be FAT32. There's no way around that.
@hexed isle
sorry that was stupid language to be using when i say bindings i mean how would i mount two partitions connected by btrfs under root?
ah, so a multi-device filesystem?
yes
thats what i am trying to achieve
i have 2 disks with 1 root, 1 home, and 1 swap partition each, and i want each root and home to be treated as one respectively
does that make sense
Yeah, give me a moment, I'm lagging balls running out of ram building chromium on Gentoo 😂
I know how to do this
i'm assuming they are currently separate file systems
and you want to join them together
alr
i used the mf.btrfs command and specified both devices
for the root and home points
oh
okay so you should have a mult-device file system
if you do lsblk -f
you should see that both of those partitions have the same UUID
they do
okay
yeah
alright
do you have that file system mounted anywhere
no
can you mount it somewhere
so we can see what type of RAID it's doing
sudo btrfs device usage <mountpoint>
it should show info for both disks
for example, i have 2 500 GB hard drives in RAID0 (striping, no redundancy)
$ sudo btrfs device usage /media/hdd_root
/dev/sdb1, ID: 1
Device size: 465.76GiB
Device slack: 0.00B
Data,RAID0/2: 444.75GiB
Metadata,RAID10/2: 21.00GiB
System,RAID10/2: 8.00MiB
Unallocated: 1.00MiB
/dev/sdc1, ID: 2
Device size: 465.76GiB
Device slack: 0.00B
Data,RAID0/2: 444.75GiB
Metadata,RAID10/2: 21.00GiB
System,RAID10/2: 8.00MiB
Unallocated: 1.00MiB
the metadata and system info part of the filesystem is striped and mirrored but the data is only striped
if it's not already in the RAID mode that you want, you can change it
i have to mount both partitions?
no, mounting any of them mounts the whole file system
it will automatically figure it out
lsblk will only show one partition as being mounted to that mount point, but that is normal
$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
...
sdb
└─sdb1 btrfs df02f1c1-fe1d-4e2a-939d-4a8bfb4c9ed0 42.8G 94% /media/storage
/media/hdd_root
sdc
└─sdc1 btrfs df02f1c1-fe1d-4e2a-939d-4a8bfb4c9ed0
sdd
...
ok good i mounted it and it showed both partitions
okay
are you putting them together because you want redundancy, because you want speed, or because you just want one big block of storage instead of 2?
third
i just want them to function as one
2x the storage
okay
1 TB is not enough
can you show this
it shows the same except the first one (ID 1) has the Data thing but it says Data,single and the second one just doesnt have the data thing at all
/dev/nvme0n1p3, ID: 1
Data,single: 8.00MiB
/dev/nvme1n1p3, ID: 2
(doesnt have the data thing at all)
everything else matches up with yours aside from the storage space differing from 440 something GiB to 600 GiB
man im so mad rn that was so counterintuitive i didnt know I had already done it for the most part
i thought there was a separate device kinda like when you use mdadm
sudo btrfs balance start -dconvert=raid0 -mconvert=raid10 <mountpoint>
this will change your disks to RAID0 (striping, no redunancy, combined capacity, extra speed)
depending on how much data you have stored, it might take a while because this will reallocate everything
i have no data whatsoever lol (im installing using bootable media usb)
it should be fast then
i dont wanna boot into arch until im 100% sure i got the core components done since i dont wanna fuck up
i learned my lesson after using archinstall that you should do things your way
you can see if it's done with btrfs balance status <mountpoint>
are all mountpoints predefined?
what are all the mountpoints i know /mnt and /home are some
wherever you mounted it
no i know but if i type in /mount /dev/nvme0n1p3 /regdufhiotgdfj it errors
partitions are either manually mounted by you, or automatically mounted at boot at spots defined in /etc/fstab
that's because regduf... doesn't exist
ok
if you make that directory then it would work
so i need to edit fstab before im finished correct?
that way it knows what to mount
arch comes with a tool to generate it automatically based on what you have mounted manually during installation (genfstab)
that's part of the installation guide
it sees what you have mounted at /mnt
well yeah i know
i have a swap partition cause i prefer it that way i used the mkswap
yeah
if you did swapon then genfstab will see that swap partition and add it to the fstab for you as well
holup why raid10
it just makes it a bit safer in the event of disk damage
highly unlikely that it would ever save your ass, but it just writes metadata to both drives
you can do raid0 if you want, but it doesn't cost much space and should have no performance impact

what is dconvert and what is mconvert
converting the data and metadata into the specified raid levels
see man btrfs balance
cool
that is the amount of data currently stored
i think
well it allocates space in advance
not like i give a shit about the extra 2GiB
you will probably want to edit the fstab after generating it to enable things like automatic TRIM/DISCARD and/or compression
i use compress-force=zstd and discard=async
hold on im just removing this random ass artifact left behind by mdadm back when i was fiddling with that it will take me another 30 sec
ok so i dont know how i managed to do this
but nvme0n1p1 and nvme1n1p1 are both synced via raid
not btrfs
you should disable that
ok so context i was working on trying to use lvm and was told btrfs was better so i switched to that and the arch wiki was weird and told me to made two separate esp parts and then make a volume out of them
because that's likely to corrupt what btrfs is doing
i'm surprised it hasn't broken it already lol
i dont need both
i have no idea how mdadm works
it was a silent error cause i wasnt running lsblk with -f
you only need 1 esp
im not gonna fuck around and find out anyway
the fact that this btrfs even works is awesome
alright im rebooting
uh idk it said something weird
oh you're just restarting the iso
almost im past the btrfs it seems
im not in it yet
have you made subvolumes for root and home
it's not required
however
if you ever want to mess with snapshots
you will want to have subvolumes
im still confused about the whole snapshot things
i have a basic idea of what they are
but i dont quite understand them
so when you make a snapshot of a subvolume
you are just marking a point in time, and the data that existed then won't get deleted
there is a concept called Copy-on-Write
you make copies of things, but the actual data only exists in one place on your drives
you just have two pointers to it
yeah i've heard about that
if you take a snapshot
and then delete files from what you took the snapshot of
or modify them
that data doesn't get deleted
it just gets marked as deleted in the subvolume
but still accessible through the snapshot
only once no subvolumes or snapshots reference a piece of data, does the data actually get deleted
when i make these subvolumes do these become new devices?
no
subvolumes are kinda like folders
except it's possible to mount them like they're devices
with the subvol= mount option
but if you just mount the device by itself without a subvol parameter
you can see all the subvolumes on it as directories
and access them like directories
and subvols can be nested in other subvols just like directories
ok but to make a root and home subvolume and then use that normally i'd do this?
yeah, so for example if you had subvolumes @ and @home for root and home, you would mount it like
mount /dev/nvme0n1p1 /mnt -o subvol=@
mount /dev/nvme0n1p1 /mnt/home -o subvol=@home
but if you just did mount /dev/nvme0n1p1 /mnt and looked inside /mnt, you would see @ and @home as directories
the @ is just a common naming scheme for subvolumes, they can be named anything though
alright how do i create a subvolu,e
mount /dev/nvme0n1p1 /mnt # mount the root subvolume (meaning without a subvol= parameter)
cd /mnt
btrfs subvolume create @
btrfs subvolume create @home
but then i would need to unmount it and do this right
if it's already mounted then you can skip the mount
swap partitions are just swap
your esp should be fat32
it's easy to fix if they're messed up
idk it says vfat swap but then for the fat32 there is a 1 by both swap partitions
$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 vfat FAT32 F586-E5F2 255.7M 0% /efi
└─sda2 btrfs 277c70af-ffb7-437b-8e90-37d37dda1052 247G 71% /home
...
nvme0n1 swap 1 d3e204d3-0390-47e1-b563-5914a3a8d285 [SWAP]
sda1 is my esp and nvme0n1 is my swap
YES
THATS WHAT IT LOOKS LIKE
that is correct
you have 2 swap partitions?
could you post the output of lsblk -f
not a problem, you can just enable them both
imma seal up all my cracks they gonna keep coming back
it needs to just be a regular fat32 partition
yep
i dont know how to destroy that
wipefs?
every restart that shit comes back bro
there is some metadata doing it
you could try just mkfs.fat -f -F32 /dev/nvme0n1p1
this should forcibly overwrite whatever's in there
there may be a specific way you are supposed to uninitialize the raid thing
overwriting it might make the kernel mad
not sure
why do you have 2 btrfs partitions on each drive
i just noticed
because the p3 on each is the root and the p4 on each is the home
lol
the way we've done the subvolumes
sigh if i need to make a correction just say
root and home are on the 2 partitions you made into a multi-device fs
yeah
do i need to merge into one part?
i can do that with ease they dont have anything valuable on them
they arent even mounted rn
yeah
yeah
i'm assuming we've been working with p3 of each drive and that's what you're calling root
is that right
yes
yeah so i would delete p4 of each drive and expand p3 into that space
ok so gdisk has a partition type called Linux x86-64 root (/) whats the deal with that
gpt
the type should be "Linux filesystem"
done
alright let me check if everything is in order
deleting the p4 shouldve wiped the file system or?
technically no, but that doesn't matter
you could recreate the partition at the exact same spot and you would see btrfs there again
but when you expand p3 into that space it doesn't make a difference
where exactly is all that data stored if not in partitions?
about the file system and such
the filesystem is stored in the part of the disk specified in the partition table
partitions are just a way to divide the disk into parts of certain sizes
modifying the partition table to remove a partition just removes the record of that partition exisiting in the space
unless you actually write zeroes to that part of the disk then the filesystem will still be there
the actual partition table is a very small piece of data stored at the beginning (and i think also the end) of the disk
what's stuck
the usb
what does it say
idfk
i rebooted and then unplugged it
put it back in
and now nothing is being detected as a boot option
and
its in the uefi menu
it shouldn't be possible to corrupt it, nothing should write to the usb
turn pc off, replug usb, then turn on again
ok there what the hell happened there
did it work?
how do i check if btrfs is working again
so i mount the partition and then i run a command
@solid granite
yeah mount it and check btrfs filesystem df /mnt
you should see total=xxx where xxx is the size of the partitions combined
if it's smaller than it should be, then the fs needs to be grown
how do i get this
the first line is the command that i ran
you would just leave out sudo and do /mnt instead of /media/hdd_root
oh yeah that shows device size as well
in this command, are your 2 devices ID 1 and 2? or is it something else like 0 and 1
no its ID:1 and ID:2
ok
just checking
ok
btrfs filesystem resize 1:max /mnt
btrfs filesystem resize 2:max /mnt
if the disks contained any data then it would be wise to do a btrfs balance start /mnt but since they're empty i don't think it's needed
yes
nice
created + mounted subvols
@ is at /mnt and @home is at /mnt/home?
that won't work
you need to umount /home
and then?
it probably failed because the directory you're trying to mount it to doesn't exist
it did
so you need to mkdir /mnt/home
/mnt/home did exist? or it did fail for that reason
alright done
okay
also don't forget
mkdir /mnt/boot
mount /dev/nvme0n1p1 /mnt/boot
i think that was the esp partition
and swapon both of your swap partitions
i did
and now
im having another problem yaaayyyyyyyyyy
pactrap isnt working
some bullshit about my kingring
keyring
keyring is not writable
try
pacman-key --init
pacman-key --populate
pacman -Sy archlinux-keyring
there are sometimes issues with the keyring if the iso is out of date
Trust database could not be updated
its not
archlinux-2023.08.01-x86_64.iso
as recent as 9 days ago
had to ask
silly arch
mount /dev/nvme0n1p1 /mnt -o subvol=@
mount /dev/nvme0n1p1 /mnt/home -o subvol=@home
that should be p3 right?
yes
im just pasting it down here so i can remount everything
im manually typing everything over
you can make code blocks
```
like this
```
like this
i have no idea what's up with that
pacman-key --init worked this time
keyring fixed?
ok so
my keyring was having problems
and i think that was what happened when i tried archinstall before going manual
ok so uh
whats up with this
i arch-chrooted in
so did you fix the keyring and do the pacstrap?
i did the locale-gen but locale.conf doesnt exist
yes
edit /etc/locale.gen and uncomment the local
whatever you installed
what comes with the base
you can just pacman -S nano
nothing afaik
do you know vim?
if not just get nano
OH THANK GOD ITS NOT DOING THAT CHROOT SHIT OMG
"RUNNING IN CHROOT" IT USED TO DO THAT
then locale-gen
also you should link your timezone ln -sf /usr/share/zoneinfo/<Region>/<State>/<City> /etc/localtime you can tab through to complete and find yours
echo LANG=en_US.UTF-8 > /etc/locale.conf
export LANG=en_US.UTF-8
OH RIGHT SO ABOUT MY BOOTLOADER
do i use grub or systemd
which one is better for this
preference imo, but I prefer systemd boot. however I never used BTRFS
is the package just called systemd?
oh
however it's there already and you don't need to install anything extra
how do i install systemd and systemd boot on my arch installation
machine-info isnt working and thats a command bundled with it according to the arch wiki
well the difference is that grub is more automatic and abstracted, systemd you got to manually edit some files
machine-info I believe won't work in chroot, I think only on the archiso before you chroot
not working there either weird
maybe they mean etc/machine-info that you can cat?
although I don't have it locally
I wrote this little guide if you wanna follow the sections inside systemd boot https://github.com/yenaras/laptop.config/blob/main/docs/systemd_arch_install.md#systemd-boot
just swap nvim with nano
ok
this is while chrooted in
also replace /dev/sda3 with your root partition
can check the sections above too if you want
to double check what you done so far that's not btrfs related
wdym
Whatever you are putting root on
Basically whatever /mnt was mounted to
Root is the base of your linux
All your system shit
In my guide /dev/sda3 was the root partition
It's not the case for me now, but I wrote that a few years ago
My son broke that laptop
As in broke the hardware
Hes 5 yo
you have a son lucky
Yeah he's great
He wants to be like me
Anytime I go to the bathroom, he rushes to get my tools and take stuff apart
Not just PC parts
He has most of my electronic components hid somewhere
I need to find them
Relays and capacitors
Etc
he even stole one of my multimeters
I have no idea where he is hiding my stuff
most I got out of him is a 9v battery pig tail
everytime I go out of the room he is taking my electronics
I got a few arduinos and esp32s but not enough parts to build stuff anymore
one time he had access to a playstation and I wouldn't give him my psn password
next think I know, he has a browser up on the playstation about cracking password hashes
he's only 5 years old
I know he can't crack it but the fact that he was trying is impressive
part uuid of which thing exactly @sturdy parrot
if we're remaking the file at the bottom wahts the point of all the top steps
i really respect your guide btw
PARTUUID of your root partition, it's easy to append it to the file first and build the file around it than getting it and writing it down, then building the file
I'll edit that line to elaborate in the wiki, thx for taking the time to read it and for the feedback
phallguy received a thank you cookie!
@hexed isle pushed the edit
thanks man
yenaras received a thank you cookie!
anytime
mount /dev/nvme0n1p1 /mnt # mount the root subvolume (meaning without a subvol= parameter)
cd /mnt
btrfs subvolume create @
btrfs subvolume create @home
mount /dev/nvme0n1p1 /mnt -o subvol=@
mount /dev/nvme0n1p1 /mnt/home -o subvol=@home
mkdir /mnt/boot
mount /dev/nvme0n1p1 /mnt/boot
@sturdy parrot do i need to be in the root file system for this to work? do i need a package for touch to work? it says it cannot touch the arch.conf file since it doesnt exist (im in my bootable media usb)
what is the partition hash
Did you pacstrap yet or is this all you have done?
i put that in to remount everything
cause everytime i reboot i have to do that
no i already did everything up until thsi point in your guide and 90% of my arch system is installed
this is the last step
i just dont know what the hash is or how to obtain that
touch should be a base command, what all did you pacstrap
bootctl install should make the directories in your boot
linux linux-firmware base nano man-db man-pages texinfo
You want the root partition, if you're chrooted in you can just do findmnt -fn -o / > /boot/loader/entries/arch.conf because / I believe will have the same PARTUUID of /dev/nvme0n1pX but I noticed you are mounting the same partition for both here
Basically you want the PARTIUID of your root partition
no i already mounted everything including the root
i did
this is the part i havent done
That's the number you get with yhe command
I'll show you mine
can you show me lsblk -f
OHHHHH
i see
i replaced the text that said PARTUUID with the uuid itself
yes
the hash is supposed to be replaced with partuuid ohhhh....
and make sure you have a space and rw after
what is this stuff do i need it
no you don't need it
it's just some kernel parameters I set
you can look into them in the wiki if you like
sysrq=1 is good to have, it allows you to reboot safely with a special key sequence if you get in trouble
<alt>+<sysrq>+REISUB (reboot even if system utterly broken)
how do you keep partitions mounted after rebooting
don't reboot now
i know
once it's installed, your fstab will handle that
oh right i havent done fstab yet
/etc/fstab defines what mounts on boot
did you do genfstab -U /mnt > /mnt/etc/fstab before you chrooted?
anyway the fstab won't be loaded from the live usb, only on your hardware when you are done
ok ill do that
you have to exit chroot to run that cmd
i did
kk
thank you so much for your help btw
np
I can help more in like an hour when my son goes to bed if needed
are those tabs or spaces? can i just have a normal space between each key and value?
You can use tab or any number of space, I just like them lined up
these two packages return error: target not found
It's an old guide, I need to make a new one
I'm not even on Wayland anymore
And my son broke that laptop
I'm on xorg i3 on my desktop
I don't recommend you start with sway and Wayland anyway
pavucontrols should work though
But I would use pipewire over pulse audio
Maybe do KDE or Gnome or XFCE for your desktop, follow the arch wiki for this bit
Maybe tonight I'll write a guide for my current setup
Oh typo on my end for pavucontrol
And rhe other one should be xorg-xwayland, but I don't recommend Wayland unless you are really experienced with Linux and want to test it's readiness. It's still in it's infancy
Manual arch install
lsblk returns a different uuid than findmnt -fn -o PARTUUID /dev/<root-partition>
yeah but use the one from findmnt
lsblk -f shows UUID which is different than PARTUUID
check blkid | grep /dev/<root-partition>
you can see both that way too
you could specify with the UUID but PARTUUID is less likely to change
i did... it said waiting 10 seconds for device
mounting on real root
cant find
failed to mount
now being dropped into emergency shell
when you used UUID?
or PARTUUID
because you need to make the key the name of what you use
UUID or PARTUUID
also check your fstab
if there are double entries on your fstab, you will get errors like that
ohhhhhhhhhhhhhhhhhh
well because im using btrfs i was thinking uuid would be better
ok i used the uuid
i just changed the key to UUID
error: root device mounted successfully, but /sbin/init does not exist
@sturdy parrot
chroot in from live usb and run mkinitcpio -P
understood sir
i thought i didnt need to do that because the wiki said it was already ran upon installing the packages
but ill do it now
sometimes it's necessary to do it again
not sure what happened in your case
I have to run it every time I update the kernel and nvidia drivers, using a pacman hook
I guess I don't manually run it, the nvidia.hook does it for me lol
good thing to do on a fresh install while chrooted in is to run pacman -Syyuu
or if you make it to live system, either or
how do i install nvidia drivers
do you have an nvidia gpu?
yes
sudo pacman -S nvidia nvidia-utils
in that case you should also use the pacman hook
wth
add this to your arch.conf init=/lib/systemd/systemd
after your UUID and before rw
nvm that's an old answer on stackexchange
does it say this? ```
/dev/sda2: clean, 59309/14622720 files
ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own. Good luck.
sh: can't access tty: job control turned off
[rootfs ]#
YES
/sbin/init is a link to /lib/systemd/systemd
even if you link that, I think something else will be broken
did you pacstrap base?
i did
maybe just pacstrap it again
WIAT
and base-devel
DO I NEED TO PUT MY MOUNT POINT IS A PARAMETER TO PACSTRAP
yes
well
you need to put /mnt
pacstrap /mnt base base-devel linux linux-firmware just try that again
it shouldn't hurt anything
with everything mounted of course
To be fair you aren't that far in tbh, restarting and taking notes is what I did starting out years ago
And why do you want btrfs
Even though that's not your issue, I'm just curious
Is it a RAID volume?
so i can extend my disk to another one
gotcha
oh i see
root device mounted successfully, but /lib/systemd/systemd does not exist
everything works fine its just this one init file or whatever
"This usually happens because you're mounting the wrong partition as "root" in the kernel command line." https://bbs.archlinux.org/viewtopic.php?id=219102
actually go ahead and mount how you normally do and then show me lsblk
from archiso
ping me when cuz I'm working on an app
alright
what really helped me when starting with arch linux and learning linux in general, I had arch already set up on my desktop but you can have anything and do this. I was installing it to my laptop and would ssh to the laptop for set up. I messed up a lot of things. So I would write github markdown files documenting the process. Thus the guide I shared you. I feel like documenting your process is an important thing that we overlook and skip a lot in tech but it helps so much. I should document more now, but I'm telling you it helps a lot if you document stuff yourself while you are doing it
this is kind of a makeshift documenting place
yeah but it can get lost quick later
you should document stuff on your own somehow
even write stuff down on paper at first
I found md files are great for documenting stuff
especially atm I'm building an industrial maintenance work order system, and I plan to build a wiki for certain tasks
say no more
@sturdy parrot ok master chief heres the lsblk -fa
the reason im using uuid instead of partuuid is because i thought there may be a compatibility problem with the btrfs file system and i dont think the uuid would change for that anyway
/boot/loader/entries/arch.conf
You mounted /mnt and /mnt/home on the same partition. Did you want a separate home partition? If not then you just mount /mnt and not /mnt/home
And if you want home on a separate partition, you'll have to make a new partition
Maybe it's a btrfs subvolume thing?
it is
.
look man i just need to figure out whats up with this sbin init shit
if i could find that everything would be smooth sailing
/sbin/init not found...
it's something to do with your mount point for root when you pacstrapped the system.
you didn't cd back out of /mnt before mounting your subvolumes to /mnt again
oh actually try adding rootflags=subvol=@ to your options in /boot/loader/entries/arch.conf
seems some extra steps are needed for btrfs setup
your default subvolume needs to be @ and not @home
@hexed isle did you get it sorted out?
im turning it on and trying it
very sorry about all of this i wouldve been done 3 days ago if it wasnt for this wack config
all good, btrfs seems like an extra learning curve lol
and then what do i set my init to again
wow thats a really informative link
you found