![]() ![]() The size of such parts may range from 2 KB to 2 MB, so each file is stored on several hard disks at the same time. Then these parts are written consecutively to all hard disks within such array. However, when data is written to a RAID system, a file is divided into several parts. It's certainly not related to the boot problem.Download Why can’t ordinary software tools restore files from RAID?Ĭonventional hard disks keep user’s data by writing it to their surface in a consecutive way, and this is how an entire file is stored on a single hard disk. If you don't have that, you can probably do it via fw_setenv in the uboot-envtools package, but I can't help with that since I've actually never done that myself.Įvery thing went smooth for more or less 200GB after that MBLD hangs up. Setenv requires serial access to the uboot console. Or, if you want it to be as short as possible, without a fallback to booting OpenWrt from a single drive in Drive A: setenv bootcmd 'sata init ext2load sata 0:1 100000 /boot/boot.scr source 100000' Setenv boot_owrt_11 'echo - searching boot.scr on 1:1 ext2load sata 1:1 100000 /boot/boot.scr' Setenv boot_owrt_01 'echo - searching boot.scr on 0:1 ext2load sata 0:1 100000 /boot/boot.scr' I actually once wrote a much, much simpler boot script than the one MBL uses: setenv boot_owrt 'echo - SATA init sata init if run boot_owrt_01 then echo - found boot.scr on 0:1 source 100000 elif run boot_owrt_11 then echo - found boot.scr on 1:1 source 100000 else echo - boot.scr not found on any disk! fi' ![]() You can leave OpenWrt on that disk unconfigured, it will never actually boot, the MBL will just take the boot.scr file and continue booting from the disk in drive B. I would argue this is a very sensible option anyway, OpenWrt does not take up that much space and you afterwards have the option of booting off that disk without reformatting it first. I guess WD never expected anyone to shove anything but a completely uninitialized or a properly MBL-initialized disk in there.Īnyway, at this point there's two solutions to your problem:Ī) put OpenWrt on the second disk, too. Which makes it a rather shitty fallback mechanism. the ext2loadattempt in the first line apparantly doesn't error or time out, it just sits there confused. What I'm a bit surprised now is that if the partition exists, just not the file, or if the partition is anything but ext2. Lbf4=sata init ext2load sata 0:2 100000 /boot/boot.scr Lbf3=sata init ext2load sata 1:2 100000 /boot/boot.scr Lbf2=sata init ext2load sata 0:1 100000 /boot/boot.scr Lbf1=sata init ext2load sata 1:1 100000 /boot/boot.scr ![]() Load_boot_ap2nc=echo - Checking Boot Partitions - if run lbf1 then echo 1:1 elif run lbf2 then echo 0:1 elif run lbf3 then echo 1:2 elif run lbf4 then echo 0:2 fi Although I'm actually surprised that neither I nor anyone else in the last years ran into this obvious problem, even by accident.īoot_sata_script_ap2nc=run load_boot_ap2nc source 100000 WD and their insistence to have the two drive numbered backwards, down to the boot parameters. uboot is trying to load /boot/boot.scr from sdb1 which obviously will not be there on a blank disk. I'm a bit old fashion and I skip all these fancy bouncy features like home media hub or private cloud (which in my opinion are very dangerous eg.: WD and vulnerability CVE-2021-35941) and I'm setting up this like local file server for encrypted backups so I need this disk daily for short time. There is nothing wrong in use ordinary disks at home or small office. I wouldn't rely on them for anything critical or non-redundant of course, especially given their age, but in the same vein any disk can fail and I similarly wouldn't trust a single NAS-grade disk with irreplaceble data. Their rationale might have been that this kind of "home NAS" powers down the drives between infrequent periods of use and doesn't actually need or even necessarily benefit from NAS-grade drives rated for 24/7 constant operation.Īnd they were not entirely wrong: In 10+ years of use - half a decade with the original firmware, the other half with OpenWrt - I haven't had a single WD Green in any of my multiple MBLs fail on me. Neither were WD Greens, WD still used them in the single-drive MBLs from factory. It didn't help, but at Tuesday I will have another drive so I will test it again. To confirm or disprove try a current snapshot, the fix will be in the next (minor) release versions. This may be caused by a bug that has very recently been found and fixed (tl dr: the upstream SATA driver had problems with certain drive firmwares, it became apparant with some SSDs). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |