Civic1201

Members
  • Posts

    167
  • Joined

  • Last visited

Community Answers

  1. Civic1201's post in after upgrading to 6.12.9 -> Error: Backup corrupted was marked as the answer   
    I found the solution here:
     
     
    Backup is working now.
  2. Civic1201's post in cleaning up docker - old files/images was marked as the answer   
    I found the easy solution by clicking advanced view on docker page and deleted the old images. Was just to lazy to think about that option.
  3. Civic1201's post in USB drive failed after reboot - no shutdown possible was marked as the answer   
    System is running again  I was able to reflash my last local image to the same stick and done.
    Lesson(s) learned:
    - whenever you tweak your Autofan settings disable Flash-backup as all saved setting from Autofan will result in a Flash backup.
    - when changing a lot of settings this will create a loop (at least for me) and the flash drive will be not accessable anymore
    - after all settings saved reenable flash-backup und run a backup
    - never forget manual updates...
  4. Civic1201's post in AER: Corrected error received - which option to solve it? was marked as the answer   
    Problem solved!
    For testing I changed the Western Digizal SSD to an ADATA 240GB and waited for 24 hours -> no errors at all.
    Switched to a brand new 970 Evo Plus and testet again -> 0 erros  and no comments needed anymore
    So I am done with Western Digital, next step is to replace the 2 WD RED in my first server.
  5. Civic1201's post in can´t replace cache drive -> cache - too many missing/wrong devices was marked as the answer   
    Stupid me....
    I found the solutiion here
     
  6. Civic1201's post in unable to access GUI, SSH access is working was marked as the answer   
    Ok I was able to flash the backup to the thumb drive and system is back and running. Thank you.
  7. Civic1201's post in corrupt USB drive after updating plugins was marked as the answer   
    Problem solved
    USB drive was not readable anymore so I used the backup from UnraidConnect and flashed it to the same drive -> server is running again!
    Another drive is on the way if the old one has problems again.
    So guys never forget you backups
  8. Civic1201's post in changed to ipvlan and still -> Error: macvlan call traces found was marked as the answer   
    That was an easy fix
    Thank you!
  9. Civic1201's post in pcieport: corrected error received - fix? was marked as the answer   
    Ok I found the final fix here and it´s working:
     
     
    append initrd=/bzroot pci=nommconfto -> did not solve the problem for me.