Jump to content

jbat66

Members
  • Posts

    35
  • Joined

  • Last visited

Posts posted by jbat66

  1. UNRAID: 6.8.2

    I'm running an Intel NUC, so only have one drive. It is a 2.5" 5TB data drive. No parity drive. (no room in the case).

    I did a delete of a folder  of MP3's from a Windows 10 computer (ie. via SAMBA) The delete was taking a long time, so I canceled the delete... It didn't cancel and just hung. The Web GUI stayed up and SSH was working, but things were kind of flaky. So I stopped my Dockers, but they just hung in a stopping state. I did a Power down via the web GUI, but nothing happened after 10 min, so I did a reboot at SSH command prompt, and it said system was going down.... Again nothing on the console. So I punched the soft down power button on the server, and more services shutdown ect, but never did power down. All this time the HD light was blinking fast, as if I/O was happening.  Doing htop didn't show anything strange and CPU was at 5%, however the GUI CPU said 90%. I'm thinking the GUI CPU indication was wrong, as htop is looking at all the items running... So I waited 20 min for the system to shut down cleanly but did not completely shutdown... Then did hard down on the server. Brought the server back up, and GUI is working, but now the drive says "Unmountable: No file system". Currently the system says the disk is active and smart is healthy. I stopped the array started it in maint mode, and I'm currently doing a read check...

     


    Just wondering what my odds are that the drive will come back.

    To put it another way, does the read-check do any correcting of the XFS file system?

     

    Thanks

  2. On 1/31/2020 at 5:08 PM, Shaank0 said:

    I have had issues twice now randomly where the docker container shows its running, throws no errors but you cant connect to to the plex server (docker container) its running within the settings of 32400 but when you connect to it it doesnt pull anything up. It was working yesterday find. 

     

    Ive done a server reboot, no luck in fixing. not sure what happens as i have not updated anything.

     

    anyone else have this issue and if so how did you fix. 

    the allocations shows:

    binhex-plexpasshost192.168.1.2 '???'   (had to put quotes on '???' due to it changing into an emoji

    Network type is host, all other Docker and VM's are working fine.

    Yep same thing just happened to me.

    I'm running the binhex-plex not the binhex-plexpass

    Network type is host, all other Docker and VM's are working fine.

     

    I did just upgrade my free plex account to a plex pass, but that was it. I also just added a user, and that was about the time it quit working.

  3. 14 minutes ago, FrequencyLost said:

    Thanks for this plugin. I have my shares setup so they each use their own hard drive exclusively. I prefer the order of keeping things together, and i've been using this plugin to shift files when necessary to the drive its share is assigned to. One of my shares now exceeds the size of its hard drive, so I've added an additional drive for that share so it uses 2 disks exclusively, similar to the example below,


    Share 1 = Disk 1

    Share 2 = Disk 2

    Share 3 = Disk 3, Disk 4

    As far as I can tell its not possible, but can you please confirm if there is any way to use this plugin (or other means) to gather the files from Share 3 scattered across all disks and place them on either Disk 3 or Disk 4?

     

    Thanks in advance for any information you can provide

    I'm not sure if the unBALANCE plugin can do what you are wanting to do.

     

    I would use rsync at the command prompt and move a top level directory to your disk 4 so that you have space on disk 3 and disk 4. In the unRAID share management page, I would set Share 3 to only use Disk 3 and Disk 4, and then only split at the top level.

     

    If you are uncomfortable with rsync at the command prompt, you may want to look into the binhex - Krusader - Docker Container, and use that to move your files. When you set up Krusader, set your path varable to /mnt and not /mnt/user so that you can see the disk shares.

     

    One last note, wether you are using rsync or Krusader, make sure never to move or copy files from a "disk" share to a "user" share. Always go disk to disk or user to user.

    i.e. rsync -a /mnt/disk1/sharename/folder /mnt/disk2/sharename/folder

    or

    rsync -a /mnt/user/sharename/folder /mnt/user/someothershare/folder

     

     

  4. On 12/29/2019 at 5:07 PM, jbrodriguez said:

    I get you.

     

    I have those hard-coded arguments, because users can shoot themselves in the foot if they're not familiar with rsync.

     

    Especially the -R is really needed.

     

    I'll give it some more thought.

    Thanks, and I really do like your Reset to Default button. Basically just do a warning "don't change these settings, unless you understand rsync, otherwise click the reset button" lol

  5. 6 hours ago, jbrodriguez said:

    Hi, thanks for the comments !

     

    unBALANCE move works by copying then deleting, precisely for events such as your scenario (interrupted mid transfer).

     

    So you didn't actually need to move back files to the source, just delete files from the destination.

     

    Hope that makes sense.

    Yes that makes sense, thanks.

    One can never interrupt a transfer with -P enabled, for fear of a partial file hanging out. The only option would be to not interrupt the transfer, or if the transfer is interrupted, to make sure you do the same transfer later successfully or like you said delete all the files that were copied thus far.

     

    It would be great if it defaults stay as -avPRX, but you have made the -X customizable, it would be great if all the options were customizable. 

     

    Not UnBALANCE related, but rsync related. Today I had a problem moving files with rsync, and it was failing because it could not change the group settings. As you know the -a includes the -g and -o options specifically -a includes -rlptgoD. So I changed my settings from -av to -rlptDv (same as -av but no g and o) and was able to complete my transfer. Sometimes there are reasons when someone needs to change the rsync options.

     

    Thanks.

  6. Love your work on UB!!!

     

    I searched this thread but only saw one other comment about rsync -options. Would it be possible to let users change all the command line options for rsync, and not just the -X?
    "By default, rsync is invoked with -avPRX flags. Note that the X flag is customizable, so you can remove it if needed."
    Here is why I ask. the -P is problematic. I lost a 250GB file because of it. Here is the example.

    I have widget.dat (250GB) on Disk 1 along with other files in the share. I start the move to Disk 2, most of the file move, but it starts moving the 250GB file, and I cancel the move, before being completely done (or power outage or whatever).  Now I have widget.dat (250GB) on Disk 1, and widget.dat (39GB) on Disk 2.

     

    Now not looking at all my file sizes in the CLI, which most folks would not go. I use UB to move the files from Disk 2 back to Disk 1. My good widget.dat (250GB) on Disk 1 got overwritten by the partial ie bad widget.dat (39GB) from Disk 2. Good by file!!!!

     

    IMHO If -P was not on I would not have had data loss.

     

     

×
×
  • Create New...