Opawesome

Members
 View Profile  See their activity

  • Posts

    276

  • Joined

  • Last visited

Community Answers

  1. Opawesome
    Opawesome's post in (SOLVED) Issues with assining static IP to Docker container (Pihole) was marked as the answer   
    Can you try maybe deleting the 192.168.2.0/8 custom docker network ? This /8 CIDR seems very wrong to me on the 192.168.X.X range, as it may overlap with the 192.168.1.0/24 network.
  2. Opawesome
    Opawesome's post in (SOLVED) Cannot stop array to finalise shrink array while retaining parity operation was marked as the answer   
    I rebooted and got an unclean shutdown... Now performing a parity check...
     
    I later found a comment under one of SpaceInvaderOne's video on YouTube that someone figured out how to finalise the "stop array" operation (https://www.youtube.com/watch?v=nV5snitWrBk&lc=Ugweuc_wFZta3uxs0PV4AaABAg.9u9MWHF1ArU9vHBCZfLE09) :
     
     
    I hope this will help.
  3. Opawesome
    Opawesome's post in Cannot edit shares with a 'dot' in their name anymore since upgrade to 6.11.X was marked as the answer   
    I created a bug report:
     
  4. Opawesome
    Opawesome's post in Start/Stop array buttons not showing was marked as the answer   
    Thank you @JorgeB.
    My array is encrypted so clicking the button result in a "Missing encryption key" error, as no field is available to enter the passphrase.
    I rebooted the server once again and the START/STOP buttons are now showing, along with the passphrase field.
    Very weird indeed
    I wish you a good day.
    OP
  5. Opawesome
    Opawesome's post in Wipe free space was marked as the answer   
    It turns out this little script seems to do the job:
     
    #!/bin/bash DISKNUMBER="1" # Set the disk number which free space should be wiped dd if=/dev/zero of=/mnt/disk"$DISKNUMBER"/zero.small.file bs=1024 count=102400 cat /dev/zero > /mnt/disk"$DISKNUMBER"/zero.large.file sync ; sleep 5 ; sync rm /mnt/disk"$DISKNUMBER"/zero.small.file rm /mnt/disk"$DISKNUMBER"/zero.large.file unset DISKNUMBER  
    I have just tested it in a screen session. The disk filled up as expected and then the "zero.small.file" and "zero.large.file" were deleted to free up the space back.
     
    The point of having a small file is to avoid keeping the disk completely filled too long, as it can take time to delete the large file.
     
    I hope this helps.
     
    Any improvement or remark is obviously more than welcome.
     
    OP