Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,783

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Now try formatting again with Unraid and post new fdisk output if it fails.
  2. JorgeB
    type wipefs -a /dev/sdf1 then wipefs -a /dev/sdf and repost fdisk output
  3. JorgeB
    Nothing obvious, please post output of fdisk -l /dev/sdX
  4. JorgeB
    There's constant crashing on the log, including references to the Unraid driver, there's another user that recently had similar issues with the same HP Microserver Gen8, including some data loss due to fs corruption with both btrfs and xfs devices: For now I would recommend going back to v6.9.2, looks like these serves don't get along with the newer Kernel, unclear for now if all Microserver gen8 will have the same issues or just a specific CPU/BIOS combo.
  5. JorgeB
    If it works yes, at least it's much newer, and cache devices should be automatically assigned, download the 6.9.2 zip and extract only the bz* files overwriting existing ones.
  6. JorgeB
    Realtek driver support with Linux has always been hit and miss, look at the post below, it might also help you:
  7. JorgeB
    Settings -> FTP Server
  8. JorgeB
    That's because you downgraded to v6.8, doesn't v6.9 work? If you want to remain on v6.8 just re-assigned them as they were.
  9. JorgeB
    No, the solution is this, though sorry I linked another post that linked to this one: https://forums.unraid.net/topic/119502-bzimage-checksum-error/?do=findComment&comment=1120488
  10. JorgeB
    Stock Unraid doesn't report CPU/MB temps, you can try reporting the issue in the appropriate support thread for the plugin you're using.
  11. JorgeB
    Yes, if the config is the backup, and it's the complete config folder, not file.
  12. JorgeB
    If you want to go back to v6.9.2 unzip that to the flash drive then restore only the config folder from the backup.
  13. JorgeB
    You could revert by just overwriting the bz* files, if you overwrote everything most settings will be gone, do you have a backup of the flash drive? If not see here: https://wiki.unraid.net/Manual/Changing_The_Flash_Device#What_to_do_if_you_have_no_backup_and_do_not_know_your_disk_assignments
  14. JorgeB
    If it's working let it be.
  15. JorgeB
    It appears that there are lots os USB related issues, make sure the flash is in a USB 2.0 port and/or try a different one (in a different controller).
  16. JorgeB
    Do you have a monitor/ipmi? Where did the boot stopped?
  17. JorgeB
    You can move the settings, or at least most of them, some setting might be causing the issue, so try moving a few at a time, and move network.cfg.
  18. JorgeB
    Try the below, it usually helps mostly with Dell servers and bzroot checksum error, but it won't hurt to try:
  19. JorgeB
    Shfs is crashing when the mover runs: May 18 03:40:05 Apollo kernel: shfs[8826]: segfault at 0 ip 000000000040277f sp 000014f2d44518f0 error 4 in shfs[402000+b000] Unfortunately can't tell why it's crashing, make sure the files being moved and not being manipulated by other apps/dockers, that is known to sometimes cause issues
  20. JorgeB
    So it's working now? Only thing I find about the NICs in the log is this: May 19 02:57:49 Tower kernel: pci 0000:05:00.0: invalid VPD tag 0xff (size 0) at offset 0; assume missing optional EEPROM May 19 02:57:49 Tower kernel: pci 0000:08:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM
  21. JorgeB
    Nothing obvious, make sure you don't have multiple browser windows open on the GUI, also try booting in safe mode.
  22. JorgeB
    Unlikely that the update is related, and basically same issue persisting after downgrading confirms that, check/replace/swap cables on disk1, you can also look at the LSI BIOS, if it's not detected there it also won't be in Unraid.
  23. JorgeB
    Setup the syslog server and post that after a crash together with the diagnostics.
  24. JorgeB
    If you never set a password it should be asking to set one up: If you don't see this do the recovery password procedure and you should see that at next boot.
  25. JorgeB
    Please post the diagnostics after a failed attempt.
×
×
  • Create New...