I've acquired a KD20 from EBay (no disks) and want to install OpenWrt on it. This is what I did:
Installed two disks with 1TB each
Switched on, the KD20 started the setup procedure and ran up to step 5 (drive configuration) and I chose 'striped' (don't ask me why). After a while. the formatting process stopped with an error message, some disk problem, can't remember the message. I know the disks are OK because they worked perfectly in another system, which I abandoned and sold.
Started the setup process again and the it immediately opens the wizard window with step 5 as shown in the attached screenshot: it shows a progress bar, but there's no progress at all and none of the areas to select nor the Create button (Erstellen, I selected German in the setup) is active.
I tried both disks as single disk, in both slots: the Step 5 screen reflects the change, e.g. with one disk inserted, there is only one possible selection, but the progress bar is still there and that's it.
I understand that I need a working setup to upload the OpenWrt firmware, so now I'm lost.
I know about the possibility to get to the serial port and try the serial condole, but I'd rather like to avoid this.
Maybe someone has seen this before. I'd appreciate any help.
It's the step where you have to choose which type of RAID mode you wish to set up as shown in the picture.
Schritt 5: Erstellen eines RAID-Laufwerks = Step5: Create a RAID drive
Sorry. I didn't follow your link.
in the section 'Installation Process' I read
Once you have successfully flashed the intermediate firmware, you can now access it using ssh (assuming KD20 is directly connected to eth0 on your host)
Unfortunately I'm not yet in this process. I cannot flash the OpenWrt firmware as long as the basic setup of the KD20 with the stock firmware has not succeeded and that's where I get stuck.
Thanks, Hans
Thanks for the tips and the links. I'll try with another disk eventually but I'm not very confident because it's all the same without any disk. I've sent an email to shuttle support but honestly I don't expect any answer,
If nothing helps I'll bite the bullet and try with the serial console.
BTW, https://openwrt.org/toh/hwdata/shuttle/shuttle_omninas_kd20 provides a link where the last stock firmware is still available.
And it's really queer that there's no way to use the hardware reset button to perform a factory reset.
The initial problem is solved.
Using the WayBack machine I found and downloaded the file KD20.zip, unpacked it to a USB stick and - voila - my KD20 is up and running again. The detailed steps were:
Format a USB stick with VFAT (mkfs.vfat ...)
Unpack KD20.zip and copy all files to the stick (don't copy the zip file, this won't work)
Install disks in the KD20. Insert the USB stick and start the KD20, Be patient, you will see activity on the stick, At some time the ON/OFF LED will turn red. When this LED turnes blue again and stops blinking you're done and can access the web interface to go through the setup process.
Now I*ll try to install OpenWrt. I'm a little bit puzzled because there are different descriptions of the install process and broken links. My question now are:
Which is the latest OpenWrt firmware for the KD20?
Where do I get it (I read about an intermediate firmware, because the target firmware is too big to be directly uploaded from the KD20 stock firmware?
If something goes wrong with this installation, will the recovery procedure in KD20.zip still work? For the worst case and before I found out about KD20.zip, I soldered a cable to the KD20s uart pins.
A short answer and maybe a working link would be very helpful.
I do not understand 'removing sata disks for ins%all'. Could you elaborate a bit more on it? Some USB stick solution would be very welcome because this is what happened:
I successfully created the file lede-oxnas-kd20-factory.tar.gz and did a firmware update
The KD20 started with no problem and I could ssh into it (new MAC, new ID).
Then I made a mistake because i thought I'm clever and looked for the latest OpenWrt firmware release available for the KD20, which is 23.05.4 and replaced the files to upload in the next steps with the newer ones.
No problem at all with the steps ’re-format UBI' and 'write kernel' only I did it with the newer version 23.9.4 which was probably a BIG MISTAKE.
After this, the KD20 boots but the ON/OFF Led turns red and that's it.
I can ping the KD20 but all ports are closed, no web, no ssh, and the serial console doesn't work either...
Looks like I've finally bricked my KD20 and I don't know if it can be recovered and how.
I tried USB recovery with the files from KD20.zip - no activity on the stick.
There's no response from serial either. Maybe I've made a mistake with the cable/connector or I damaged a strip line on the board because the through connections were very oxidized and i had to scratch a lot to get it soldered.
My last hope would be either booting from USB or from SATA, if this is possible at all.
Maybe the files from the KD20.zip could be adapted to what I installed. I made notes of all steps that led to the problem if that helps (also see my last post)
If something goes wrong with this installation, will the recovery procedure in KD20.zip still work? Answer: If you messed up U-Boot the answer is NO.
For the worst case and before I found out about KD20.zip, I soldered a cable to the KD20s uart pins. Remark: Take care, do not use a default RS232-USB adapter. This can fry your Uart. You need a TTL 3.3V adapter . I never found out how this adapter has to be connected: in my understanding a 3.3V source is needed but this is not mentioned anywhere. It would be great if some guru could describe this in detail and add it to the WIki.
:
You can probaby find an updated u-boot over att Doozan's, but I'm only guessing.
Newer u-boots often have netcat built in, removing the need of USB TTL interfacing.
Don't know if it helps, at the moment, but an oxnas box is almost unbrickable, provided you have the right tools/skills. An oxnas SoC tries to boot from sata, before looking at flash. So a well prepared sata disk will boot the box.
You can try if the files here can prepare a bootable disk for you.
