Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,662

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Yep, that does it: ndk_sh B t u v w x y z aa /dev/sdt: 434.79 MB/s /dev/sdu: 434.79 MB/s /dev/sdv: 433.82 MB/s /dev/sdw: 435.06 MB/s /dev/sdx: 434.84 MB/s /dev/sdy: 434.54 MB/s /dev/sdz: 434.61 MB/s /dev/sdaa: 434.80 MB/s Total = 3477.25 MB/s And results were more consistent with multiple runs.
  2. JorgeB
    Unfortunately parity can't help with filesystem corruption, it would rebuild the disks as they are now, but it's not normal to have severe corruption in two disks at the same time, you might have a hardware issue, like bad RAM.
  3. JorgeB
    There are some known issues with v6.9.2 and spin down, you can try downgrading to v6.9.1 and see if it helps.
  4. JorgeB
    Usually any expander port can be used as in or out, it just depends on what they are connected to, it's like that with the older HP 6G expander.
  5. JorgeB
    Those diags were not created by an unclean shutdown, next time one happens check the logs folder for the diags with matching time.
  6. JorgeB
    Run an extended SMART test.
  7. JorgeB
    Are those diags after a crash? Don't see anything out of the ordinary logged.
  8. JorgeB
    Yes, just stop the array, unassign parity2, start array, after that it can be re-used as a replacement.
  9. JorgeB
    You can get the data from the remainig good data drives, no way to get the data from the damaged drives with so many missing.
  10. JorgeB
    Use -L.
  11. JorgeB
    Should work fine.
  12. JorgeB
    https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Fix filesystem on both disks, run it without -n or nothing will be done.
  13. JorgeB
    If you started the array with a disk unassigned that disk will no longer be 100% in sync with parity, just mounting and unmounting the disks is enough for that, so you need to rebuild (or do a new config to re-enable it but it will require a correcting parity check, and that takes as long).
  14. JorgeB
    If you have any VM vdisks on that disk they will be sparse, sparse means that if you for example select 500G for the vdisk size but the OS only uses 50G, it will only occupy 50G on the disk, it can then grow as needed, if it gets copied/moved to another disk without using the flag it will occupy 500G on dest, instead of just 50G. rsync flag for this is: --sparse
  15. JorgeB
    You're welcome, you can take a look here for some recommended models:
  16. JorgeB
    Problem with the onboard SATA controller: Jun 1 14:00:59 SRVUNR1 kernel: ahci 0000:03:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000f address=0xe7d60000 flags=0x0000] Unfortunately quite common with some Ryzen boards, BIOS update might help, or using a newer Unraid release when available due to the newer kernel, failing that best bet is to use an add-on controller (or a different model board).
  17. JorgeB
    You can create multiple single device "pools", some limitations though, all existing data in a specific share using those pools would still be visible when browsing that share but you'd need to work with disk shares to copy data to all the pools except the one set to use that share, currently any share only can be configured to use one pool.
  18. JorgeB
    Yes, you can also use the existing one, just need a second adapter and more cables.
  19. JorgeB
    Click on the share then "compute" under size, it will show usage by disk/pool. This works, with the VM off.
  20. JorgeB
    Formatting is never part of a rebuild, and since the emulated disk is mounting correctly you just need to re-enable the drive, but if the replacement controller is going to arrive soon best to wait for it before doing it.
  21. JorgeB
    Shares with cache=no aren't moved to the array, only cache=yes. Yes, set the share(s) to cache=prefer and run the mover, the VMs and VM service should be disable, mover won't move open files.
  22. JorgeB
    Array can only have 30 devices max (28 data + 2 parity), but you can have additonal multiple pools and unassigned devices, hence unlimited devices, just not unlimited array devices.
  23. JorgeB
    Ahh, good catch, maybe why everything looks normal there.
  24. JorgeB
    https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601 Though that looks more like a hardware issue, so possibly nothing will be logged.
  25. JorgeB
    Yes. Which one? That's it, SFF-8088 to SFF-8088. Any one will work, they are transparent to the OS. It's not powered, looks like this: In that case I had a second PSU to power the disks and the expander on the second chassis.
×
×
  • Create New...