Jump to content

johnnie.black

Members
  • Content Count

    18015
  • Joined

  • Last visited

  • Days Won

    215

Everything posted by johnnie.black

  1. I understand by this you're using s SAS1 expander with dual link, if so you'll need to account for protocol overhead and 8b/10b encoding, of the 2400MB/s theoretical max you'll get around 2200MB/s usable, so with 24 drives around 92MB/s per drive.
  2. Just for completion problem would be using no trailing slash on source, that will create an extra folder.
  3. Either way works in this case. /mnt/disk2 or /mnt/disk2/ no extra folder will be created.
  4. If you're using user scrips there's nothing needed to do.
  5. Disk disabled but assigned, according to the syslog Unraid formatted the emulated disk successfully, but was still giving an invalid partition error, since the partition layout is created by Unraid it's likely a bug.
  6. You're having problems with disk1: Jul 22 18:08:56 Unraid kernel: md: disk1 read error, sector=2286221472 Jul 22 18:08:56 Unraid kernel: md: disk1 read error, sector=2286221480 Jul 22 18:08:56 Unraid kernel: md: disk1 read error, sector=2286221488 Jul 22 18:08:56 Unraid kernel: md: disk1 read error, sector=2286221496 Looks more like a connection problem, replace cables.
  7. Though it's unusual for a disk to be formatted in that state, it does look like a bug.
  8. Using this option will not overwrite parity, though the GUI don't reflect that, it shows the warning with or without it checked.
  9. You can format and restore data, SSD should be fine, you could have a RAM problem, since checksum errors are most times caused by a flipped bit in RAM.
  10. That's normal, what's important is that there were no uncorrectable errors, all data on COW shares is now fine and correctly mirrored, any data on NOCOW shares can still be corrupt, like mentioned in the link, no way to check or correct it since it's not checksummed. You should also reset current stats and use a script to monitor for the future.
  11. They are. Depends on much data and how fast cache is, since you used -B you can check progress with: btrfs scrub status /mnt/cache And you can continue to use the cache normally, with reduced performance
  12. The warning mentions it will deleted data at array start, and that's when it does it, it wipes the previous filesystem, the superblock.
  13. There's a checksum error on the metadata, if there's important data you should be able to recover using one of these options, then format it.
  14. You should always post the complete diagnostics but based on that your docker image is corrupt, delete and re-create.
  15. Make sure bios backup function is disabled and remove HPA from disk4, other disks also have HPA enable but only remove from disk4 for now.
  16. Docker image is likely corrupt, so likely will any more data using NOCOW shares, rest should be fixable with a scrub, more info here.
  17. You get the blue icon after a new config, but without the "data on this device will be deleted" warning, when a cache device gets a blue icon and the warning, data will be deleted.
  18. If cache is btrfs, even if single device, you can do an online replacement: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480419
  19. Check filesystem on cache device: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
  20. That is just the SMART report, diags are in Tools -> Diagnostics.
  21. Dual parity should be OK, depending on the number of data disks, encryption will have a much higher performance impact, since that CPU doesn't support AES instructions.
  22. So this rules out 6.7.0 as your problem.
  23. Well if it was blue it wasn't being detected as the previous device, buts as a new device, you should also have seen a warning similar to "any data on this device will be deleted", I believe there's not much you can do now since the superblock was likely destroyed, you can try these recovery options but without a valid superblock none will work.
  24. USB can change the ID of a device, and Unraid would consider that a new device, did you get a missing device when changing from USB?