Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About coolspot

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. Typically means version control, a copy of the file is stored in the metadata and can be restored at will. It's a feature of BTRFS and most major OSes like Windows can support them (i.e. right click, choose previous versions, etc.) They're great for preventing ransomware because you can take snapshots frequently without incurring a lot of space with BTRFS and can roll back chances en masse very easily. Personally I like to see multiple arrays as well, because I'm going to be hitting the 30 drive limit soon. Going beyond 30 drives with only 2 parity drives isn't really safe, so might as well have multiple arrays/volumes. In the future, volumes could be amalgamated with something like glusterfs similar to what Synology does with Petaspace.
  2. You need to enable the XMP 2.0 profile in the bios to use 3000 mhz. 3000mhz isn't a "standard" speed, so it's configured via Extended Memory Profiles. Technically you paid for a 3000mhz stick, so it should be stable at 3000mhz, but if not, you can always just use the sub-stock speed of 2133 which is fine. I doubt you'll notice any performance difference in unRAID.
  3. I see you quoted my thread ... I had a similar issue last year, but it was due to corruption on a StarTech PCI 2.5" HDD/SSD hotswap slot I was using. I removed the slot, connected the drive directly to my motherboard, and no more corruption. I guess the StarTech adapter had poor QC ... I had two of them and both exhibited this issue after extended use.
  4. I'm looking to run two types of bonding over one interface - 802.3ad with my primary subnet and balance-rr on another subnet. However, I only have 2 NICs, so I like to layer on top balance-rr using a virtual NIC? Is this possible with unRAID - which configuration file should I edit to add a virtual NIC to use for bonding? Any ideas how this could be achieved? Thanks.
  5. Do you need to export the hashes to run a check? If not, does it just read each file and compare it to the extended metadata checksum?
  6. I just had the same error show up - I think you are correct ... it's a spin up / down error. Under certain conditions, unRAID will read a drive before it is ready and thus cause this error. According to the SCSI error code guide I found on Oracle's website, the following code in the logs: ASC=0x4 ASCQ=0x2 Logical Unit Not Ready, Becoming Ready Indicates that the drive is OK— it is in the process of spinning up, but it is not yet ready. https://docs.oracle.com/cd/E19105-01/storedge.6320/817-5918-10/817-5918-10.pdf I'm seeing the same error on my SuperMicro 847 chassis.
  7. This looks related to Same issue with a LSI HBA and LSI Expander...
  8. I'm having the same problem - actually lots of problems with a LSI 2308 HBA and a LSI expander ... there seems to be a lot of IO WAIT problems which manifests itself in different ways including interrupting a stream if a disk needs to spin up.
  9. I'm seeing this as well running the File Integrity Plugin - is there a way to raise it?
  10. I have a question - why does the "Build Up-To-Date" become green while the plug-in is still processing a drive? Basically it's only 20% of the way through processing a disk but "Build Up-To-Date" is already flagged as green? Also, the number of files processed also seems off. For example, the system says 97.9% processed, but the calculation doesn't seem ot make sense? Currently processing file 10284 of 14494 Is this correct? Lastly, why do renamed files create a new hash - shouldn't the old hash be maintined if a file is renamed? Thanks.
  11. The LSI 9207 does detect the drive as a SATA-SSD, does that mean it supports TRIM? If TRIM is not supported, can it be run manually via a schedule? Does that work or does it mean that even manual TRIM won't work on HBAs.
  12. I'm seeing this exact same error, but different sector on a few of my drives: Mar 12 17:22:28 merlin kernel: sd 10:0:3:0: [sdm] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Mar 12 17:22:28 merlin kernel: sd 10:0:3:0: [sdm] tag#0 CDB: opcode=0x28 28 00 82 52 40 27 00 00 08 00 Mar 12 17:22:28 merlin kernel: print_req_error: I/O error, dev sdm, sector 2186428455 In my case: [Sun Jun 23 13:05:35 2019] sd 1:0:28:0: [sdab] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 [Sun Jun 23 13:05:35 2019] sd 1:0:28:0: [sdab] tag#18 CDB: opcode=0x28 28 00 00 01 62 c0 00 02 00 00 [Sun Jun 23 13:05:35 2019] print_req_error: I/O error, dev sdab, sector 90816 I don't think it's a disk failure ... but rather something to do with SMART or controller communication with the drive. When I had the unassigned plugin installed I was seeing a lot more of these errors. I think it's more of a compatibility issue than hardware error. The error above is from a Crucial M500 running off a LSI 9207-8i on a BPN-SAS2-826EL2 backplane.
  13. Same here on a SuperMicro with an onboard LSI 2308 ports w/ hard drives and a LSI 9207-8i with the SSDs. They are connected to BPN-SAS2-846EL2 expanders (24 port and 12 port). When mover runs, system grinds to a halt.
  14. Same here, upgraded to 6.7.0 and mover now causes Plex to hang, I noticed in TOP the IO wait time is through the roof when mover runs. IO Wait pegs out at 75 - 90%! I have two LSI cards on a SuperMicro BPN-SAS2-846EL2 expander, each card is connected to 2 ports on the card so there should be plenty of bandwidth. One LSI card is built into the motherboard (running of CPU PCIe) and second card is running off the 8x slot on the motherboard. I don't recall this happening on my older Celeron machine, it was running 6.6.x. Looks like others are having the exact same issue and the symptoms are identical, so that is good...
  15. Hi all, I recently migrated my setup to a SuperMicro SC847 chassis and a repurposed SuperMicro X10SLF motherboard. I noticed in the logs, I'm getting a lot of messages like: Jun 21 09:31:27 nasserv kernel: hpet1: lost 7 rtc interrupts Jun 21 09:31:28 nasserv kernel: hpet1: lost 1 rtc interrupts Jun 21 09:31:28 nasserv kernel: hpet1: lost 2 rtc interrupts Jun 21 09:31:28 nasserv kernel: hpet1: lost 5 rtc interrupts Jun 21 09:31:28 nasserv kernel: hpet1: lost 13 rtc interrupts Jun 21 09:31:28 nasserv kernel: hpet1: lost 15 rtc interrupts Jun 21 09:31:28 nasserv kernel: hpet1: lost 9 rtc interrupts I saw in another post that disabling ACPI may fix this? Is that the best way to resolve these messages in the log?