Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalI just spend the last couple hours working through the same error but with a single disk set up. Perhaps this will help.
Try running a LIVE USB/CD on the machine and mount sbc1the EPS partition. In there check out the loader/entries/arch.conf file. What I found is that I had a setting like root=PARTUUID=xxxxxxxx.... What I had to do was change it to root=/dev/mapper/<partition label>. This it worked as expected. Hope that helps.
I just spend the last couple hours working through the same error but with a single disk set up. Perhaps this will help.
Try running a LIVE USB/CD on the machine and mount sbc1. In there check out the loader/entries/arch.conf file. What I found is that I had a setting like root=PARTUUID=xxxxxxxx.... What I had to do was change it to root=/dev/mapper/<partition label>. This it worked as expected. Hope that helps.
I just spend the last couple hours working through the same error but with a single disk set up. Perhaps this will help.
Try running a LIVE USB/CD on the machine and mount the EPS partition. In there check out the loader/entries/arch.conf file. What I found is that I had a setting like root=PARTUUID=xxxxxxxx.... What I had to do was change it to root=/dev/mapper/<partition label>. This it worked as expected. Hope that helps.
I just spend the last couple hours working through the same error but with a single disk set up. Perhaps this will help.
Try running a LIVE USB/CD on the machine and mount sbc1. In there check out the loader/entries/arch.conf file. What I found is that I had a setting like root=PARTUUID=xxxxxxxx.... What I had to do was change it to root=/dev/mapper/<partition label>. This it worked as expected. Hope that helps.
