TD2779

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

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

TD2779's Achievements

Noob

Noob (1/14)

2

Reputation

  1. SSH into your server, and then I think you can docker exec into that container. I apologize that i don't know the command off the top of my head.
  2. Upgraded to 6.10.3 and after a longer-than-usual boot, server was inaccessible. Upon further examination, saw that the NIC wasn't assigned an IP address. This is via a PCI-E, Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller. Moved cable to integrated NIC, rebooted, and the integrated NIC worked fine. I haven't done further troubleshooting, other than to switch cable back to original NIC, revert to 6.10.2, and the Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller works fine again. cybertron-diagnostics-20220620-2224.zip
  3. Thank you so much for your help and patience, this worked and was super easy. (If anyone needs to do it)
  4. I hit [edit] on the container, and while I see OTHER Java-related variables, I don't see one for JAVA_VERSION. Do we need to add this manually? Just trying to stay ahead of impatient 10 year-olds.
  5. Before I deep dive into this, does anyone think it could be used to track SHARE size over time?
  6. SOLVED After speaking with the guy I purchased the card from, we identified that the DRIVE has HP firmware and seems to be presenting some incompatibilities. I was able to connect 4 SATA drives to the card without issue.
  7. A few hours into the parity check and the same messages hit the log roughly every 3 minutes. I don't particularly see a hang, but maybe a slight dip in the storage stats as shown in the attach screen snippet. I'm not sure how I'd test the power, other than having a completely 2nd PSU running this one drive. Is that even safe to do?
  8. [edit] SOLVED After speaking with the guy I purchased the card from, we identified that the DRIVE has HP firmware and seems to be presenting some incompatibilities. I was able to connect 4 SATA drives to the card without issue. [/edit] I added a LSI controller card and a new SAS drive to my server. All other drives live on built-in SATA controller. Precleared the drive, and it passed without issue. From what I could tell, the SMART data looked good as well. This is an LSI card in IT mode, purchased from artofserver on ebay. Drive is attached to a cable that starts at the card and breaks off into 4x SAS connectors. Only using one at the moment. Well I added it to my array to replace a smaller drive I had, and the rebuild went smoothly. Completed within 10 hours or so. (6TB parity, with 2x6TB drives) The past couple of days I was moving some large files from a machine on my network to AND from my server and noticed the transfers taking longer than I expected. If I watched the stats, I'd see the transfer plateau at 1Gbps but then periodically drop to almost ZERO, only to pick back up again. We're talking in the middle of transferring a single file in the 10's of GB range. To eliminate the other machine or network being an issue I used the command line on the server to copy some large files from drives to themselves. i.e. /mnt/disk1 to /mnt/disk1 All drives worked as expected EXCEPT the new drive. Same issue. Watching the stats, I could see the copy periodically hang before continuing. Never had this prior to adding the new drive. Installed the DriveSpeed docker to benchmark it, and the speed of the 6TB SAS drive matched pretty closely to the results of the other two 6TB SATA drives in my system. Other things I've tried: Swapped the PCI slot for the controller, used a different SAS connector on the cable, removing non-array drives from system in case it was a power issue, and used a different power connector. Unfortunately I don't have another SAS drive or different cable to try out. I started watching the syslog during transfers and started seeing a large number of the same message EXACTLY when the transfer speeds would stop. Jan 16 18:49:09 CYBERTRON kernel: sd 1:0:0:0: attempting task abort! scmd(00000000093ec5f7) Jan 16 18:49:09 CYBERTRON kernel: sd 1:0:0:0: [sdb] tag#222 CDB: opcode=0x88 88 00 00 00 00 01 05 9d 7b 80 00 00 00 40 00 00 Jan 16 18:49:09 CYBERTRON kernel: scsi target1:0:0: handle(0x0009), sas_address(0x5000cca23c11ae65), phy(2) Jan 16 18:49:09 CYBERTRON kernel: scsi target1:0:0: enclosure logical id(0x50050760438173e8), slot(1) Jan 16 18:49:09 CYBERTRON kernel: sd 1:0:0:0: task abort: SUCCESS scmd(00000000093ec5f7) My google-fu might be bad, but I don't know enough to understand what these messages are and I've run out of things I can think of to try without spending money. Help! p.s. you can see come good examples near the bottom of the syslog from about 6:15pm to 6:45pm. cybertron-diagnostics-20210116-1858.zip
  9. TexasUnraid's post from July 4th has an updated script that handles spaces. I don't recall if I altered the script after that, but it was my starting point and working well as far as I can tell. I have NOT gotten shadow copy/preview versions working yet though.