Mijzelf  Guru Member

BAD MAGIC is the output of ´info_setenv MODEL_ID B403´? In that case I suppose the bootloaders environment partition has a wrong header (or footer) somehow.You can try to do it from the bootloader prompt, maybe that will restore the right header. Did fw_printenv work without complaints?

First try fw_setenv without arguments, or with '-h' to get a syntax. In the u-boot prompt it would besetenv MODEL_ID B403saveenvI think in barebox it is the same. fw_setenv is designed to provide u-boot compatibility, so I'd expect fw_setenv MODEL_ID B403(saveenv is not necessary)

No, it's the modelid in the bootloader environment. B103 is NAS540, B203 is NAS520, and B403 is NAS542.You can read and write it with fw_printenv and fw_setenv. In think these binaries are in /firmware/sbin, or something like that.Of course you can also use the bootloader command prompt.

booting kernel of type uimage from /dev/nand0.kernel1.bbBad Header Checksum Failed.booting kernel of type uimage from /dev/nand0.kernel2.bbBad Header Checksum Either both kernels are corrupted in flash (unlikely), or the environment is corrupted, leading to either a wrong kernel size, (if you load only 2MB of a 3MB kernel,…

I see I made a typo.ln -s /opt/var/run /var/run should be ln -s /var/run /opt/var/run If that doesn't help, try to look at the output of the start script: /etc/init.d/samba.sh startup Do you? How is your config special?

Don't know why it doesn't work for you, but experiences in the past show that sometimes some lock file goes out of sync. The remedy is to symlink /opt/var/run to /var/run. In that case every lock is reset on boot. rm -rf /opt/var/runln -s /opt/var/run /var/runreboot Don't know about the 'utility app'. Never used it.

I read the same. And yes, that is a small percentage. 0.00001%, when I'm not mistaken.

I don't see anything special in the configuration of port 33. When I look at the difference of port 30 (LocB-LinuxIoT) and port 33 (LocB-PC1) (port 33 can be pinged from LocA-WinSrv, port 30 cannot), I see only a difference in 'Acceptable Frame Type'. 33 is all, 30 is untag only. But that shouldn't make any difference. It…

There is no space left.sda is 15625879552KiB, which is 16000900661200 bytes, which is slightly more than 16TB.sda2 is 15625378816KiB, so the difference is 500736KiB which is slightly more than the size of sda1.md0 is 15625377656KiB, so the difference with sda2 is 1160KiB, which is OK for me. 
 Nope. That GB's are…


Did you already check in /proc/partitions if there is actually room for expanding? The NAS does use swap, you can see that with 'cat /proc/swaps'. But not all types of memory usage can be swapped away. Swap is incredibly slow for random access. The access time for a byte in memory is measured in nanoseconds. The…


LocA-WinSrv cannot ping LocB-PC2, but LocB-PC2 can ping LocA-WinSrv. In that case I suspect routing/firewalling rather than VLAN's. Yes I did, and I see some inconsistencies. Yet it is hard to read without knowing which port is suspicious. I must admit that it's some time ago I configured ZyXEL switches. And in that…


Return value 8 is Operational Error. Seeing the error 'Memory allocation failed', I think you can safely assume that a 320 doesn't have enough memory to fsck a 14.8TB filesystem.About the 14.8TB, I first thought that were actually TiB's, but a quick calculation shows that cannot be true:…

That Logitech server, is that the ZyXEL provided one? In that case it can't use Entware-ng perl, as it won't search /opt for binaries.*Maybe* it works if you start the Logitech server from a shell which has the /opt directories in PATH. That should be something like /i-data/md0/.system/zy-pkgs/etc/init.d/Logitech.sh…

That is the same error as this guy had, so I suppose Plex changed something nasty. I suggested to use the Netgear package instead, and he never came back, so maybe that is the solution.


My guess is that recovery is when one of the disks went out of sync, due to being unavailable for some time or due to a bad sector, while resync is creating a new raid member on an empty partition. Or maybe just the other way around, the words seem equivalent in this context. Timewise it doesn't matter, as the…