Marcel40625 Posted December 22, 2017 Share Posted December 22, 2017 Hey, im new to unRAID and wanna test it before i buy and running in an issue. After installing the unRAID 6.3.5 on the USB Stick and making it bootable i put it into my homeserver, after boot everthing seems to work fine. (watched nearly everything first in the WebGUI) okay after defining an array and creating a share i realized that i need another user for the smb share, so i tried to create one, but after pressing "ADD USER" after i put the credentials i want for it, nothing. WebGUI offline, only way to bring back the WebGUI seems a reboot. ;( in the syslog i found: Dec 21 21:07:25 Homeserver emhttp: userPasswordConf not found Dec 21 21:07:25 Homeserver kernel: emhttp[1653]: segfault at 0 ip 00002b408a33713a sp 00007ffd431f6378 error 4 in libc-2.24.so[2b408a1e8000+1bd000] tried 2 different USB drives because thinking one has a failure, but everytime the same and chkdsk on the drives prompt no errors. hope someone has an idea. already order 3 different USB drives via Amazon Prime, maybe its realy dead drives but dont know. EDIT: okay i might found the reason ... the password from the user i added was to complex 93-|Z"P`\0^0zea#?F^X seems to much for unraid ... a but stupid in my opinion ... a password with only digits and lowercase letter works fine ... BUG REPORT: Link to comment
Frank1940 Posted December 22, 2017 Share Posted December 22, 2017 What size USB drive are you using. (I believe that USB drives should be less than 32GB.) Link to comment
Marcel40625 Posted December 22, 2017 Author Share Posted December 22, 2017 one has 32gb and the other 2 have 16gb, but they are old, might be realy corrupt, like i said waitig for Amazon to arrive today hoping for other ideas Link to comment
Marcel40625 Posted December 22, 2017 Author Share Posted December 22, 2017 okay i got the new drives, all from Intenso, the 8gb isnt showing in the USB Creator, the 16gb is blacklisted? wtf?! and on the 32gb the syslinux.exe is crashing when trying to make it bootable. Link to comment
itimpi Posted December 22, 2017 Share Posted December 22, 2017 The blacklisted drive is almost certainly from a manufacturer who does not give each USB drive they manufacture a unique GUID. Such drives are unsuitable for use with unRAID. Link to comment
Marcel40625 Posted December 22, 2017 Author Share Posted December 22, 2017 yeah i noticed that too, damn it! ordered now some other drives from Sandisk and Tochiba ... hope they have an uniqe id ... not the best start Link to comment
Marcel40625 Posted December 23, 2017 Author Share Posted December 23, 2017 okay i might found the reason ... the password from the user i added was to complex 93-|Z"P`\0^0zea#?F^X seems to much for unraid ... a but stupid in my opinion ... a password with only digits and lowercase letter works fine ... Link to comment
BRiT Posted December 23, 2017 Share Posted December 23, 2017 5 hours ago, Marcel40625 said: okay i might found the reason ... the password from the user i added was to complex 93-|Z"P`\0^0zea#?F^X seems to much for unraid ... a but stupid in my opinion ... a password with only digits and lowercase letter works fine ... Potential trouble characters I'd test with a known to work password are individual characters from |"`#? and then the combo of \0 Link to comment
Frank1940 Posted December 23, 2017 Share Posted December 23, 2017 I seem to have a vague memory that this problem has cropped up before. It has to do with the fact that changing User Passwords are being processed by the shell program and this program uses 'special characters' to denote special actions. For example, the # denotes that everything that follows is a comment and should be ignored. Link to comment
Marcel40625 Posted December 23, 2017 Author Share Posted December 23, 2017 Might be, might be, BUT this should never crash the WebGUI, especially when the WebGUI is the only comfortble way to restart the server there should be a 1) Better script because i can use this kind of password when using shell directly or 2) A check for spezial characters in the WebGUI in my opinion thats a major issue, should i report that as an bug? Link to comment
Squid Posted December 23, 2017 Share Posted December 23, 2017 5 minutes ago, Marcel40625 said: 2) A check for spezial characters in the WebGUI IIRC this was fixed in 6.4 Link to comment
Frank1940 Posted December 23, 2017 Share Posted December 23, 2017 17 minutes ago, Marcel40625 said: in my opinion thats a major issue, should i report that as an bug? Why not? I would start a new thread in this section of the forum https://forums.lime-technology.com/forum/65-prerelease-64-support/ and give the basic symptoms and what you found. Then put in a link to this thread for complete details. It may have been 'fixed' earlier but you may have found a special case that got missed. Link to comment
Squid Posted December 23, 2017 Share Posted December 23, 2017 On 12/22/2017 at 12:18 AM, Marcel40625 said: unRAID 6.3.5 4 minutes ago, Frank1940 said: https://forums.lime-technology.com/forum/65-prerelease-64-support/ https://forums.lime-technology.com/forum/52-defect-reports/ Link to comment
Frank1940 Posted December 23, 2017 Share Posted December 23, 2017 6 minutes ago, Squid said: https://forums.lime-technology.com/forum/52-defect-reports/ Big Mistake on my part. You are right!!! Link to comment
Marcel40625 Posted December 23, 2017 Author Share Posted December 23, 2017 Bug Report created: Link to comment
Acemon Posted February 18, 2018 Share Posted February 18, 2018 I find myself in a similar situation just now. My WebGUI just resounds '500 Internal Server Error' when trying to sign in, although all my services are running and I can SSH in just fine. How did you manage a clean reboot? Seemingly my issue is a 'Permission Denied', that is what nginx error logs say, and what I see when trying powerdown command. Edit (copied from my post on /r/unraid): Finally got it fixed. In case anyone ends up here, I will shortly explain problem and solution. However, I have yet to determine the cause. Problem was that /sbin/init script had lost its execute permission. So a simple chmod +x /sbin/init did the trick. How this happened, I have no idea. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.