Hi guys. I got it fixed with an original u-boot file, I found across the net. For all of you who came here via google: I have attached it to this message. Thx. sLOID.by sLOID - uBoot
Hi guys. I have a bricked WD MyCloud Ex2 (not the Ultra Version) - but I thought it was. So i dropped a u-boot image for the ultra via "bubt" on the box, wich is now dead. It still response to kwboot so i'm pretty sure I can fix it via UART. Unfortunately I can't find a proper u-boot binary to download to boot over kwboot for this box. I would appreciate if someone cby sLOID - uBoot
hi guys, thank you very much for this thread and your hard work. here is my situation: i have 2 of these boxes. both of them were from ebay and i solder the uart pins. one is running fine with the instructions from osa / bodhi, i got bodhi's debian running very well on it. root@debian:~# uname -a Linux debian 5.2.9-mvebu-tld-1 #1 SMP PREEMPT Mon Aug 19 12:47:39 PDT 2019 armv7l GNU/by sLOID - Debian
hi bodhi and even sparks, thank you guys so much. what could i say ??? the solution over the fixed scripts work well. the damn lacie has the right time now. will have some drinks later :-) @bodhi - pls, could you explain or have a short tutorial on how to get your newer u-boot version to the spi flash of the lacie ?? would love to have some more options on booting with your version. tby sLOID - Debian
hi bodhi, unfortunately there isn't any battery. i suppose the file /etc/adjtime is the reason for all that. while startup there is a line printed out with something like "adjusting time ..." here is the content of the file: Quote0.000000 1542148664 0.000000 1542148664 UTC i played around with these file ... but nothing happens. even deleting does nothing, cause the systeby sLOID - Debian
hi bodhi, sry for the late response. i didn't had any time for this project. and i think you were totally right. it doesn't matter what version of uboot the lacie uses, the clock is still out of range. in the last weeks it has no power. so the rtc should be clear. but it now says: Do 13. Mai 12:28:50 CEST 2032 it's so frustrating. hope you have just another few things to tby sLOID - Debian
YEEEEEEEAH !!!!! hi bodhi ... all worked well (i replaced the timeserver in your commandline with a german one and set it to my routers ip) everything went well and the damn lacie has the right time now. thank you so much for your hard work. :-)))))) would love to write the u-boot file to the flash of the nas. can you tell me how ??? thank you. sLOID.by sLOID - Debian
hi bodhi, here it is: Sending boot message. Please reboot the target...| Sending boot image... 0 % [......................................................................] 3 % [......................................................................] 6 % [......................................................................] 9 % [.................................................by sLOID - Debian
hi bodhi, sry for my late response, but unlikely: i had to do other things at the weekend, I'm sorry for the delay. the lacie boots up fine with your u-boot image via uart. unfortunately the rtc problem is pending. can you please tell me, what i have to do, to flash your image to nand ?? i know i have to erase the address block before. but how do i find out, what the right address itby sLOID - Debian
hi bodhi. thank you very much for your work. i'll instantly try this out this evening, when i return back home. best regards, sLOID.by sLOID - Debian
hi bodhi, ok ok ... got it. i won't do any flashing :-) i'll report later that weekend. greetz.by sLOID - Debian
hi bodhi, i tried your workaround but without success. i'll give your actual u-boot a try and when i return home i'll do the flashing. hope this will work then. thank you for your work. i'll let you know. greetz, sLOID.by sLOID - Debian
hi bodhi, here is the dmesg: - klick - and the logread: - klick - and yes, it's yours rootfs 3.18.5 thank you.by sLOID - Debian
hi bodhi, learning will never end. thank you for that :-) had to install the busybox-syslog pakage. here's the result: first the ntpdate command with the unlikely known error: ntpdate ptbtime1.ptb.de 3 Sep 19:48:00 ntpdate[28423]: Can't adjust the time of day: Invalid argument and here the output from logread right after ntpdby sLOID - Debian
hi bodhi, don't know exactly what you mean. isn't the dmesg output the kernel log ??? in the /var/log folder is the following: apt dmesg dmesg.2.gz dpkg.log messages wtmp boot dmesg.0 dmesg.3.gz fsck ntpstats alternatives.log btmp dmesg.1.gz dmesg.4.gz lastlog syslog let me know where to look. and dmesg doesnt show anything up after the ntpdate command.by sLOID - Debian
hi bodhi, it's the "LaCie Networkspace 2 lite". I include the specified name of the dtb-file in the DTS folder while building the image. (kirkwood-ns2lite.dtb). Everything went without errors, so it should be the right one. sLOIDby sLOID - Debian
ah i see. thank you for explaining. yes i have serial access. unfortunately not at the moment. the lacie is at home. but i have to work next few days. what i have is ssh access. so here are the outputs: cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000 cat /proc/mtd dev: siby sLOID - Debian
hi bodhi, yeah, i did. while playing around i found other frightened stuff: commands like: fw_setenv bootdelay=5 end up with: Warning: Bad CRC, using default environment MTD erase error on /dev/mtd0: Invalid argument i think it is a bigger problem and not only with the rtc. do you have another hint for me ?? thank you. sLOID.by sLOID - Debian
hi bodhi, yes, it does: rtc-mv f1010300.rtc: setting system clock to 2018-08-30 21:39:56 UTC (1535665196) what does it mean ??by sLOID - Debian
hi there, i'm a big fan of this forum and got a few devices allready running successfully bodhi's great debian stuff - thank you for all your work :-) my latest project is a broken (hdd - crashed) lacie networkspace 2 lite devices. i flashed the mainline u-boot (from lacie-side) and got it running with a new drive and bodhi's latest rootfs and kernel 4.4.0 my only problemby sLOID - Debian