Hi @zeusjan i try to install the Deb10+OMV5 with the USB Images on my MCHD. It works until the system reboots after the successful installation in golden image boot. It reboots in recovery mode, using the usb boot.
[INFO]: bootState: BOOT_STATE_NO_OTA
[FATAL ERROR] CBR not found, boot USB rescue mode.
==== boot_rescue_from_usb =====
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
USB1: USB XHCI 1.10
scanning bus 1 for devices... Unknown request , typeReq = 0x200c
2 USB Device(s) found
USB2: USB XHCI 1.10
scanning bus 2 for devices... Unknown request , typeReq = 0x200c
1 USB Device(s) found
USB3: USB XHCI 1.10
scanning bus 3 for devices... Unknown request , typeReq = 0x200c
1 USB Device(s) found
scanning usb for storage devices... Enter is_pmbr_valid
Warning: failed to 0xEE type in MBR
1 Storage Device(s) found
Hello, you don´t have any need to touch the golden sections, you only need to modified the A or B sections (depending on where you gonna boot), but for the look of that log i believe that you mess more than the golden section, it looks like you delete or modified the FW Table, and that´s why your NAS is trying to boot from the usb, a normal boot with a functional FW table should look like this:
If you have a backup, i recommend you to load the backup and start from scratch, if you don´t have any, I can share a fw table with you, but i can´t guarantee is gonna work
It looks like you managed to fix the golden fw table, i believe that you had a checksum error because you change the kernel, dtb and rootfs on the beginning . What method do you use to change the kernel, rootfs and dtb file when you installed Debian? you used fwtutil from forth32 or other method???. you need to write again the kernel, rootfs and dtb file with a utility that modified the checksum on the fwtable (like fwtutil from forth32 install image). And you need to check and double check that you are going to write every thing in their corresponding place (the kernel on the golden kernel, etc.). the best practice now that you recovered the golden fwtable, is copy that table over another partition (1 or 2) and try to boot from there to no mess anymore with with the golden boot, so you can recover if you had any problem.
Short background story about the situation. My MCHD partitions brick them self, maybe while a broken update. Now it try to bring this system back to life … with debian and omv.
When i boot from usb and startup fwutils from forth32 is shows:
@RAH-66 or @Alex-N do you guys have a link for upgrading the kernel to 4.9? I am running 4.1 kernel and I don’t see where to get the archive that contains the 4.9 kernel
I want to give this a go on my mycloud. Back at the beginning of this thread western1 said “Edit 28.04.2020 : others people confirm that you won’t loose your data” but later I saw where it looked like data was wiped during installation of debian. Has anyone done the install recently and do you lose your existing data?
I didn’t, but I also backed it up. If you don’t have local storage I’d recommend paying a few dollars to throw it on a cloud service for a couple of hours while you do the upgrade.
Am I correct in assuming this install will remove the odd restsdk indexing and storage management software from the data areas of the MCH leaving a standard filesystem store in their place ?
I know this is an odd followup question, but does anybody know what project the storage system used in the original firmware is based on and what features it provides beyond a cloud API ?? (is it WD blb?)
It seems an odd engineering choice if it doesn’t provide zoned storage or some useful feature… It certainly makes a lot of things impossible and has many drawbacks… I just don’t get what would have motivated the design choice, the device is deliberately hobbled by some very questionable quirky choices.
A cloud auth system with no local fallback capability (unusable without internet access)
A cloud store system that slows access on local networks in exchange for ?? (nothing ?)
A cloud store that appears to have incomplete file semantics (or giant bugs)
A cloud store system that is not multi tasking (or has giant bugs)
Hardware with a lot of promise, but most of it completely and deliberately blocked off from its owner.
Forced and uncontrollable updating.
The resounding question I have for this is why ? Such potential here and they deliberately busted it.
q
