MyBookLive keep restarting

First, I’m pretty sure the power adapter is fine.

My MyBookLive keep restarting Since I manually restored the firmware ( http://download.wdc.com/nas/apnc-024310-048-20150507.deb ).

The update.log shows that the upgrade failed:

updateFirmwareFromFile.sh:12/07/21 15:22:59:upgrade start: /CacheVolume/apnc-024310-048-20150507.deb
updateFirmwareFromFile.sh:12/07/21 15:22:59:check_size=
updateFirmwareFromFile.sh:12/07/21 15:22:59:version_current=024310048
updateFirmwareFromFile.sh:12/07/21 15:22:59:version_newfile=024310048
updateFirmwareFromFile.sh:12/07/21 15:22:59:package_newfile=apnc
updateFirmwareFromFile.sh:12/07/21 15:22:59:master_package_name=apnc
updateFirmwareFromFile.sh:12/07/21 15:22:59:master_package_new=apnc
updateFirmwareFromFile.sh:12/07/21 15:22:59:update_container=
(Reading database ... 
dpkg: warning: files list file for package `ramlog' missing, assuming package has no files currently installed.

dpkg: warning: files list file for package `libparted0’ missing, assuming package has no files currently installed.
18711 files and directories currently installed.)
Preparing to replace apnc 02.43.10-048 (using …/apnc-024310-048-20150507.deb) …
preinst: currentRootDevice=/dev/md0
preinst: master_package_name=apnc
preinst: update_container=
Restore raid device: /dev/sda1
Restore raid device: /dev/sda2
Prepare for upgrade install to /dev/sda1 …
Stopping periodic command scheduler: crond.
Stopping itunes device: forked-daapd.
Kill Miocrawler Process…
Tue Dec 7 07:23:11 PST 2021 - %I - Communication Manager - Stop
Prepare for upgrade pkg install…
mdadm: /dev/sda1 appears to contain an ext2fs file system
size=1999808K mtime=Wed Dec 31 16:00:01 1969
mdadm: size set to 1999808K
mdadm: creation continuing despite oddities due to --run
mdadm: array /dev/md1 started.
preinst: current device=/dev/md0
preinst: upgrade device=/dev/md1
Unpacking…
Unpacking replacement apnc …
Setting up apnc (02.43.10-048) …
postinst: upgradeDevice=/dev/md1
postinst: currentRootDevice=/dev/md0
postinst: upgradePath=/mnt/rootfs
Copy image to upgrade device /dev/md1:
blockSize=64k blockCount=31247
Compare checksum
-: FAILED
md5sum: WARNING: 1 of 1 computed checksum did NOT match
ok 1
Upgrade failed
mdadm: stopped /dev/md1
mdadm: added /dev/sda1

Since then, I’ve only been able to access the device for about 3 minutes at a time.

Seems the device keeps repeating the following process:

Power on -> Light[blue] -> Light[yellow] -> Light[green] -> Light[off/blue]
                ^                                                 |
                |                                                 |
                +-----------------------<-------------------------+

The device can be accessed only in green light state, but for 3 minutes there is almost nothing can be done, not even trying to restore the firmware again.

I’ve write a script to monitor the device:

device=<IP>
while true
do
    printf "[%s] %s" $(date +%H:%M:%S) "Waiting for device to be online"
    while ! /sbin/ping -q -c 1 $device &> /dev/null
    do
        printf "."
    done

    printf "\n[%s] %s\n" $(date +%H:%M:%S) "Device is online"

    printf "[%s] %s" $(date +%H:%M:%S) "Waiting for device to be offline"
    while /sbin/ping -q -c 1 $device &> /dev/null
    do
        sleep 10
        printf "_"
    done

    printf "\n[%s] %s\n" $(date +%H:%M:%S) "Device is offline"
done

Output:

⋊> [~/D/mybooklive] sh ~/.scripts/watch-mybooklive.sh
[10:08:17] Waiting for device to be online.........................................................................................................................
[10:30:30] Device is online
[10:30:30] Waiting for device to be offline________________________
[10:34:42] Device is offline
[10:34:42] Waiting for device to be online............................
[10:39:50] Device is online
[10:39:50] Waiting for device to be offline____________________________
[10:44:42] Device is offline
[10:44:42] Waiting for device to be online.............................................................................................
[11:01:46] Device is online
[11:01:46] Waiting for device to be offline_______________________
[11:05:48] Device is offline
[11:05:48] Waiting for device to be online..............................
[11:11:19] Device is online
[11:11:19] Waiting for device to be offline_______________________
[11:15:20] Device is offline
[11:15:20] Waiting for device to be online.............................
[11:20:40] Device is online
[11:20:40] Waiting for device to be offline________________________
[11:24:51] Device is offline
[11:24:52] Waiting for device to be online...........................
[11:29:49] Device is online
[11:29:49] Waiting for device to be offline________________________
[11:34:01] Device is offline
[11:34:01] Waiting for device to be online...................................................................................................
[11:52:11] Device is online
[11:52:12] Waiting for device to be offline_______________________
[11:56:13] Device is offline
[11:56:13] Waiting for device to be online...........................
[12:01:11] Device is online
[12:01:11] Waiting for device to be offline_______________________
[12:05:12] Device is offline
[12:05:12] Waiting for device to be online.....................................................................................................
[12:23:45] Device is online
[12:23:45] Waiting for device to be offline_______________________
[12:27:46] Device is offline
[12:27:47] Waiting for device to be online...........................
[12:32:44] Device is online
[12:32:44] Waiting for device to be offline________________________
[12:36:56] Device is offline
[12:36:56] Waiting for device to be online..........

Hi @BGVevS,

Have you opened a Support Case? If not opened, for more information, please contact the WD Technical Support team for the best assistance and troubleshooting:
https://support-en.wd.com/app/ask

Finally made progress.

Since it has not been able to reflash the firmwar, I finally want to investigate why the disk cannot be removed:

MyBookLive:~# /usr/local/sbin/resetButtonAction.sh

currentRootDevice = /dev/md0
upgradeRootDevice = /dev/md1

Ensure both partitions are members of the original MD device
mdadm: hot remove failed for /dev/sda1: Device or resource busy
mdadm: Cannot open /dev/sda1: Device or resource busy

Then I found that the “recovery” progress went very fast:

MyBookLive:~# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md0 : active raid1 sda2[1] sda1[2]
      1999808 blocks [2/1] [_U]
      [======>..............]  recovery = 34.8% (696320/1999808) finish=1.7min speed=12403K/sec

unused devices: <none>

But as soon as the number approaches 74% the device restarts. The process takes about 3~5 minutes. After the device restart, it starts recovering again from the beginning.

I’ve tried pausing recovering, but it doesn’t work. The device still reboots after about 3 minutes:

MyBookLive:~# echo idle > /sys/block/md0/md/sync_action

Then I tried the following commands:

MyBookLive:~# /usr/share/mdadm/checkarray -x --all;
echo 0 > /proc/sys/dev/raid/speed_limit_max;
echo frozen > /sys/block/md0/md/sync_action

Still not preventing recorvering, but it slowed down to 1/10th of what it used to be. Although the device still restarted in the end, its online time was greatly extended.

After restarting and looking at the progress of recovery, it stopped:

MyBookLive:~# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md0 : active raid1 sda2[1] sda1[2]
      1999808 blocks [2/1] [_U]

unused devices: <none>

Then the device has not restarted until now (more than 12 hours):

MyBookLive:~# uptime
 22:07:34 up 12:04,  2 users,  load average: 1.00, 1.01, 1.05

What I don’t quite understand is why it is raid1, MBL obviously only has one hard disk?

Not yet. I‘d like to observe the current situation and see if I can find the real reason.