stev067

Members
  • Posts

    85
  • Joined

  • Last visited

Recent Profile Visitors

343 profile views

stev067's Achievements

Rookie

Rookie (2/14)

24

Reputation

  1. Dang, ok thanks. I will just try to rebuild same disk and call it a fluke. Sucks to rebuild 14TB disk though.
  2. Hoping someone can take a look at my logs and help me determine what happened and what I should do. Last night, one of my disks got taken offline while I was moving a batch of files from it to my cache drive, and I think it was saying read errors. From what I can tell, the SMART details don't look much different from the other disks, and it says it passes. My array is connected through an HBA card and SAS expander card, so it could possibly have been a hiccup in either of those too. My array is like 6 months old, so I'm hoping this disk isn't actually toast. Thanks I appreciate any help. haven-diagnostics-20211008-0731.zip
  3. I was going to say check out my build in my signature, but I guess signatures are only visible when viewing the forum on desktop. Here's where I'm at currently: Unraid Pro 6.10.0-rc1 Array: 10x 14TB Seagate Ironwolf Pro (2 parity) Case: Fractal Define 7 XL Motherboard: Asus Prime X570 Pro CPU: Ryzen 9 5950x Memory: Kingston 64GB 3200MHz DDR4 ECC Cache: Samsung 980 Pro 2TB NVMe and 980 Pro 500GB NVMe HBA Card: LSI 9211-8i (IT mode) (cooled with Noctua 40mm) SAS Expander: Intel RES2CV240 (cooled with Noctua 40mm) Network Card: Intel X550-T1 10Gbps PSU: EVGA 850 GR CPU Cooler: Corsair H115i RGB Pro XT UPS: APC 650W Hotswap Bay: Icy Dock flexiDOCK MB795SP-B
  4. Did anyone have to make any changes to their secondary / 10Gb NIC? On this update, I'm suddenly unable to interact with SMB shares over my 10Gb NIC, p2p from my W10 pc. I can ping back and forth using those IP's, and I can still connect over the br0 1Gb connection, just not my fast one. It will prompt me for credentials, and appears to connect, but then explorer will just sit/timeout when I start navigating my shares. I've rolled back for now.
  5. TY let me know if you need any standoffs because I have way more than I could ever use.
  6. I drilled 3 holes in the floor and used brass standoffs to mount it. I'm pretty happy with how it turned out.
  7. Small update in my build. I upgraded one of my cache drives from 500GB to 2TB. Still Samsung 980 Pro NVMe. This is the cache drive I use for moving files between this machine and my main PC. It was big enough for that, but then I started to use Handbrake to re-encode a large video collection, and using this cache drive as the platform for that.
  8. https://www.amazon.com/gp/product/B07DXRNYNX/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
  9. I'm pulling my hair out over this one. Since updating to the new RC last night, I am no longer able to access my shares from my main PC, which I was previously doing via a secondary, 10Gb NIC on eth1. I've tried re-making the user, clearing out all the old shares and their registry entries. Rebooted both machines a dozen times. It lets me connect to the share, but when I go to navigate the folders, it just spins and times out. When I connect via the 1Gb connection on eth0, all is fine. But I really need that 10Gb speed between these machines. Any ideas what I can check? I really didn't change anything else aside from the OS update. Thanks.
  10. I'm also interested, because my curiosity may take me to rack-mounting things at some point. You may get more/better answers by making a new thread, because I don't know if people will really see your question here.
  11. I went ahead and rebooted the system, with the raid enclosure turned off and unplugged from the system, and now the errors have stopped, which leads me to believe it could be the culprit. I'm going to pull each disk and do a chkdsk on my windows PC.
  12. Did you ever figure this out? I'm having the same problem.
  13. @Symon I saw you posted the same issue in Jan-2019, but I didn't see a resolution from you. The other user on that thread mentioned not mounting a drive to be passed through, but my passed through drive is not mounted.
  14. Hey guys, Today I noticed that my system log is full of the same repeating error(s), going back as far as the full size of the log, which appears to be 3 days. I have not noticed my system behaving badly in any way, but my syslog is useless if I can't shut this error up. I have tried researching this error without much luck. Please if anyone can point me in the right direction, I'd really appreciate it. I have 2 unassigned drives, both NTFS. One is a USB raid-50 enclosure with 8 disks. I'm able to mount it and RW with it. This error persists even when that drive is powered off and unplugged from the system. My other drive is a HDD passed through to a Windows 10 VM, where I formatted it within the VM. Those are the only 2 NTFS drives in my system. I wish I knew when this started, because that would help me narrow it down, but I have no idea. Thanks Jul 16 13:50:49 Haven ntfs-3g[7775]: ntfs_mst_post_read_fixup_warn: magic: 0x3a00b303 size: 4096 usa_ofs: 13360 usa_count: 13114: Invalid argument Jul 16 13:50:49 Haven ntfs-3g[7775]: Actual VCN (0x153024243000e20) of index buffer is different from expected VCN (0x0) in inode 0x3aaee. haven-diagnostics-20210716-1142.zip