- Reseting the configuration and booting .rootFS -> won't boot
- Reseting the configuration and booting root.bin -> won't boot
I really don't know why, specially the root.bin option.
Anyway, earlier today I got a new 4GB pendrive just for the WDTV, and a small cheap USB hub. The good news is:
- Booting .rootFS from the pendrive -> check!
- Booting .rootFS from the pendrive connected to the USB hub and sharing the port USB2 with the wifi dongle -> check!
I'd love to know what's wrong with the boot.bin method in the 1TB disk, but well... who knows...
Now, there's something that I'd like to check with you: as I didn't know if the pendrive was going to be recognized as sda or sdb, y set ROOT_UUID with it's uuid. The boot went fine, in the end the pendrive ended up being sdb (which is kind of logic, as it is attached to the port USB2, maybe I should exchange ports between the hub and the disk just to be safe). I suppose that the WDTV boot from there because I forced the ROOT_UUID. The thing is: the WDLXTV Config page at the WEC has this warning in yellow in the header:
- Code: Select all
Invalid ROOT_UUID value: 'ea5266e1-61fe-4f4d-816a-2d71d550740d', changed to ''. Please verify and save.
Why? That UUID is the one I get with blkid. Why is it invalid? Why is it being cleared? Is it being really cleared? If I grep /tmp/conf/config, ROOT_UUID has the correct value (is not empty). I tried a couple of times writing it again with config_tool, and saving the configuration, but when I refresh the WEC it keeps showing the warning.