Installation: root fs with btrfs fails.
From
Arne Ploese@21:1/5 to
All on Thu Apr 18 12:40:01 2024
Hi,
installing debian daily image (trixie) and formating the root
filesystem with btrfs fails on the first startup.
The Installer creates a subvolume named "@rootfs" and writes a correct
fstab under @rootfs/etc/fstab.
But the u-boot bootprocess has not this information and mounts the root
devece as is and not the subvolume.
Here my workaround:
Copy all dirs inside @rootfs the "expected" root and "fix" the fstab.
install u-boot-menu and fixed the /etc/default/u-boot with : U_BOOT_PARAMETERS="rootflags=subvol=@rootfs ro"
copy all files back under @rootfs and revert the fstab to the
original.
If this is a bug, against which package or installer in general should
I file a bug?
Arne
<html><head><style>pre,code,address {
margin: 0px;
}
h1,h2,h3,h4,h5,h6 {
margin-top: 0.2em;
margin-bottom: 0.2em;
}
ol,ul {
margin-top: 0em;
margin-bottom: 0em;
}
blockquote {
margin-top: 0em;
margin-bottom: 0em;
}
</style></head><body><div>Hi,</div><div><br></div><div>installing debian daily image (trixie) and formating the root filesystem with btrfs fails on the first startup.</div><div>The Installer creates a subvolume named "@rootfs" and writes a correct fstab
under @rootfs/etc/fstab.</div><div style="font-size: 14.666667px;">But the u-boot bootprocess has not this information and mounts the root devece as is and not the subvolume.</div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family:
Cantarell; font-size: 14.666667px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -
webkit-tap-highlight-color: rgba(0, 0, 0, 0.4); -webkit-text-stroke-width: 0px; text-decoration: none;"><br></div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Cantarell; font-size: 14.666667px; font-style: normal; font-variant-
caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0.4); -webkit-text-stroke-width: 0px; text-decoration: none;">Here my
workaround:</div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Cantarell; font-size: 14.666667px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-transform: none;
white-space: normal; word-spacing: 0px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0.4); -webkit-text-stroke-width: 0px; text-decoration: none;"><br></div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Cantarell; font-size: 14.
666667px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-tap-highlight-color:
rgba(0, 0, 0, 0.4); -webkit-text-stroke-width: 0px; text-decoration: none;">Copy all dirs inside @rootfs the "expected" root and "fix" the fstab.</div><div>install u-boot-menu and fixed the /etc/default/u-boot with :</div><div>U_BOOT_PARAMETERS="<
a href="mailto:rootflags=subvol=@rootfs">rootflags=subvol=@rootfs</a> ro"</div><div>copy all files back under @rootfs and revert the fstab to the original.</div><div><br></div><div><br></div><div>If this is a bug, against which package or installer
in general should I file a bug?</div><div><br></div><div>Arne</div><div><span></span></div></body></html>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)