Jump to content

JorgeB

Moderators
  • Posts

    67,453
  • Joined

  • Last visited

  • Days Won

    706

Everything posted by JorgeB

  1. Just going to ping @jbartlettso we can take a look at the calculations.
  2. If it's close to 0 after that appdata is using more space than you think, if not there's something else on cache.
  3. Move the appdata to the array and check the used space reported after that.
  4. Something is using it, Windows can also report wrong used space over SMB, move the data to the array and check again.
  5. du isn't reliable with btrfs, df (and the GUI) will show correct used space.
  6. Start by upgrading the LSI firmware to latest, since it's on an old one, if issues continue check/replace cables and/or try a new PSU if available.
  7. See here for some recovery options, try the "ro,notreelog,nologreplay" mount first, if that doesn't work btrfs restore is probably the best option.
  8. Looks more like a flash problem, reboot and if still the same run chkdsk on the flash then extract all the bz* files from the Unraid zip overwriting existing ones, then reboot again.
  9. Until you find and fix the problem don't run correcting parity checks, and don't rebuild any disk on top of the old one, either use a spare or re-enable with a new config instead (but any data written to the emulated disk, if any, will be lost).
  10. See the first couple of posts on the UD support thread: https://forums.unraid.net/topic/44104-unassigned-devices-managing-disk-drives-and-remote-shares-outside-of-the-unraid-array/
  11. Like suspected it's showing the wrong values: 241 Total_LBAs_Written ------ 100 253 000 - 16039330064 242 Total_LBAs_Read ------ 100 253 000 - 33785959168 Logical sector size is 512 bytes, total LBAs written is the raw number x the logical sector size, so total writes are currently 8.2TB, diskspeed is multiplying by the physical sector size (4096 bytes), so you need to divide by 8 to get correct values.
  12. And did you replace the cables? If yes disk is likely dead.
  13. Post diags after at least two parity checks with errors (without rebooting).
  14. Disk dropped offline, power down, check/replace cables and power back on, if the disk is detected post new diags (note: even if detected it will still be disabled).
  15. You can ignore that. As for the total reads/writes they seems excessive, I suspect diskspeed is misinterpreting the SMART data, please post the SMART report using the GUI.
  16. You first need to fix the problem, then reboot and redo the new config.
  17. You can add the 10GbE IP to your Windows hosts files (that's what I do) or connect by IP address and always use the 10GbE IP.
  18. Errors on multiple disks suggest a cable/power problem, recheck all cables and/or use a new PSU if available.
  19. This looks more like a kernel issue, likely gone on the next beta/rc.
×
×
  • Create New...