I’ve had trouble following Fox_exe’s instructions (his AutoInstall, or moving shares to /Public and then imaging from there via SSH), so now I’m trying to do it all manually (hooking it up to a tower PC), by creating partitions, and then dd imaging everything to those partitions.
My hard drive does not have MyCloud OS now (although I can get it back, if I need to). I’m now using SystemRescueCD, and I have GParted and the terminal up.
I am under the impression that OMV on MyCloud uses 8 total partitions, with 2 raid partitions, and the storage formatted in ext4.
Will those who have have OMV installed on their MyCloud take a screenshot of their partition table in GParted, so that I can compare and copy your partition settings?
And if someone else has posted a screenshot of theirs, but yours looks different, would you please still post yours, so that I can take note of any differences?
And finally, if you already know for sure which partition gets “kernel.img” and which partition gets “rootfs.img” written to them, would you please state that here?
Partition’s size - any. Important only partition numbers - 7 for bootconfig, 5 - for kernel. 1,2 - rootfs (md raid).
But possible to change layout in boot config and make your own layout and sizes. But this way only for people, who known what they do.
For all others - just use default partition layout (Look inside “Unbrick” instructions).
I’ve written those images as you said, but it’s not quite working yet. Here’s a little extra information.
The only partitions that are formatted are:
sda1 = linux-raid
sda2 = linux-raid
sda4 = ext4
The other partitions are unformatted. Should any of them be formatted a certain way?
The only partitions that have “Flags” are:
sda1 = raid
sda2 = raid
I’ve noticed (on other working Linux partitions), that there are often “bios_grub”, “boot”, or “msftdata” flags. Should any of the other partitions have any of these other flags?
There is 15.00 MiB of unallocated space before all of the partitions. Is this okay?
Alright, so I fixed the md127 problem by just booting up from my normal harddrive and then plugging the WD drive into the 2nd SATA connection. Then did DD rootfs.img again to both sda1 & sda2, and “md” did not show up.
However, even after DD rootfs.img -> sda1 & sda2, and DD kernel.img to sda5, and DD config.img to sda7 …
then put back together the WD drive as it should be …
Now it won’t appear on the network, and since it won’t appear on the network, I can’t access it via 192.168.2.11, or SSH into it, since it won’t appear show, and it’s still got the solid white light.
This is what my partitions look like now (md127 is gone and the key icons are gone… that’s good):
from your link, plugged it back in, and it’s turned green!
An “android” device has showed up on my DHCP Client list (under 192.168.2.1), and it points to 192.168.2.7, but using that address doesn’t load any screen, and SSH still refuses connection. I’m getting anxious, but I’m afraid to do anything.
Should I still use that:
dd if=boot-md0.env of=/dev/sda7
mentioned in your instructions? Or would that mess it up? Or should I do something else?
[Edit: And… it ended up doing the same thing as before… adding the key icon, and setting the mount point to /dev/md126 …]
@Fox_exe : I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you. I love you.
If I get this job at the machinist union that I’m applying for (which looks extremely likely), I’m clicking on that “Donate” button, on your website, as soon as I can (most likely in a couple months). I put up a Post-It note on my wall, to serve as a reminder.