salvdordalisdad

Members
  • Posts

    29
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

salvdordalisdad's Achievements

Newbie

Newbie (1/14)

1

Reputation

1

Community Answers

  1. Hi Guys, Very glad to see it being maintained. Much appreciated, thanks. I have a whole bunch of scripts which use netcat "nc" to send hand-crafted TCP streams to a target TCP socket across the network. It's specifically for some automated LED lighting which is pre-tasmota. I had to reverse-engineer the commands to set colour, brightness etc. so these are sent using "nc" That doesn't appear to be in the current release of Nerdtools, unless it's hiding in a package... Is it hiding, or can I request it please? (or get some hints as to how to install it please?) Can't upgrade to 6.11 without it. Thanks in antici....pation. sdd
  2. --Update-- I found a few dockers on Dockerhub, as searched in "Apps". One working version (signed) is: ibhde/lldpd/ You need to run it with network configured as "host". It will grab some info & present it - such as the original hostname etc You can add variables or adjust the ones provided. Works as expected on my 3 unraid servers. YMMV. Still would be nice to have it as part of Nerd tools, where it really belongs, but this will do until then.
  3. Hi Guys, You can tell whether a techie is network-centric because they always want to ssee stuff like LLDP in use everywhere ! It's supported on most distributions, and well documented, and relatively low risk, please can we have it on Unraid? As far as I can tell - as a multi-server for multiple years owner - it's about the only thing missing from Unraid. I know I could run up a VM or (if I knew how) a docker perhaps, but that's a fudge & I'm not so keen on fudges as they always end up biting you. Nerd tools seems like the obvious place for it. It's so useful to confirm what's connected to what - "is it in the right port?" is sometimes the MOST important question, saves hours sometimes. Bit like the picture attached (only with all the information intact of course!) Any chance maybe, pretty please? keep up the brilliant work. TIA
  4. ...and a post scriptum for the record... After the parity build had completed, the system was left idle for a few more days, adjusting this & adding that etc. The parity drive started giving READ errors, only a few hundred, but even a handful is too many for a fresh build. So I swapped it out - reluctantly expecting another 5 - 25 day parity build - and was shocked to see the estimate for the new parity build should take around 8 hours... It actually took 10 hours, but heavens to betsy what a difference! Just a shame that the original cause (the Toshiba 7200 rpm) parity drive problem could not be spotted earlier...I had my suspicions but no evidence. So what have we learned here today? If the parity build says it's going to take 25 days - one of the disks is probably faulty. Now go & figure out which one!
  5. Hi All, Rather than fret about it, I figured I'd just ask it every few days & see. I asked it today & found this message: Last check completed on Tue 24 May 2022 08:04:42 AM BST (two days ago) Duration: 4 days, 7 hours, 14 minutes, 8 seconds. Average speed: 10.8 MB/s Finding 0 errors And it's all running fine, no errors. Pesky calculator got it massively wrong! Oh well, it was a very ueful learning experience - stop fretting & let it do its thing! Thanks to all who chipped in.
  6. Hi JorgeB Thanks, I did a quick & dirty single disk array & got docker up & running on fresh demo license & new USB stick (seemed quickest!) These are the stats from the disks: disk MB/sec MB/sec sdf 200 97 sdg 157 70 sdh 200 87 sdb 150 73 sdc 200 94 sdd 183 84 sde 142 67 They all seem pretty much within a similar range, no single one stands out as clearly having difficulties. Any thoughts? Thanks in advance. (Nice picture - Slava Ukraine! )
  7. That's really interesting, but if I have no cache? Anyway, I started with a fresh 6.10 trial on a new USB, as I had clearly got something wrong & I am comfortable with starting from scratch. So I ran the diskspeed benchmarks & was a little surprised at the max & min values. disk MB/sec MB/sec sdf 200 97 sdg 157 70 sdh 200 87 sdb 150 73 sdc 200 94 sdd 183 84 sde 142 67 So I chose the fastest (sdc) as the parity. Are these figures good enough? Do they indicate any underlying issues? Anyway, just rebuilt the array again & started it & it's now saying 16 days . The CPU is trundling along at 3% util, so it's not that. All the SATA ports are 6Gbps, all the disks are 6Gbps. Any suggestions, or just "yeah it might do that" Thanks in advance for any pointers. Also - when I want to move back to the old USB, what do I copy from this USB drive to that one & what do I delete on that one? (I know that the license in in the plus.key file, but virtually naff all else of what's on there).
  8. Hmm, yes it dort of works, but it still says "path does not exist". I think I'm going to scratch this server & start again. Now I need to find out how to do that on the existing USB drive... some searching to do I think. But not right now, out of time, have to be after the weekend now. ;-/ Thanks for the nudges, much appreciated...
  9. So I did some digging into those diags & saw a LOT of dead tcp connections, and spotted that port_ping+ I cancelled all of the (legacy from previous config) user scripts & rebooted. Now those connections are gone, which is as expected. The parity build time has gone down to 9 days - which is an improvement - woohoo! I think I've spotted another slight issue... Can't run docker diskspeed Docker ... "path does not exist" There was no /mnt/system/docker folder, so I created one - now it doesn't complain about that anymore. There's no /mnt/user/appdata folder - but I can't create one of those... "no medium found" Contents of /mnt/user: root@n3:/mnt# cd /mnt/user root@n3:/mnt/user# ls -l total 0 drwxrwxrwx 1 nobody users 6 May 19 11:07 filestore/ I'd expected a bunch of folders, system, appdata, domains... Do I just create those, or is something lower level going to be required to fix that? - open to suggestions. Tried creating "system" as a share - didn't do anything, no folder in /mnt/user at all. So I created the folders /mnt/system/docker and /mnt/user/filestore/appdata But even with those fudged the docker refused to start. Definitely something lower level needed. I will tiidy up that mess I just made...and await the right instructions. (Even if those instructions involve starting from scratch)_. Thanks in advance Lee
  10. Hi Guys, I just recovered my 3rd unraid server ("Plus" license) & replaced a couple of disks intending it to become a backup target. So I zeroed all the disks & created a new array of 7 x 4Tbyte disks, with one of them as parity. All the disks are completely blank, freshly formatted in xfs. These were happy in the old servers, so I assumed they'd be OK for this job. However, it seems not. The parity build (1st time as it's a new array) says it will take 25 days to complete. When it first started, it said 10 hours, and has crept up since then. So clearly something's wrong, probably a dying disk, but I don't know how to diagnose it, so please can someone read the diags & point me in the direction of the faulty disk?n3-diagnostics-20220519-1514.zip Thanks in advance. Much appreciated. Lee
  11. ...aaaaaand that was the cause. Why on earth would you provide 2 m.2 slots when only one of them works! That shouldn't be in teeny tiny small print on page 57, it should be in large print with a WARNING sign... oh well, you live & learn. ;-/
  12. Hi Guys, Just re-using an nvme drive 256gb intel (I think) drive for use as a cache experiment. The drive is working, I cleared all the partitions & reset it as GPT n2-diagnostics-20220102-1701.zip There's 2 slots on this motherboard, so I used slot 1 & re-powered the server. But it doesn't show up, I think I must be missing something. The motherboard doesn't seem to need to have the m.2 slots enabled. Here's the diag download. Not sure it's any use as the drive isn't showing up there either! I've done this on many occasions before & not hit this snag before... I've done a bit of googling, but all the answers get very specific quickly, so better to ask for help I think. Open to suggestions as always. Thanks in advance. Supplemental: Just read through the MB manual, and it looks like maybe one of the slots is disabled! (very small print bit about ...only supported in 11th gen CPUs...) (i HATE small print ! ) Will move it & update.
  13. D'oh! Rookie error! Very grateful for that. Increased my understanding by one notch... Thank you.
  14. Hi Guys, Not sure it's a bug, but just updated from 6.8.3 to 6.9.2 Was advised to post it here to let you (dlandon) know. 1st thing I noticed which was OK but now isn't quite working is on the "Main" tab. Under the SMB / NFS / ISO shares section, the orange buttons labelled "Add Remote NFS/SMB share" and "Add ISO File Share" had disappeared & a debug line was displayed instead. So I deleted my two NFS shares & the buttons re-appeared. But if I add a NFS share back again, the "add" buttons disappear and I get this line of debug instead: Fatal error: Uncaught Error: Call to undefined function _() in /usr/local/emhttp/plugins/dynamix/include/Helpers.php:35 Stack trace: #0 /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php(387): my_scale(0, NULL) #1 {main} thrown in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 35 The share process works exactly as expected & the share is certainly working AOK. However, I can't now add a 2nd share because the buttons have disappeared. Suggestions welcome on how to debug further to get you the info you need. Thanks in advance.