• Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

RealActorRob's Achievements


Apprentice (3/14)



  1. This is in settings /mnt/user/BlackTowerMain/storj,/mnt/user/storjnode2 (second entry I just added) for folders, and *.db,*.v1,*.sj1,*.log,*.tmp,.storj*,.Recycle.Bin in Custom files. Storj nodes update so much (and are self healing probably) but I was still getting log lines such as BLAKE3 hash key mismatch, /mnt/disk3/BlackTowerMain/storj/storage/blobs/pmw6tvzmf2jv6giyybmmvl4o2ahqlaldsaeha4yx74n5aaaaaaaa/2q/ouw7yyys2wfigjx2vfmmns4if2naa77erhiudde3p6y2apqhaa.sj1 is corrupted (and LOTS of them!) Or am I missing some syntax/formatting? Basically, I really don't care about corruption in these directories at all. It's all storj slices so I doubt it'd even matter. The other nodes, I presume, would just heal it and I'd get a CRC/parity error etc.
  2. I have a 2230 Kioxia with no heatsink on a PCIe card that's at 58C. No heatsink. I figure that's a reasonable temp. I set the warnings to 140/145F. 2600MB/s in an R720xd if anyone is interested in the future. Also it isn't a flat line in Diskspeed and isn't being used just yet, so there's a datapoint. 2728mb high and 2579 low so something like 8% variance?
  3. Had a parity disk disable due a read error (forget the exact problem) but subsequent preclears are going fine. One completed, another almost completed, plan to read 3. Speaking of, is there a way to test R/W a particular sector say, 50 times? Thoughts on using it? Probably use it as a Chia drive but might press it back into service if it passes a bunch. Also: I've got a drive pushing 93,000 power on hours but only 110 start/stop counts. It's at a nice 35C now. WD20EARS.
  4. Ugh. I tried it several times this way with a few variations thrown in and even used 'defaults write TMShowUnsupportedNetworkVolumes 1' Nada.
  5. All I had to do was click the red 'X' by preclear on the Main tab and FORMAT is now orange. Not using it just yet, but looks good to go if/when needed.
  6. I did 'Fix Preclear' on that tools page, and I'm running another preclear but 99.99% sure it wasn't interrupted last time. I also cleared all the preclear reports on that drive, but I suppose those are stored in appdata and not on the precleared drive. Hopefully a complete preclear will fix it, and why not run another one LOL.
  7. Interesting, this is two disks: The second one has no filsesystem and neither does the top one. But one has a mount option greyed, and the other doesn't. All I've done is preclears so I wonder what I've done differently to the top one....confusing. Destructive mode is obv. enabled. After formatting second disk: So it's like sdi is in a limbo where it doesn't have a filesystem but also I never formatted it and the format button isn't avail.
  8. Ok, what am I missing? 'Mount' is greyed out. All I want to do it mount/automount the unassigned disk. Not even share it. Just want to use it to play around with Chia mining. One thought: do I have to restart the array to get it to work?
  9. Will be doing another one if the drive passes another preclear or two and the extended SMART test passes. I have a WD Red CMR NAS on order to replace it. Edit: Seagate Ironwolf NAS was a little cheaper and a little higher rated, review-wise.
  10. I'm doing a preclear at the same time as an extended test, which should hammer this drive pretty well.
  11. It wasn't, and I turned FTP off. It had no users enabled and firewall wasn't opened so it was pretty secure, but, one less thing. Thought I'd turned off FTP already...might have been doing something with it and forgot to re-disable. I also turned off the mover log, since mover isn't having issues ATM to reduce log file size.
  12. Found this on the device page under SMART log: ATA Error Count: 1 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1 occurred at disk power-on lifetime: 54381 hours (2265 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 10 51 08 70 c9 a5 02 Error: IDNF Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 2f 00 01 10 00 00 00 00 3d+07:43:39.996 READ LOG EXT 60 20 08 e8 93 6d 40 00 3d+07:43:39.996 READ FPDMA QUEUED 60 00 00 e8 8f 6d 40 00 3d+07:43:39.996 READ FPDMA QUEUED 60 b0 00 38 8c 6d 40 00 3d+07:43:39.991 READ FPDMA QUEUED 60 00 00 38 88 6d 40 00 3d+07:43:39.986 READ FPDMA QUEUED
  13. It's from Automounter, which helps keep SMB shares from dropping and/or it's a discovery of services from same. It's helped with my SMB issues doing backups on Mac OS X Mojave.
  14. It's a 4TB I've run other tests on and all turned out fine. I replaced my working 3TB Parity 2 drive for future upgrades. So, this drive got x'd during a rebuild of parity onto it. Drive is in a disk tray on a server, so I doubt this is a 'cable' issue. Preclear went normally. Rebuild had 1 read errors but the SMART doesn't show ANY read errors or fails. running another preclear now and an extended test now. A short time ago, 800 hrs, this also passed an extended. Diags attached. Thoughts? To sum: other than the 1 read error on the parity rebuild, I don't see ANY indication of drive problems. I'm sure this is an ex-data center drive, noting the power on hours vs. power cycle count.