Jump to content

tsakodim

Members
 View Profile  See their activity

  • Posts

    21

  • Joined

  • Last visited

 Content Type 

Posts posted by tsakodim

    Big problem with following the official guide "Replacing Multiple Data Drives with a Single Larger Drive"

    in General Support

    Posted

    On 6/11/2021 at 9:25 AM, JorgeB said:

    You can, just move form disk to disk, don't involve shares.

    Hi again, so I just moved quite a lot of data with mc from disk to disk to equalize the load on the disks but still at my main tab the source disk that was the almost full disk is still almost full even though the data on target disk that I moved seems to has been moved. Meaning that the capacity of the target disk has changed.

     

    I did a parity check but still the same. Do I have to do the move with the array stopped?

     

    What on earth am I doing wrong???

    Big problem with following the official guide "Replacing Multiple Data Drives with a Single Larger Drive"

    in General Support

    Posted

    21 hours ago, JorgeB said:

    Assuming you copied the data directly to the disk, i.e., without using a specif folder or share and it's now together with the data that already existed on that disk I would remove the disk from the array, then run rsync again but now from an unassign disk to the array, you'll need to do it multiple times if there are multiple shares on source, but it will start where it left of, i.e., just copy whatever is missing, and since the array is now the dest no issues with space.

     

    I think I have understood the process but as I mentioned the rsync was not completed because dest disk got full so now I don't know what files have not been transfered and are still only on the source disk. Unless I can do the process you said for both the source and the dest disk and the duplicate files will just be skiped or overwritten.

    Big problem with following the official guide "Replacing Multiple Data Drives with a Single Larger Drive"

    in General Support

    Posted

    I searched the dest disk for vdisks it only had one 30GB. The source disk had none though. So there is no way I can understand how the 700GB of the source disk grew that much to occupy the 1.4TB of the dest disk and without any vdisk in source disk.

     

    By the way if I repeat the rsync command with the --sparse flag will it replace and fix these elusive large files that occupy all this space?

     

    And what about the --inplace flag could that help?

     

    Thanks in advance

     

     

     

     

    Big problem with following the official guide "Replacing Multiple Data Drives with a Single Larger Drive"

    in General Support

    Posted

    9 hours ago, JorgeB said:

    It doesn't, but if there were any sparse files on source (like vdisks) they won't be sparse on dest unless you use the appropriate flag.

    Sorry my english are not that good so I have to google what sparse file is. Do you know how can I check if there were any sparce files? And what is right flag and why it was not mentioned on the wiki guide 🤬

     

    Thanks for your help really appreciate it

    Big problem with following the official guide "Replacing Multiple Data Drives with a Single Larger Drive"

    in General Support

    Posted

    10 hours ago, Vr2Io said:

    A simple question, how much source files size, destination used and free space.

     

    Obviously I don't have the destination used and free space anymore since the destination drive is full now but the source is 714GB and the 2TB destination disk had 1.4+ TB free.

    I am thinking that this rsync does something more than just copying files. I am not an expert but I thought that the official guide would be a foolproof process.

    Big problem with following the official guide "Replacing Multiple Data Drives with a Single Larger Drive"

    in General Support

    Posted

    So I wanted to replace some of my old small drives with a bigger one. I found this guide from unraid's wiki:

    https://wiki.unraid.net/Replacing_Multiple_Data_Drives_with_a_Single_Larger_Drive

    I followed the "Safer method" and at the second part where I copy all the data from the small drive to the bigger one using the "rsync -avX ..." command even though I have doublechecked from the "main" tab that the destination (big new) drive had more than enough space for the data of the smaller drive the proccess has stopped with the following message:

     

    rsync: [receiver] write failed on "/mnt/disk1/*******.mp4": No space left on device (28)
    rsync error: error in file IO (code 11) at receiver.c(378) [receiver=3.2.3]
    rsync: [sender] write error: Broken pipe (32)

     

    What am I suppose to do now?

     

    I searched for a duplicate file finder plugin for unraid so I can find all the files that have been copied to the big drive from the small one and delete them so I can redo the process with another way maybe.

     

    Please help if anyone has any clue or idea

     

    Thank u

    [Support] lnxd - PhoenixMiner

    in Docker Containers

    Posted

    9 minutes ago, lnxd said:

    Thanks! If you mean to control it you’d need to start an interactive session using docker exec for now, I’m still investigating whether that’s possible.
     

    Otherwise the logs should be visible via the WebUI in the Docker page, click on the xmrig logo and press logs.

     

    Or of course run this in terminal: 

    
docker logs xmrig -f

     

    Yes the logs are what I wanted to see perfect
    Thanks again

    ps I left the donation to lnxd-fee, thats you right? Chears!

    Xeoma - Surveillance Software

    in Docker Containers

    Posted

    7 hours ago, mi5key said:

    No, I just put the VERSION in the /mnt/user/appdata/Xeoma/xeoma.config and it works just fine.  But coppit will have to update the image with the correct URL for the automatic updates to come in.

      

    
# The version to use. Valid values are a string like '17.5.5', 'latest', 'latest_beta', or a URL.
#VERSION='latest'
VERSION='20.11.30'

     

    Thanks mi5key i did it and now its running but.... can't connect to it. This is what docker logs xeoma returns:

     

    *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
    *** Running /etc/my_init.d/10_syslog-ng.init...
    Dec 19 11:27:06 d0de56771b3d syslog-ng[13]: syslog-ng starting up; version='3.13.2'
    *** Running /etc/my_init.d/30_parse_config_file.sh...
    Configuration:
      PASSWORD=<hidden>
      VERSION=20.11.30
    *** Running /etc/my_init.d/40_install_xeoma.py...
    2020-12-19 11:27:07 Determining version of Xeoma to use
    2020-12-19 11:27:07 Config version is "20.11.30"
    2020-12-19 11:27:07 Using Xeoma version 20.11.30 (a user-specified version)
    2020-12-19 11:27:07 Downloaded file /config/downloads/xeoma_20.11.30.tgz already exists. Skipping download
    2020-12-19 11:27:07 Installing Xeoma from /config/downloads/xeoma_20.11.30.tgz
    2020-12-19 11:27:08 Installation complete
    *** Running /etc/my_init.d/50_configure_xeoma.sh...
    [Dec 19 11:27:08 AM] Setting the password


    Password set successfull
    *** Booting runit daemon...
    *** Runit started as PID 70
    [Dec 19 11:27:08 AM] Starting the server in 5 seconds. See the log directory in your config directory for server logs.
    Dec 19 11:27:08 d0de56771b3d cron[75]: (CRON) INFO (pidfile fd = 3)
    Dec 19 11:27:08 d0de56771b3d cron[75]: (CRON) INFO (Running @reboot jobs)
    [Dec 19 11:27:08 AM] Not using archive cache
    /bin/sh: 1: ip: not found
    /bin/sh: 1: ip: not found
    /bin/sh: 1: ip: not found
    /bin/sh: 1: ip: not found

     

    I run it in bridge mode but I have tried also host mode and still the same. I ping the address from a windows pc and nothing there too.

     

    I must have missed an important step I guess

     

     

    Screenshot 2020-12-19 133203.jpg

    Weird share access situation

    in General Support

    Posted

    Today when I woke up I found out the power has gone down during the night but cause of UPS the server hasn't turn off. When I tried to access my unraid mapped drive in windows it was not working and trying the //tower at the explorer had the same effect. The same was happening to all my other machines in the house (media players etc). The GUI of the server though at http://tower was working fine and all the shares appeared fine and i could browse them through the web interface. So I tried to access the shares through the static ip address and everything was ok. Something was wrong with the name "tower" so I changed the server name to something else and it worked again with the new name.

    Anyone else ever experienced similar situation?

    My version is 6.4.1

×
×
  • Create New...