Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,416

  • Joined

  • Last visited

  • Days Won

    706

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    First few GBs of any transfer are cached to RAM, IIRC 20% free RAM by default, so initial speed is much faster, up to line speed, after that you are limited by the actual device writing speed.
  2. JorgeB
    Google IPMI and how to use it, there's nothing you can do with a keyboard/mouse that can't be done with IPMI.
  3. JorgeB
    Don't know why but it's still renaming eth0 to eth1, leaving you without eth0 which is needed, see if it's the same with an older release, like 6.7.3, delete network.cfg before doing it.
  4. JorgeB
    For some reason NIC was renamed to eth1, please post a screenshot/photo of Interface Rules (Settings -> Network Settings) Since you don't have LAN you can boot with GUI mode.
  5. JorgeB
    Did you miss my post or is your signature out of date?
  6. JorgeB
    Only took a quick look but everything looks normal, though there are a lot of nerdpack tools installed, make sure you need them all.
  7. JorgeB
    Apr 9 22:30:13 Tower kernel: XFS (md1): Metadata corruption detected at xfs_buf_ioend+0x4c/0x95 [xfs], xfs_inode block 0x7724be98 xfs_inode_buf_verify Apr 9 22:30:13 Tower kernel: XFS (md1): Unmount and run xfs_repair md#=disk#
  8. JorgeB
    First check which one is 1 and 2 by listing it: sas2flash –c 1 –list and/or sas2flash –c 2 –list then add -c # to the erase command
  9. JorgeB
    There are still issues with the cache device, looks more like a connection issue, try replacing both cables, it can also be a compatibility issue with the controller. That might not explain the parity check pausing, but don't any other issues logged, so try again after fixing the cache issue.
  10. JorgeB
    Disk1 had a bunch of read errors, it looks like a disk problem, you can run an extended SMART test to confirm.
  11. JorgeB
    At the time the diags were saved there were writes going on to 10 different array disks, this can only be extremely slow since parity needs to be updated simultaneously for all 10, avoid writing to more than one array disk at a time.
  12. JorgeB
    https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480418
  13. JorgeB
    Also see this.
  14. JorgeB
    New config is needed at step 11, also no need to wipe previous disks/partitions, just setting them to an encrypted filesystem is enough, Unraid will offer to format it at next array start. If it's a single share on those disks you could rename it on all 3 disks and move it together, but it not be as simple as using Unbalance. See above.
  15. JorgeB
    It will keep them all, before re-enabling them just make sure both services are using the previous existing paths, settings -> docker and settings -> vm manager
  16. JorgeB
    No problem, and forgot the mention, the SMART error I was referring to is this one, lower in the log: Error: WP at LBA = 0xeef86878 = 4009257080 I don't remember seeing it before, and unlike for example UNC @ LBA which usually means bad sectors, I have no idea if this one is usually a disk problem or not.
  17. JorgeB
    No, but the SMART test passed, so disk is OK for now.
  18. JorgeB
    Cache pool looks good, only a quick glance but didn't notice any other issues.
  19. JorgeB
    If your signature is correct you have a board with IPMI, no need for keyboard/monitor.
  20. JorgeB
    Try with a different brand/model device if possible, some devices might have issues with a specific controller, I know for example that some 2.5" Seagate drives have some with Asmedia controllers, same for some HGST 2.5" drives and LSI controllers.
  21. JorgeB
    Like mentioned perfectly fine to copy to disks shares from an outside source, like your desktop, enable them then and copy to \\tower\cache and \\tower\diskX
  22. JorgeB
    Yes, either copy everything you can from UD to the array (better after replacing the disable disk) or use ddrecue to clone it to a new disk then rebuild parity based on that, ddrescue is fairly simple to use, more info here. If the emulated disk is unmountable (and not fixable) same will happen if you rebuild to a new disk.
  23. JorgeB
    Superblock on the emulated disk is missing/corrupt, that suggest parity wasn't 100% valid. You can see if the actual disk mounts with UD, though since the disk appears to be failing it might be good to clone it with ddrescue first.
  24. JorgeB
    File is too big, even for Notepad ++, post the standard diags, so we can see if something is spamming the syslog.
  25. JorgeB
    It will, that's why you should have checked parity is already valid. Because the partitions are not setup the way Unraid requires them to be, like mentioned because you were using a RAID controller.
×
×
  • Create New...