View previous topic :: View next topic |
Author |
Message |
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54214 Location: 56N 3W
|
Posted: Sun Mar 04, 2018 8:02 pm Post subject: |
|
|
Francky,
Lots of different block objects have UUIDs.
You can use a uuid in the mdadm --assemble command but you must use the UUID of the raid set.
Code: | mdadm -E /dev/sda11 | will show it.
He is an example from my /boot.
Code: | $ sudo mdadm -E /dev/sda1
Password:
/dev/sda1:
Magic : a92b4efc
Version : 0.90.00
UUID : 9392926d:64086e7a:86638283:4138a597
... |
It won't change anything as that step works.
Your debug shows the kernel trying all the filesystems it knows.
Going back to your blkid output we see
Code: | /dev/md8: UUID="751484c4-b9da-43a1-b100-e7cc61dbd8a2" UUID_SUB="4561ee17-ee4b-422c-a5f7-319e3b63e29c" TYPE="btrfs" |
That confirms that you have a BTRFS with a subvolume. Its the subvolume that must be mounted as root, not the top level BTRFS filesystem.
The UUIDs here are filesystem UUIDs
You need to mount the object with UUID 4561ee17-ee4b-422c-a5f7-319e3b63e29c as root. That appears to need additional parameters.
There may be some hints on the Arch forums but I've never used BTRFS.
You have the userspace mount command in your initrd
Try Code: | mount UUID=4561ee17-ee4b-422c-a5f7-319e3b63e29c /mnt/root || rescue_shell |
That's an educated guess. As I say, I've never used BTRFS.
Code: | mount -t btrfs UUID=4561ee17-ee4b-422c-a5f7-319e3b63e29c /mnt/root || rescue_shell | will be faster, as mount will only try btrfs. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
Francky n00b
Joined: 25 Feb 2018 Posts: 14 Location: France
|
Posted: Mon Mar 05, 2018 10:12 am Post subject: |
|
|
I have tried what you said:
Code: | mount -t btrfs UUID=4561ee17-ee4b-422c-a5f7-319e3b63e29c /mnt/root || rescue_shell |
but now I am dropped to the rescue shell because the mount command fails.
The error says:
Code: | mount: mounting UUID=4561ee17-ee4b-422c-a5f7-319e3b63e29c on /mnt/root failed: no such file or directory
Something went wrong. Dropping to a shell. |
Do you have another idea?
I will take a look at the arch forum but my hopes are small to make this *** boot by itself... |
|
Back to top |
|
|
redwood Guru
Joined: 27 Jan 2006 Posts: 306
|
Posted: Wed Mar 14, 2018 12:42 am Post subject: |
|
|
Did you ever get this solved?
Also, did you try either the UUID or just /dev/md11 instead of the UUID_SUB ?
What's your kernel's boot commandline (/etc/default/grub)
or linux line in /boot/grub/grub.cfg
something like
linux /kernel-genkernel-x86_64-3.17.0-gentoo root=UUID=[...] ro single rootflags=subvol=root dolvm vconsole.keymap=us splash vga=791 quiet
or maybe subvol=/
or maybe subvolid=5
What does "btrfs filesystem show /dev/md11" show?
Did you look either of these gentoo guides:
https://wiki.gentoo.org/wiki/Btrfs/System_Root_Guide
https://wiki.gentoo.org/wiki/Btrfs/Native_System_Root_Guide
or the arch guide:
https://wiki.archlinux.org/index.php/Btrfs#Mounting_subvolumes
Curious, why are you putting btrfs on top of mdadm raid1?
Why not just use btrfs to create raid1 from your partitions?
btrfs's raid1 is supposedly fairly stable and if btrfs handles the raid1 itself, then it can correct any errors if it should find any bitrot. On the other hand,
btrfs allows you to only boot once in degraded mode (after that you're locked out).
Also why all those partitions instead of just using btrfs subvolumes?
I guess if btrfs's quota is still buggy, then using physical partitions
instead of btrfs's namespaces would prevent eg.
an errant log file growing too large and running out of free space,
or if you need encryption so need btrfs on top of luks on top of mdadm raid.
Just curious as I'm considering re-installing two computer systems and am trying to decide on partition schemes and filesystems. I've been running sabayon on laptop with btrfs and full disk encryption without problems for a couple years now. My desktops are mdadm raid1 (2 hd @ 2TB each) + LVM + ext4. Adding a 3rd 2TB hard drive and was considering growing the mdadm raid1 to raid5 (4TB) or repartitioning and going with btrfs's raid1 (3TB) |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|