Jump to content

Profezor

Members
  • Posts

    155
  • Joined

  • Last visited

Posts posted by Profezor

  1. On 2/1/2024 at 12:23 PM, JorgeB said:

    If you have already replaced the cables (including power) and the devices are still not detected in the BIOS it suggests a device or board problem.

    OK here is a bit more info.

     

    I added the Disk Location plugin.

     

    The two 16 TB Seagate drives (one is data and one is the parity)  in the Not Found Section passed the SMART test, so they have power and they both have new SATA cables as well. However, they both don''t show up in the array (or as unassigned drives).

     

    Any ideas on how to get them to appear? This is last issue from rebuilding. What I am I missing?

     

    Thanks in advance.

    IMG_7915.HEIC

  2. On 1/28/2024 at 6:44 PM, Profezor said:

    I will check and get back to you. But at least 3 of 5 were visible after I switched cables, but now I just see 2.

    No they don't show up in the Bios either, I just see the 2 drives plus the 2 cache drives. It must be a power connection or bios setting or?

  3. On 1/23/2024 at 6:16 PM, JorgeB said:

    Please don't make multiple posts about the same thing, hidden the other one.

     

    There are ATA errors with multiple devices, check/replace cables

     

    Jan 23 07:01:24 Galaxy kernel: ata5: SATA link down (SStatus 0 SControl 310)
    Jan 23 07:01:24 Galaxy kernel: ata5: limiting SATA link speed to 1.5 Gbps
    Jan 23 07:01:24 Galaxy kernel: ata8: COMRESET failed (errno=-16)
    Jan 23 07:01:24 Galaxy kernel: ata5: found unknown device (class 0)
    Jan 23 07:01:24 Galaxy kernel: ata5: SATA link down (SStatus 0 SControl 310)
    Jan 23 07:01:24 Galaxy kernel: ata5: limiting SATA link speed to 1.5 Gbps
    Jan 23 07:01:24 Galaxy kernel: ata5: found unknown device (class 0)
    Jan 23 07:01:24 Galaxy kernel: ata5: SATA link down (SStatus 0 SControl 310)
    Jan 23 07:01:24 Galaxy kernel: ata8: SATA link down (SStatus 0 SControl 3F0)
    Jan 23 07:01:24 Galaxy kernel: ata8.00: disable device
    Jan 23 07:01:24 Galaxy kernel: sd 8:0:0:0: rejecting I/O to offline device

     

    Ok, I have made progress.

    i have all my dockers back.

     

    i also changed all my Sata cables with brand new ones, But now the system can’t see three drives. Could it be not the sata cables but the power cables? Or…?Diagnostic attached. 

    galaxy-diagnostics-20240128-1820.zip

  4. any advice  with this. one?

     

    Given, I am not using my backup usb as it would not boot, I am using a fresh unraid install. So it doesn’t have my old containers.

     

    Do you think I could copy the docker templates from the unbootable usb? If so where are the templates and associated files located?

     

    if it Docker.man and docker folder within the plug-in folder? Or should I copy over more?

  5. 2 hours ago, trurl said:

    The configuration isn't in the appdata. Like all other settings in your Unraid webUI, the templates for reinstalling your containers is on the boot flash in the config folder.

     

    https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file

    https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications

    Given, I am not using my backup usb as it would not boot, I am using a fresh unraid install. So it doesn’t have my old containers.

     

    Do you think I could copy the docker templates from the unbootable usb? If so where are the templates and associated files located?

     

    if it Docker.man and docker folder within the plug-in folder? Or should I copy over more?

  6. 2 hours ago, JorgeB said:

    Please don't make multiple posts about the same thing, hidden the other one.

     

    There are ATA errors with multiple devices, check/replace cables

     

    Jan 23 07:01:24 Galaxy kernel: ata5: SATA link down (SStatus 0 SControl 310)
    Jan 23 07:01:24 Galaxy kernel: ata5: limiting SATA link speed to 1.5 Gbps
    Jan 23 07:01:24 Galaxy kernel: ata8: COMRESET failed (errno=-16)
    Jan 23 07:01:24 Galaxy kernel: ata5: found unknown device (class 0)
    Jan 23 07:01:24 Galaxy kernel: ata5: SATA link down (SStatus 0 SControl 310)
    Jan 23 07:01:24 Galaxy kernel: ata5: limiting SATA link speed to 1.5 Gbps
    Jan 23 07:01:24 Galaxy kernel: ata5: found unknown device (class 0)
    Jan 23 07:01:24 Galaxy kernel: ata5: SATA link down (SStatus 0 SControl 310)
    Jan 23 07:01:24 Galaxy kernel: ata8: SATA link down (SStatus 0 SControl 3F0)
    Jan 23 07:01:24 Galaxy kernel: ata8.00: disable device
    Jan 23 07:01:24 Galaxy kernel: sd 8:0:0:0: rejecting I/O to offline device

     


    thanks. Cables.

    so I should probably replace all the SATA cables to be sure?

     


    I wasn’t hiding anything. I thought that the two forums would reach different people who would have different perspectives.

     

  7. 17 hours ago, JorgeB said:

    Try using a new flash drive, create it using the USB tool, no key needed, and test if it boots, if yes you can then recreate the current one.

    Morning!

     

    I make a live linux to test the. system. It booted immediately. SO it seems my boot usb files are corrupted.

    If I make a clean boot usb, and boot with that - WILL I LOOSE ALL MY DATA AND DOCKERS ETC? OR will I be ok and get back to normal? 

     

    Thanks

  8. 1 hour ago, JorgeB said:

    Just changing the folder name is enough, but you can also recreate the flash drive using the USB tool, default is UEFI boot enabled.

    But as u see that is not working unfortunately 

    what would happen if I created a new usb, not a backups?
     

    would have still have access to my drives and data?

  9. On 1/14/2024 at 12:48 PM, JorgeB said:

    It appears to be booting to a UEFI shell, make sure UEFI boot is enabled in Unraid, if there's a EFI- folder on the flash drive rename it to EFI.

    Ok, I removed the “-“ and double check the bios end up it still goes to the shell/script. Any other suggestions? How do I unable uefi in unraid other than changing the folder?

    IMG_7757.jpeg

    IMG_7778.jpeg

  10. I changed my motherboard and chassis. I took the drives and moved to the new chassis.

     

    Can't get it to boot.

     

    I am using a copy of the last boot disk saved here at Unraid.net

     

    Can you see anything in the picture? This is. where the booting stops

    What would happen if I tried to boot. from a new boot usb instead of my own?

     

    Really need my data and stuff.

     

     

    IMG_7757.HEIC

  11. This is output of my digikam log.

    Additional, my GUI does connect. It shows a bank page with "Cannot GET /"

     

    I am sure it is an easy solution, but need help to solve.

     

    I am running 6.12.3

     

    Thanks in advance.

     

    __

     

     

    2023/09/18 11:20:29 [warn] 221#221: could not build optimal types_hash, you should increase either types_hash_max_size: 1024 or types_hash_bucket_size: 64; ignoring types_hash_bucket_size
    _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.

    Xvnc KasmVNC 1.2.0 - built Sep 15 2023 16:22:02
    Copyright (C) 1999-2018 KasmVNC Team and many others (see README.me)
    See http://kasmweb.com for information on KasmVNC.
    Underlying X server release 12014000, The X.Org Foundation

    [migrations] started
    [migrations] no migrations found
    ───────────────────────────────────────

          ██╗     ███████╗██╗ ██████╗ 
          ██║     ██╔════╝██║██╔═══██╗
          ██║     ███████╗██║██║   ██║
          ██║     ╚════██║██║██║   ██║
          ███████╗███████║██║╚██████╔╝
          ╚══════╝╚══════╝╚═╝ ╚═════╝ 

       Brought to you by linuxserver.io
    ───────────────────────────────────────

    To support LSIO projects visit:
    https://www.linuxserver.io/donate/

    ───────────────────────────────────────
    GID/UID
    ───────────────────────────────────────

    User UID:    99
    User GID:    100
    ───────────────────────────────────────

    [custom-init] No custom files found, skipping...
    [ls.io-init] done.
    Obt-Message: Xinerama extension is not present on the server
     

×
×
  • Create New...