Jump to content

TeeNoodle

Members
  • Posts

    19
  • Joined

  • Last visited

Posts posted by TeeNoodle

  1. Hello!

     

    Been running UD for a while. Just updated to the last version, and for some weird reason, all i can see in the UD section is the Unraid loading animation. Same when I hit on the plugin icon in Plugins. Anyone else has that issue? Should I just completely restart Unraid?

     

    T

     

    logs:

     

    Feb 13 21:04:02 NoodleNet php-fpm[10142]: [WARNING] [pool www] server reached max_children setting (20), consider raising it
    Feb 13 21:10:53 NoodleNet nginx: 2019/02/13 21:10:53 [error] 10212#10212: *994825 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.229, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.20", referrer: "http://192.168.1.20/Main"

     

    load is around 20, which is super bad.

     

    second edit:

    since the load was terrible, I rebooted it all. seems to be back to normal.

  2. 7 hours ago, olehj said:

    Commit #29 - BUG: Javascript: Added delay between kill and start/stop to the Locate button, should be more stable now. Thanks to TeeNoodle for debugging and testing.

    Just tested the new update, works flawlessly. 🤘

  3. 6 hours ago, olehj said:

    Maybe it isn't that bad anyway.. it looks like this is specified by the hardware controller before the connected device. So rather a bad approach of defining hard drives at my end. I just saw some nice looking unique numbers and thought that would be a good idea, but I expect they might change if you change HW controller (like raid cards or motherboards). I better get down and changing this behavior to a MD5/SHA1 hashed number based upon family name, device model and serial number - I guess I never seen any drives (at least serious ones) without a serial number.

    Thanks for the info you provide, it helps me understand even more of how things might be setup.

    It's not only that serial in your plugin, i checked it out and both SMART and Unraid reports the serial as is. So yeah, might be a good idea to rely on something else for disk identification in the long run. Mind you, it's ADATA, and i don't know for other manufacturers.

     

    Brother, you're most welcome, it's my pleasure to help you debug and improve on that plugin. I consider that what you did with that plugin should already be in Unraid in the first place. So, anything you need me to provide or test, I will do if possible.

     

    Also, sent you monies for a beer. You deserve it.

  4. 1 hour ago, olehj said:

    That is actually a bit scary - typically everything will have a LUN in my mind. I do have it on my SSD drives and all other drives. For sure my script will fail if you add two of these drives as it is heavily depended on the LUN. You can check smartctl -i /dev/<path to device> if you get something else than a bunch of 0's. Look for: "LU WWN Device Id"

    root@NoodleNet:~# smartctl -i /dev/sdh | grep LU
    LU WWN Device Id: 0 000000 000000000

     

    Freaky, huh??

  5. 3 minutes ago, olehj said:

    Ye, the SSDs can be a bit lacking when it comes to SMART information, and seems to work different with LEDs, temp works though. I have 2 identical SSDs so I need to check the serial number of the drive and hopefully have assigned the correct tray to it

    Then this is a bit weird:

    1:0:6:0 0000000000000000 ADATA SU655 2I4220072140 480.1GB SSD 2.5 inches

    Are SSDs lacking Logical Unit Numbers for a reason?

     

  6. Just now, olehj said:

    Sweet! Then it will be included in the next update

    Fantastic! Thank you so much for your help! Thanks to you, now I will know in which damn tray which drive is, in case one of them fails ;)

     

    I noticed it doesn't work with SSD disks, but you had warned me about it, and it's fine because it's the only SSD disk in the array, so by elimination, I know which one it is. It doesn't display the SSD temp either, but meh! I think we can all live with that ;)

     

    Again, great work. You made a very useful plugin, which I think everyone will really enjoy. I know I will!

     

    Cheers

  7. 5 minutes ago, olehj said:

    10-4! HUZZAH! WE GOT A WIN!

    Tested flawlessly on Chrome x64, Firefox x64, and Firefox Linux/x64. Tried multiple drives. They all respond with a beautiful blinkage.

     

    Thank you so much! Now that plugin is damn shiny!

     

    Cheers!

  8. 6 minutes ago, olehj said:

    Did you try the new update? I have done some mods to it. For me it works the same in Win and Linux now

    Sadly, still no dice for me. I really wonder why it's doing that...

     

    Chrome + Firefox on Windows = no dice.

     

    However, i DID manage to get something out of Firefox for Linux, but. It works once. Once it's stopped again, it won't work again.. until i reload the page. Then, it works again, once. And then won't work again after stopping it again. Now, even after a page reload, it won't work anymore.

     

    It's the weirdest thing.

  9. 1 minute ago, olehj said:

    Did you try the new update? I have done some mods to it. For me it works the same in Win and Linux now

    Just updated it as soon as it came in! :D

    Sadly, still no dice, but let me completely remove and re-install the plugin, plus i'll clear cache and everything. Stay tuned!

     

  10. 8 hours ago, olehj said:

    This does work flawlessly. I get disk LED activity. The second command does indeed stop the process. So there's something between JS and PHP.

     

    Tested it on Firefox and Ubuntu. Nope.

     

    And i THINK i know what's maybe possibly going on. I'm no coder, but bear with me.

     

    Checked through the Firefox inspector, in the Network tab. When I hit that button, it simultaneously seem to do a GET request both on the cmd=killall and then issues a cmd=start command on the drive. Is it remotely possible that there's a racing condition happening here? Like the kill command being delayed, and killing the start command as it happens? Maybe network latency could cause that. I tried adding a 'sleep 2' at the begining of the smartlocate script, but that didn't seem to help. I'm a bit baffled.

     

    Cheers!

     

     

     

     

  11. 7 minutes ago, olehj said:

    I'm mainly a hardcore linux user. I tried the function in Windows now, and it seems to have a bit more problems there. I did however succeed a few times, but it is way more unstable.

    So am i, brother (Linux sysadmin here), but that's my home desktop which is a gaming machine ;) In my case, I didn't manage at all, it's not even intermittent, the smartlocate function doesn't seem to be executed properly at all. Will keep you posted with the URL tests as soon as i get home.

     

    Cheers

  12. 23 minutes ago, olehj said:

    It looks like this is a Windows specific problem, can you try to check if you see activity happening on 1:0:1:0 using this URL

    fantastic, i will test this tonight as soon as i get home. are you telling me you're testing it on Linux browsers?

     

  13. 6 minutes ago, olehj said:

    If you go directly to the source file, does it give you a blank page (expected result) or does it say "File not found"?

    Getting a blank page

     

    PS: i'm on 6.6.6, didn't upgrade yet.

  14. 1 hour ago, olehj said:

    What web browser are you using? The call happens from javascript and has mainly been tested with newer Vivaldi, Chrome (both blink engines) and Firefox.
    Be sure you haven't disabled javascript, or have any plugins/extensions disabling it.

     

    Edit: And does the "Locate" button change to black background and does it say  "Stop" after clicking it?

    I'm using Firefox (Win64-Win7) but just tested it on Chrome, to no avail. Button does toggle to black, as it should. Firefox has a few addons, nothing that should interfere with JS, but Chrome is stock. Seems like the JS calls work, but shell execution doesn't, for some reason. I tried starting the Location button, and doing a ps aux | grep smart a bunch of times while it's supposed to be running, and i never see the shell command pop in.

     

    Cheers!

     

  15. On 1/23/2019 at 9:32 PM, olehj said:

    The Locate function is very vague and only calls smartctl -x /dev/bsg/PATH every half second.

     

    You can test manually by using that command, just replace PATH with the path number available (you can see it from the list, or by ls /dev/bsg). Everytime you run the command, the LED on the HD might light up. If the smart data does not work, goes too fast, then the locate button won't work either.

     

    After multiple tests, targeting the same device for consistency:

     

    - manual smart -x test always works. of course it's a short bleep, but it works flawlessly. if i shell loop it, i definitely get some flashing action.

    - tried targeting the same exact device with the plugin (in this case 1:0:1:0). nothing. not even a tiny blink. tried triggering other disks. also tried spamming the Locate button multiple times. got nothing.

     

    I definitely think there might be a code glitch there. The shell command definitely does what it should. The plugin, unfortunately, doesn't. Hope this helps.

     

    Cheers!

     

    EDIT: went ahead and checked the code on GIT and noticed you use a shell function called smartlocate. So, went ahead and tested it. Works flawlessly. So the issue seems to be between your PHP code shell call and the function. But I can't really debug deeper.

  16. Hello Olejh!

     

    First, I was really awaiting this plugin, and it looks amazing! Testing it on 6.6.6, on a Dell R510, with a H200 in IT mode. Drive lights seems to be working normally when I access the array or preclear disks.

     

    However, I get no disk light activity when I hit the Locate buttons. Tried different disks, and waited a bit to see if it would light up, to no avail.

     

    Any idea?

     

    Thanks in advance

×
×
  • Create New...