Hello,
Since QuTS Hero 6 isn’t final yet and I couldn’t get Samba running with the beta, I thought I’d update to 5.3.3.3424.
Unfortunately, after that, SAMBA no longer works and my ISCSI LUN doesn’t work either.
SAMBA: fallback to 36445 or nothing at all. Lots of errors when trying to repair:
[~] # netstat -tln | grep 445 [~]
(empty output)
setcfg Samba EnableKernelSMB FALSE -f /etc/config/uLinux.conf [~]
/etc/init.d/smb.sh restart
Restarting SMB services: Shutting down SMB services:{“retcode”: -15, “result”: “failure”, “error”: “CLI is busy”} smbd-notifyd cleanupd smbd mdssd-master mdssd-child{“retcode”: -15, “result”: “failure”, “error”: “CLI is busy”} nmbd. Shutting down winbindd services:{“retcode”: -15, “result”: “failure”, “error”: “CLI is busy”} winbindd. Starting Regenerating smb_a.conf from smb.conf. Starting SMB services:Shutting down winbindd services: winbindd. {“retcode”: 0, “ret”: “success”} Starting winbindd services:{“retcode”: -15, “result”: “failure”, “error”: “CLI is busy”} {“retcode”: -15, “result”: “failure”, “error”: “CLI is busy”} {“retcode”: -15, “result”: “failure”, “error”: “CLI is busy”}
ISCSI: Target missing
If I try to create a new one, I can’t connect the existing LUN.
After wasting half a day with ChatGPT, I’m going to downgrade again 
Then backup TVS-h674 to the TS-673
Then—well, what next?
Regards,
Alfred
That sounds more like a bug than a feature request… moved
Here in the German section, it was previously in “Feature Request.”
Please open a support ticket and our support team will be happy to assist you. We would also like to know which version you upgraded from to 5.3.3. Thank you!
(Translated by AI)
Upgraded from QuTS Hero 5.2.9.3410 to QuTS Hero 5.3.3.3424.
Afterwards, the iSCSI target disappeared and SAMBA wouldn’t start or listen on port 445 anymore.
As mentioned, I rolled back to QuTS Hero 5.2.9.3410 and was able to restore SAMBA and iSCSI.
For now, I won’t open a ticket as 5.3.3.3424 is no longer installed.
Or would it still make sense to do so?
If you like, you can also download the logs from the Help Desk and send them to me via private message. I can then forward them to our internal team for analysis. Thank you!
(Translated by AI)
How to download diagnostic logs from the Helpdesk app | QNAP
Hi Steve - 1st… english or german?
2nd - how the hell do I send you the zip-file?
and yes - would be nice if you could find anything regarding these fatal errors..
Cheers - Alfred
German section, so English please
Nice of you to reply – but I don’t know if Steve speaks English, and what the AI (which, according to you, causes more problems than it solves) will end up translating 
SteveKo is from Taiwan (QNAP HQ), his answer was translated via an external AI.
It’s best to turn off the automatic AI translation of the forum at the very top, then it becomes clear in which language the posts here in the forum are originally posted.
Otherwise, everything turns into a Loriot sketch here if all posts are constantly being translated back and forth into different languages.
1 Like
Very good point – thanks!
But now, just to make it clear for dummies…
My post is now in the German-speaking section.
Steve writes in English and the AI translates into German – now that’s been turned off.
So should I reply in German or in English?
Or would you move the thread to an English-language section?
I just think that an AI can’t translate everything, and after 40 years in IT, my English is pretty decent
The AI only translates in the reading direction, not when you write. So SteveKo used an external translator to post in German in the German forum (otherwise he would probably only be able to reply in Chinese or English).
In the German section (see screenshot above), please reply in German.
If you’re able to write in English as well, just open the next topic in the English section.
Our team has analyzed your logs and, after some time, tried to reproduce the issue but was unable to replicate the situation you described. If you perform another upgrade in the future and encounter a similar problem, please open a support ticket so our support team can investigate this further. Thank you again for your help!
(Translated with AI)
