Elmojo

Has anyone been able to get WOL working in Rustdesk outside of a local LAN? I've asked on the Rustdesk Github, and the answer is "you can't", but that seems...implausible. I feel like there has to be a way to do such a simple and commonly-needed thing, especially since Teamviewer and Anydesk do it without issue. Any ideas?

I'm having the same issue, except that mine is a brand new Win11 install. Mine also halts at the "spice-server bug" line. Did you ever find a solution?

Yes, both in IT mode. One is a PERC H810 in HBA mode. That one is running my external MD1200 disk shelf. Those drives all sleep perfectly. The other is a PERC H730, also in HBA mode. That one is running the internal drives connected to the backplane. Most of the drives sleep fine, except for the 5x 6TB Seagate drives I bought a couple months ago.

Any additional thoughts on this? It feels like I'm really close to having this working...

Nope, mine are on Dell full size HBAs.

There are a myriad factors that can govern how certain hardware works (or doesn't) within a given environment. There often is no simple "explanation", unfortunately. If you find a definite culprit for the failure to sleep, other than "it's Dell's fault", then by all means, please share it!

I don't think this is correct. I have 2 RAID cards in my T630, both flashed to non-DELL firmware. All my drives spin down just fine, except for the specific Seagate SAS drives noted above. There doesn't seem to be anything in iDRAC or the Dell BIOS that would wake drives, but I haven't done a deep dive looking for that specifically. There are so many Dell servers out there in home labs, I think we'd have heard about it if this was a widespread, known issue.

I agree, but my cooling is kinda...overkill. lol I have a dedicated 14k BTU AC that's blowing directly into the intake of the server. All my server equipment is in a separate room, which is maintained at roughly 20c/45%RH. All the other drives in the same chassis run 32-40c when spooled up, and the drives in my external disk shelf avg 23-26c when up. It's only these Seagate drives that refuse to spin down, and also have temp issues. It's baffling. They're also the newest drives in my system, by far.

I would suggest you scan back through the last few pages of the thread. I'm having the same issue, with different Seagate drives. From my research, this seems to be an issue with some Seagate SAS drives, and I've been unable to find a solution thus far. It doesn't appear to be related to the controller, or to this plugin. If you find anything to the contrary, please share it! I'm actually unable to use my drives right now. Since they stay spun up all the time, they are running really hot (51c avg) and I'm afraid to leave them in service.

Possible, I guess. I'm using 38400, which is what I used in putty and it worked fine there. As for protocol, The thread that discusses how to talk to these MD1200 boxes says it uses the standard 8N1. However, that's not specifically an option with screen. The article linked above lists these variables as options... /dev/ttySX: Linux serial port (e.g., /dev/ttyS0 [COM1] ) baud_rate: Usually 300, 1200, 9600 (default), 19200, or 115200. This affects transmission as well as receive speed. cs8 or cs7: Specify the transmission of eight (or seven) bits per byte. ixon or -ixon: Enables (or disables) software flow-control (CTRL-S/CTRL-Q) for sending data. ixoff or -ixoff: Enables (or disables) software flow-control for receiving data. istrip or -istrip: Clear (or keep) the eight bit in each received byte. I'm using the baud rate (38400) and cs8 flags in my string. That may be incorrect, or incomplete. Anyone have any ideas? The folks over at STH have an extensive thread on the MD1200. It lists the communication as "RS232, 38400-8-n-1", if that helps.

So this is odd... I opened terminal and tried "screen /dev/ttyS1 38400,cs8", to see if maybe my serial port was just a different ID. I got the same blank screen with the solid cursor. However, if I pressed the up arrow (for history), I got all my serial console history from the MD1200! This tells me that my serial port is ttyS1, and that it does indeed appear to be able to talk to the MD1200, which is great news. Here's the weird part.... After that first contact, every time I try to connect again, or enter any new commands, the 'conversation' is getting more and more garbled. I no longer see the standard prompt for the MD1200 console interface (something like Bluedress_1.06.00:), nor can I even type commands at this point. I can start typing, but then it sort of stutters or freezes and doesn't allow me to complete the commands or execute them. If I arrow up, and execute past commands, it may or may not work, but the output is increasingly jumbled. Any idea what's happening?

Aha! I see, said the blind man... lol Now I have a blank screen, which makes sense, since nothing is connected. I'll check it out after a meeting this evening that I need to go prepare for. Thanks for the help! You're always on the ball, SimonF.

I'm not sure why it shows so many. My server only has 1 physical serial port. Maybe the others are internal headers or something?

When I run the screen command in terminal, using "screen /dev/ttys0 38400,cs8", I get the response: "Cannot exec '/dev/ttys0': No such file or directory" Is that just because the cable is not physically connected at the moment? I'm not super familiar with how serial comms work.

Gotcha! When I run that command in terminal, I get the attached... Looks like that last column on the right are serial devices, no? How do I figure out which is the actual serial port?

Detected where, exactly? Where would I look? I do believe it's enabled in BIOS, but I can check if it doesn't show up. I try not to reboot unless I have to.

I have a Dell T630 tower server, which has a physical serial port. I would like to be able to use this port to communicate with my MD1200 disk shelf, for health monitoring and configuration of settings. Ideally, I'd like to be able to do this using the terminal (or a plugin, VM, whatever) from within unraid, which seems like it should be totally doable. However, I have thus far been unable to figure out how to get unraid to talk to my T630's serial port. I've done all sorts of searching, and found somewhat related posts (mostly old) that seem to be asking similar questions, but none are really ever resolved. I've seen suggestions for using a USB-to-serial adapter, but I'm not really interested in that option, since I already have a specialized (expensive) console cable for my MD1200 that's serial-only. Anyone have suggestions for method for enabling simple comms between the unraid OS and the serial port? I'd love to be able to eventually run automated scripts on a timer, but let's walk before we run.

So I've done some additional checking, and it appears that my spin-down failures are not due to this plugin, or anything to do with a file system, or even disk activity, but rather the fact that I'm running these Seagate 6TB SAS drives. I know I've seen something about these drives having a spin-down issue, but can't find it right now. Does anyone have info on that?

Good point. Sorry I can't help. I no longer use this plugin for a similar reason. I'm now using binhex-urBackup. If you get the issue resolved, you might want to look into it as a replacement, if you haven't already.

There should be no need to reboot after installing or uninstalling any plugins or dockers with unraid, unless they are VERY poorly coded. That's kind of one of the big "selling points" of server-type architectures; that they don't require constant reboots to apply updates and software changes, even system-level stuff. Looking at you, Mr. Windows... lol

Okay, got it, thanks. I'll see about switching over to ipvlan. The failure was entirely mine, not yours. I've always had difficulty understanding networking of all types. I'm not sure why, since other computer concepts I find easy to grasp, but networking is like black magic to me. Will do. Not totally sure I'll grasp the implications, but I'll certainly make the effort. Thanks for all the info. I'll wade through it as I can, and make corrections to my setup as you've outlined. I appreciate all your time in putting this together for me!

Yes and no. Yes, multiple NICs. No, not a blade server. It's a PowerEdge T630. It came to me that way. I've actually removed 2 NICs to free up slots for other things. No idea why they had/need so many. I'm currently only using 1 port on a single NIC, but I'd love to be able to "gang" multiple connections to increase overall speed, kinda like we used to do with the old shotgun modems. Is that what bonding does, or is it just for failover/redundancy? So I read this before upgrading, and understood about 10% of it. lol What's a call trace? I assume it's bad, but there's no explanation. I've never seen anything like it as an error or in my logs, so I assume I don't have that issue? You say you recommend using macvlan, but later you say that using ipvlan is fine. I'm confused. Can you give an example of what difference it would make either way, and what sort of consequences it would have leaving things as they are? I'm firmly in the "if it ain't broke..." camp. However, I'm also a believer in tweaking things if they can be improved. Yes, I hear the irony... lol I'm sorry to report that I comprehended essentially nothing below this line. I can certainly follow the steps outlined, but... why? What would be the benefit? I'm not doubting your skill or knowledge at all, I'm just wondering, what shortcoming is this addressing, or what positive feature would I be enabling by monkeying with settings that (as best as my ignorant self can tell) are working fairly okay at the moment? ELI5, por favor? lol EDIT: So I did install the Tips and tweaks plugin, thanks! Are there specific changes I should be making, using that plugin?

capacity is in the eye of the beholder...

Oh, if only mine was that easy. lol

Mine looks like this... I feel like your post contains excellent, and extremely useful information, I'm just too ignorant to make use of it. lol