• Posts

  • Joined

  • Last visited


  • Gender

dingy's Achievements


Newbie (1/14)



  1. Yeah, this is nutty. The older version of software shows EPC NOT being enabled. I've tried changing the EPC settings and received the same error "Failed to send EPC command to /dev/sg7". I will power-cycle the server (and clear the read error). The process that logs the error? Looks like it might be SMART related. The other drives log SMART at about the same time. The way I figure it - if it happens again, I'll replace the disk controller. I have until Feb 1 to send my replacement back, although since I'm seeing the same exact issue on different drives and different ports (but the same controller) the only thing left is the controller. Either that, or snag another VN0022.. The only other thing would be to install RC2 or backrev... ************************ UPDATE:: Yep. Nutty. Need beers nutty. Seems that my drive letters changed. Low current spinup has changed from Disabled to Ultra Low Enabled (FWIW - same settings as is on my VN0022 drives). EPC does not show as enabled. Guess I need to try setting the Low Current spinup, reboot and see what happens. It appears that although disabling EPC "didn't work", something did. Guess it is a feature, not a bug. UPDATE #2: Was able to disable Low Current Spinup. Rebooted and have verified that Low Current Spinup is disabled and EPC is not enabled. Time to wait and see what breaks. <EDIT> Shout-outs for the help. Thanks!
  2. Thanks. Already checked Seagate for new firmware - was a dead end ("not available"). I'll use the older version - thought I've give it a shot with the latest.
  3. My bad. Scheduler is for 3:30 AM on Sundays, weekly so the above is not scheduler. I haven't been able to determine what kicks off at 3AM. All dockers are on SSDs and don't talk to the rotating rust.
  4. Lastly - thinking it could be a firmware issues, so I looked on the Seagate website. There is no new firmware available. The only thing different between my VN0022 drives and the VN004 problem child is that the VN0022s are running SC61 FW whereas both VN004s (still have the old one in the system) are running SC60. The following was in today's disk log: Jan 9 12:08:37 Tower emhttpd: read SMART /dev/sdh Jan 9 12:08:56 Tower emhttpd: shcmd (26): echo 128 > /sys/block/sdh/queue/nr_requests Jan 9 12:08:59 Tower s3_sleep: included disks=sdb sdc sdd sde sdf sdh Jan 10 00:24:59 Tower emhttpd: spinning down /dev/sdh Jan 10 03:00:31 Tower kernel: sd 1:0:6:0: [sdh] tag#2660 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Jan 10 03:00:35 Tower kernel: sd 1:0:6:0: [sdh] tag#2740 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=19s Jan 10 03:00:35 Tower kernel: sd 1:0:6:0: [sdh] tag#2740 Sense Key : 0x2 [current] Jan 10 03:00:35 Tower kernel: sd 1:0:6:0: [sdh] tag#2740 ASC=0x4 ASCQ=0x0 Jan 10 03:00:35 Tower kernel: sd 1:0:6:0: [sdh] tag#2740 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 40 00 00 00 08 00 00 Jan 10 03:00:35 Tower kernel: blk_update_request: I/O error, dev sdh, sector 64 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jan 10 03:00:53 Tower emhttpd: read SMART /dev/sdh Jan 10 03:33:10 Tower emhttpd: spinning down /dev/sdh Jan 10 17:16:32 Tower emhttpd: read SMART /dev/sdh Jan 10 17:46:15 Tower emhttpd: spinning down /dev/sdh The 3AM time is interesting though, as this is the time (weekly) that data is transferred from the Cache...
  5. Downloaded SeaChest, followed instructions, and it didn't work too well. Note: this is using the current version of SeaChest; files end in "x86_64-redhat-linux" (from the Non-RAID directory). Is this correct? /dev/sg7 - ST8000VN004-2M2101 - WSD56WY4 - ATA Failed to send EPC command to /dev/sg7. EPC Feature set might not be supported. Or EPC Feature might already be in the desired state. Any suggestions? I figure I could continue to attempt a fix, return what I have and get another VN022 for a bit more $$$ or get get something a bit larger. Anyway - the info: ========================================================================================== SeaChest_Info - Seagate drive utilities - NVMe Enabled Copyright (c) 2014-2021 Seagate Technology LLC and/or its Affiliates, All Rights Reserved SeaChest_Info Version: 2.1.0-2_2_3 X86_64 Build Date: Jun 17 2021 Today: Mon Jan 10 17:16:13 2022 User: root ========================================================================================== /dev/sg7 - ST8000VN004-2M2101 - <edited> - ATA Model Number: ST8000VN004-2M2101 Serial Number: <edited> Firmware Revision: SC60 World Wide Name: 5000C500E34389D3 Drive Capacity (TB/TiB): 8.00/7.28 Temperature Data: Current Temperature (C): 23 Highest Temperature (C): 35 Lowest Temperature (C): 22 Power On Time: 11 days 3 hours Power On Hours: 267.00 MaxLBA: 15628053167 Native MaxLBA: Not Reported Logical Sector Size (B): 512 Physical Sector Size (B): 4096 Sector Alignment: 0 Rotation Rate (RPM): 7200 Form Factor: 3.5" Last DST information: Not supported Long Drive Self Test Time: Not Supported Interface speed: Max Speed (Gb/s): 6.0 Negotiated Speed (Gb/s): 6.0 Annualized Workload Rate (TB/yr): 1313.05 Total Bytes Read (TB): 24.01 Total Bytes Written (TB): 16.01 Encryption Support: Not Supported Cache Size (MiB): 256.00 Read Look-Ahead: Enabled Write Cache: Enabled Low Current Spinup: Disabled SMART Status: Unknown or Not Supported ATA Security Information: Supported Firmware Download Support: Full, Segmented, Deferred Specifications Supported: ACS-4 ACS-3 ACS-2 ATA8-ACS ATA/ATAPI-7 ATA/ATAPI-6 ATA/ATAPI-5 SATA 3.3 SATA 3.2 SATA 3.1 SATA 3.0 SATA 2.6 SATA 2.5 SATA II: Extensions SATA 1.0a ATA8-AST Features Supported: Sanitize SATA NCQ SATA Rebuild Assist SATA Software Settings Preservation [Enabled] SATA Device Initiated Power Management Power Management Security SMART [Enabled] 48bit Address PUIS GPL Streaming SMART Self-Test SMART Error Logging Write-Read-Verify DSN AMAC EPC [Enabled] Sense Data Reporting SCT Write Same SCT Error Recovery Control SCT Feature Control SCT Data Tables Host Logging Set Sector Configuration Adapter Information: Vendor ID: 1000h Product ID: 0072h Revision: 0003h
  6. Just found this topic and thanks for the info (and the afternoon's reading, of course)! Wish I would have found it sooner.... I'll perform the magic on my sole VN004 (problem child) after parity check completes. FWIW - I only receive a single! read error on it (been driving me nuts). FWIW - my other disks are VN0022s. I have had zero issues with them.
  7. I'm running Unraid 6.9.2. Except for a rebuild (a new case), Unraid has been running for years now. I can't tell you what version I started at without digging for the printed email from my license purchase. As to my version of MacOS? Well... the mini has been powered down for a while. I think it was running either 10.11 or 10.12. It is now running 10.15.
  8. Sounds kind of familiar. Hope this helps: I've had my old mac mini stored for a while. Finally had a chance to get it setup and updated (to Catalina), and... Time Machine didn't work. There have been two things that changed - MacOS and a few updates to Unraid. After working on this for a couple of days, I found that creating a new share and sharing it as yes/Time Machine worked great. I want to use my unassigned device, so that solution didn't work too well (if Santa is nice I might get another 8TB drive and be able to setup a real share). I got to thinking that this had to be something samba related. I read far too much regarding Samba and followed a few too many threads. The path I followed is that netatalk is bad (remember Apple's announcement of deprecating AFP?). I decided to leverage Samba defaults as much as possible and it worked. My Samba extras are below. Changes/new stuff is shown in red. If this is erroneous or requires changes, PLEASE say something I hope this helps whomever! GL:HF! #disable SMB1 for security reasons [global] min protocol = SMB2 [TimeMachine] ea support = Yes path = /mnt/disks/TimeMachine vfs objects = acl_xattr catia fruit streams_xattr valid users = joeuser write list = joeuser guest ok = no #new stuff fruit:nfs_aces=no inherit_permissions = yes # fruit:aapl = yes fruit:encoding = native fruit:time machine max size = 2 T #doing two things - ignoring anything with netatalk #also relying on samba defaults (might be a problem) #fruit:locking = netatalk #changed from netatalk fruit:metadata = stream #default value is file #fruit:resource = file fruit:time machine = yes fruit:advertise_fullsync = true durable handles = yes kernel oplocks = no kernel share modes = no posix locking = no inherit acls = yes