• Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

Elmojo's Achievements


Explorer (4/14)



  1. 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?
  2. 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.
  3. Any additional thoughts on this? It feels like I'm really close to having this working...
  4. Nope, mine are on Dell full size HBAs.
  5. 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!
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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?
  11. 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.
  12. 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?
  13. 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.
  14. 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?
  15. 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.