Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,893

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    That can be on or off, if for VMs mostly.
  2. JorgeB
    Without parity, you were mentioning using a trial key, just assign the data disk(s), though note that it will invalidate parity if you then put it back in the original array.
  3. JorgeB
    Thanks, didn't check before, but I do see it when exploring the forum, jus not on the activity streams like before:
  4. JorgeB
    You must assign the disk to an array data slot.
  5. JorgeB
    Disable SSL and see if you can access it without it.
  6. JorgeB
    Not seeing the normal star icon for threads I've posted in, is it just me?
  7. JorgeB
    It's not logged as a disk problem and SMART looks OK, suggest swapping cables/slot between the two parity disks and see if the issue follows the disk or not.
  8. JorgeB
    Like mentioned that error is fatal, you need to re-format, if the fs doesn't mount now you can use btrsf restore to try and recover the data, option #2 here.
  9. JorgeB
    If you are using Firefox reboot first then use a different browser.
  10. JorgeB
    Unfortunately there's nothing relevant logged, this usually suggests a hardware problem, I also see that disk3 appears to be failing, you can confirm by running an extended SMART test, but that should not make the server crash.
  11. JorgeB

    Syslog full

    JorgeB replied to Zodis's topic in General Support

    OK, just wanted to make sure, some users think they can format a drive and restore the data with a disk rebuild.
  12. JorgeB
    You have SAS disks, either disable spin dow or install the SAS spin down plugin. As for the unclean shutdowns, not clear to me if you see an unclean shutdown after you shutdown or reboot the server or if the server is crashing and rebooting on its own.
  13. JorgeB
    # Generated settings: IFNAME[0]="br0" BRNAME[0]="br0" BRSTP[0]="no" BRFD[0]="0" BRNICS[0]="eth0" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="192.168.1.99" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.1.1" DNS_SERVER1="8.8.8.8" DNS_SERVER2="8.8.4.4" USE_DHCP6[0]="yes" DHCP6_KEEPRESOLV="no" SYSNICS="1" Might not work if you have more than one NIC.
  14. JorgeB
    Tools -> New config -> Keep all assignments -> Apply Then for the data disks click on each one and click on "Erase", then there will be an option to format them after first array start.
  15. JorgeB
    The permanent syslog doesn't come with the diags, you need to get the file from wherever you set it to save to.
  16. JorgeB
    Nope, and the issue occurred right after spin up, suggesting that is the problem. That's a good idea. It will rebuild the current emulated disk, including any data written to it after it got disabled, just make sure it's mounting and data looks correct before rebuilding on top.
  17. JorgeB
    Looks like the SATA SSD is also dropping offline, but can't see that in the diags, probably due to all the other errors. It can, you should try disabling it for now.
  18. JorgeB
    Agree.
  19. JorgeB
    Yep. Dec 1 22:53:03 Tower kernel: nvme nvme0: Abort status: 0x371 Dec 1 22:54:04 Tower kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1 Dec 1 22:54:04 Tower kernel: nvme nvme0: Removing after probe failure status: -19 Dec 1 22:55:04 Tower kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1 Dec 1 22:55:04 Tower kernel: nvme0n1: detected capacity change from 488397168 to 0 Device is dropping offline, see if the above helps, if it doesn't look for a BIOS update or try a different NVMe device if available.
  20. JorgeB
  21. JorgeB
    No btrfs filesystem detected on the old device, that suggests the device was wiped with wipefs, you can try this: btrfs-select-super -s 1 /dev/sdb1 Note: this won't work if the device was encrypted, if that was the case you'd first need to restore the LUKS headers, if you have a backup.
  22. JorgeB
    JMB controller is bound to vfio-pci, delete /boot/config/vfio-pci.cfg and reboot.
  23. JorgeB
    That error could be a SAS disk not spinning down, please post the diagnostics.
  24. JorgeB
    Try recreating the network settings, rename /boot/config/network.cfg to .bak and reboot, then reconfigure.
  25. JorgeB
    Yes, when the data recovery is finished just format the disk.
×
×
  • Create New...