1000001101000 / Debian_on_Buffalo

Tools for Installing/Running Debian on Buffalo ARM based Linkstation/Terastation/Kurobox/Cloudstor devices.
316 stars 40 forks source link

Latest Installer Images Not Working for TS2Pro on Bookworm and possibly Bullseye #196

Open williamcfarmwise opened 10 months ago

williamcfarmwise commented 10 months ago

Appears that checkin 22796ef1 has broken the installer image for TS2Pro (don't know about others, as I only have a TS-Live to test with, which is the same as a TS2Pro hardware-wise). I get System Error E04 Can't Load Krnl error when attempting to use the image to install. I reverted to checkin d91c81d to get the bookworm installer image to work. Latest Bullseye installer image also appears to have the same symptom, but I did not check which previous version worked, but I suspect the same.

1000001101000 commented 10 months ago

Looks like a silly mistake on my part.

I've:

There's not much reason to repeat your install if you ended up with a working system but you should copy the latest micro-evtd-armel from the repo into /usr/local/bin/micro-evtd on your device. Ironically, the update that broke these installer images was mainly targeted at making the boot process more reliable in ways that affect the ts2pro.

williamcfarmwise commented 10 months ago

Thanks for the update, the new initrd.buffalo has fixed the krnl error. I can now boot into the installer. Upon further testing I found that during the partitioning portion of the installer, get the following error: "Software RAID not available, The current kernel doesn't seem to support software RAID (MD) devices. This should be solved by loading the necessary modules." I didn't see that error in the previous working install, so assuming that this is another issue in the latest image. Please let me know if you can reproduce. Thanks again.

1000001101000 commented 10 months ago

I just gave it a try on mine and was able to create a RAID1 device without issue.

Can you provide more detail of the steps you are taking and the raid level/etc you are using? Also please post a screenshot of the error.