Mijzelf  Guru Member

But the share is still not working Is samba running? ps | grep smb or maybe ps -A | grep smb depending on the invoked ps. As said I have no idea what causes this, but I'm certainly not a samba specialist. Maybe @django_alexander has an idea?

That doesn't look good. There are 'unhandled error code's from the harddisk, whatever that may be. If your data is valuable, you should create a bit-by-bit copy of the harddisk, and do a filesystem repair on the copy. I suppose you have a disk slot free? In that case the copying can be done on the NAS itself. I can provide…

It doesn't exist. The CLI is a Linux CLI, which is far to extensive to catch in a manual. The 542 runs busybox. You can find a list of commands here, but not all commands are implemented. Further there are other binaries added. In many cases you can find their usage on google. And there are also undocumented commands,…

That is amazing. I wrote that package something like 10 years ago, and as far as I can remember this issue never popped up before. except for 2 weeks ago: For him reinstalling the SambaReplacement package worked, but actually I have no idea where this suddenly comes from. A power outage can corrupt files, but the…

That input/output errors are either a filesystem error, or a disk error. A filesystem error might be cured by a filesystem repair, a disk error means almost certainly you'll have to replace the disk. The kernel log should tell which one it is. You can read it by executing 'dmesg'.

Most settings are stored on a flash partition, not on harddisk. Yet I'm not 100% sure the ssh server (telnet is not the best choice) indeed doesn't write on disk. In case a symlink is the cause of the problem, it doesn't matter anyway, because it's not an error. Only the webinterface crashes on seemingly cyclic directory…

Neither will destroy your data. A factory reset deletes the configuration, which means you'll have to reapply users and shares. (The directories are still there, but you'll have to 'promote' them to share). A rescue stick only flashes firmware, and leaves everything else as-is.

The file libiconv.so.2 is damaged. Don't know why. You wrote that the 3TB is in bad condition. Maybe related? In theory you can download a fresh copy here, (which you'll have to extract), but writing to a dying disk is asking for troubles. You could remove the 3TB, then the 4TB becomes systemdisk, and you can install…

Depends. When the kernel still boots (which doesn't necessarily gives a reachable NAS) you can use a RescueStick. I don't have one for the 542, but the stick for the 540 should also work, when you exchange the .bin file by one from a 542, and put it's md5 sum in the appropriate file. But if the kernel still boots, a…

After removing the old disk, you'll have to reboot, to 'promote' the new disk to system disk. But you probably already switched the NAS off to remove the old disk.

Strange. The package contains only two files: /opt/etc/init.d/S09ZyXELSambaReplacement and /opt/etc/samba/ZyXELSambaReplacement.conf. That's it. Don't see what it matters to reinstall these. There is no init script which sets things up. The only 'nasty' thing is in /opt/etc/init.d/S09ZyXELSambaReplacement, on start it…

You can move the 4TB to the first slot, but you don't need to. The NAS doesn't care in which slot the disks are. If you have two disks, and swap them (with the box off, off course) it will still recognize and use them.

Unpack the .zip file. There is a large .bin file inside, which you can upload using the webinterface of the NAS.

If you have installed packages they will be gone. They are installed on a hidden part of the 3TB disk. Further the new volume is a new volume, which means that you'll have to re-assign shares. The old shares point to the 3TB disk which is no longer there.