Hooverdan
(Dan W.)
17
This is actually an issue that was fixed with 5.0.11-0 & improved on in 5.0.15-0 [phillxnet edit]. Here’s a corresponding thread on the forum:
So, if you can get to the update screen via the menu:
you could update (testing channel) to the latest version. This will likely make this error go away.
From the thread I referenced above, maybe you can also run this command, and post the output:
lsblk -P -p -o NAME,MODEL,SERIAL,SIZE,TRAN,VENDOR,HCTL,TYPE,FSTYPE,LABEL,UUID
2 Likes
