bar1

Members
  • Posts

    79
  • Joined

  • Last visited

Posts posted by bar1

  1. Hi, did anyone try to use xcp-ng?

    I am really struggling also with vmplayer and virtualbox

     

    if i take my existing ,working USB, i keep on getting 169.254 ip address....not sure what else to try

  2. Hi, sorry i am sure it's a very basic question but not sure i am understanding 100%.

    everywhere i check , people enable GPU passthough and use RDP to connect to the VM.

     

    my unraid currently isn't connected to anything, if i passthrough the GPU ,and if i connect a monitor will my VM output to the monitor?

    is it something i can set up?

    thanks ....Bar1

  3. Hi everyone, back from holiday and still have issues.

    should i just try to replace my flash drive?

    i run a few scans on it and it seems fine.....

     

    while i was on holiday my server got restarted a few times....and every time i had to reinstall the unassigned devices plugin , and run :

    /usr/local/sbin/emhttp &

    also the had to install rclone a few times again.

     

    no issues with Dynamix WireGuard, and Nerd Tools, and community plugins....

  4. 21 hours ago, itimpi said:

    Sounds as if you may have some sort of problem with your flash drives.    Your symptoms are consistent with it not being picked up in the later stages of the boot process, or it having file system corruption.  
     

    I would suggest plugging it into a PC/Mac and running a check on it.   Also, while you are at it if you do have not already done so make a backup in case you need to redo the USB stick for any reason.

    Flash drive seems ok, but let me also make a backup.

    I do have a problem with my hp server that sometimes the sata drives are not being read properly, but that should  be affect /usr/local/sbin/emhttp from starting up?

     

    I also attached my diagnostics.

     

    if i want to test another flash drive without moving the license?it should be ok to do, with the 30 days trail, i believe?

    bar1-unraid-diagnostics-20201129-1026.zip

  5. Hi everyone, this is the second time it happens i am getting concerned now.

    this is also a security issue because ssh port is defaulting back to 22 (after i set it to something else).

     

    my power tripped last night, all my plugins got deleted, had to start /usr/local/sbin/emhttp & manually, ssh defaulted to port 22...and still check what else...

     

    what can the issue be ?

     

    NerdPack is still there,,,,but not unassigned devices so my whole docker/vm environment isnt working

  6. Hi, having a lot of issues here with my 8TB drive.

    I currently removed it from the array and trying to troubleshoot it as a mounted drive.

     

    Drive only mounts as read only and if i try get files off it i often get an error.

    i can start a btrfs scrub (with or without -r)

    but when i check:

    Status:           aborted
    Duration:         0:00:00
    Total to scrub:   5.85TiB
    Rate:             0.00B/s
    Error summary:    no errors found

     

    btrfs check --repair /dev/sdd1
    enabling repair mode
    WARNING:

            Do not use --repair unless you are advised to do so by a developer
            or an experienced user, and then only after having accepted that no
            fsck can successfully repair all types of filesystem corruption. Eg.
            some software or hardware bugs can fatally damage a volume.
            The operation will start in 10 seconds.
            Use Ctrl-C to stop it.
    10 9 8 7 6 5 4
     3 2 1
    Starting repair.
    Opening filesystem to check...
    ERROR: cannot open device '/dev/sdd1': Device or resource busy
    ERROR: cannot open file system

     

    ....anything else i can do to recover files from the drive before format?

    most of the stuff on the drive is backed up anyways, so not a big deal

    I attached the SMART log....drive should still be under warrenty

    ST8000DM004-2CX188_WCT1BP7F-diagnostics-20200724 (sdd).txt

  7. On 6/12/2020 at 1:38 PM, Kru-x said:

    I'm not sure, that problem usually indicates that WP can't reach wordpress.org server due to internet connection. I don't think it's a docker/unraid problem and the only problem I can think of is if you have changed network type (normal is "Bridge") so your container can't reach internet.

     

    plugins and updates work fine though....its only themes

  8. everytime i try to look for new plugins i get this message:

    An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums.

     

    any ideas?

    just running local wordpress at home...

  9. Hi everyone 🙂

    I have been having endless issues with BTRFS....

     

    some files i am unable to delete...

     

    Input/output error

     

    root 5 inode 24265354 errors 2001, no inode item, link count wrong
            unresolved ref dir 256 index 10 namelen 3 name VMS filetype 2 errors 4, no inode ref
    root 5 inode 31918401 errors 2001, no inode item, link count wrong
            unresolved ref dir 263 index 39 namelen 5 name plex2 filetype 2 errors 4, no inode ref
    ERROR: errors found in fs roots
    found 429917249536 bytes used, error(s) found
    total csum bytes: 284564684
    total tree bytes: 2985312256
    total fs tree bytes: 2559033344
    total extent tree bytes: 113246208
    btree space waste bytes: 860472707
    file data blocks allocated: 11333576867840
     referenced 411394830336

     

    Checking filesystem on /dev/sdc1
    UUID: cc634dc3-e790-438f-b9c0-3ead4e9fcdbb
    [1/7] checking root items
    checksum verify failed on 707087319040 found 000000B6 wanted 00000000
    checksum verify failed on 707087319040 found 000000B6 wanted 00000000
    checksum verify failed on 707087319040 found 000000B6 wanted 00000000
    bad tree block 707087319040, bytenr mismatch, want=707087319040, have=0
    ERROR: failed to repair root items: Input/output error

     

    How can i get rid of all errors?

    everything is currently backed up.

     

    what will actually happen if i run --repair? so many warnings about running it....