sacretagent

Members
 View Profile  See their activity

  • Posts

    943

  • Joined

  • Last visited

 Content Type 

Posts posted by sacretagent

    Release: rTorrent/ruTorrent for unRAID

    in Docker Containers

    Posted

    question

     

    i have plexconnect running in a docker on dockerport 80

    it needs to be 80 and can not be changed

     

    so if i install this now then i will have 2 dockers running on port 80....

    i know this one has a different host port but will this work?

     

    I want to get rid of deluge....  but i guess i can't change since this docker also runs on port 80 ?

    unRAID Server Release 6.0-beta14b-x86_64 Available

    in Announcements

    Posted

    Can Limetech please explain me if i can upgrade my server where i used fdisk to partition 1 big part of my cache disk in btrfs and 1 very  small part in raw to be used for swap file ?

    i spend 5 days on my other server to retrieve my complete tv database in plex...

    this server had 6000 movies in plex... which i would hate to rescan all :(

     

    so how do i go about it ?

     

    With -beta14 or higher we don't mess with the partition structure of a single cache disk if there already exists a mountable partition 1, so I think you should be good.  To be safe you could use 'dd' command to save your current MBR record to a file:

     

    dd if=/dev/sdX of=/boot/mbr.backup count=1

     

    (Replace 'sdX' with device name of your specific cache device.)

     

    After you upgrade and start array, if your cache device comes up 'unmountable' then do not click Format - instead send me email: [email protected].  But this shouldn't happen ;)

     

    Thanks guys,

     

    I took the jump today and upgraded both systems to 14B without issues

    the one with the raw swap file didn't have any problemsto find the partitions

    everything is up and running

    the gui seems MUCH snappier in this version

    overall the machines seems faster too

     

    will need to do some testing for that :)

    unRAID Server Release 6.0-beta14b-x86_64 Available

    in Announcements

    Posted

    Can Limetech please explain me if i can upgrade my server where i used fdisk to partition 1 big part of my cache disk in btrfs and 1 very  small part in raw to be used for swap file ?

    i spend 5 days on my other server to retrieve my complete tv database in plex...

    this server had 6000 movies in plex... which i would hate to rescan all :(

     

    so how do i go about it ?

    unRAID Server Release 6.0-beta13-x86_64 Available

    in Announcements

    Posted

    how would i proceed to upgrade my second server ?

     

    cache drive is partitioned with fdisk for sure

     

    sdg1 is btrfs cache drive

    sdg2 is swap file as btrfs doesn't support swap files

     

    my first server i reformatted the drive as i couldn't wait any longer for a solution... most things work again but rescanning plex will take days .....  50.000 + tv episodes

    unRAID Server Release 6.0-beta13-x86_64 Available

    in Announcements

    Posted

    what i don't get is why the disk is thinking he is reiserfs now

     

    he was XFS 100 % sure

     

    root@R2D2:~# xfs_db /dev/sdp1
xfs_db: /dev/sdp1 is not a valid XFS filesystem (unexpected SB magic number 0x00000000)
root@R2D2:~# xfs_db> sb 0
0: No such file or directory

fatal error -- couldn't initialize XFS library
root@R2D2:~# xfs_db /dev/sdp
xfs_db: /dev/sdp is not a valid XFS filesystem (unexpected SB magic number 0x00000000)
root@R2D2:~# dmesg | tail
mdcmd (21): import 20 0,0
mdcmd (22): import 21 0,0
mdcmd (23): import 22 0,0
mdcmd (24): import 23 0,0
ntfs: driver 2.1.30 [Flags: R/O MODULE].
REISERFS (device sdp1): found reiserfs format "3.6" with standard journal
REISERFS (device sdp1): using ordered data mode
reiserfs: using flush barriers
REISERFS warning (device sdp1): sh-462 check_advise_trans_params: bad transaction max size (66316). FSCK?
REISERFS warning (device sdp1): sh-2022 reiserfs_fill_super: unable to initialize journal space
root@R2D2:~#

    unRAID Server Release 6.0-beta13-x86_64 Available

    in Announcements

    Posted

    Stopped array ... disabled auto start of the array

    rebooted

    all disk show up....

    start array ....

    says my XFS cache disk is unformatted ??????

    so no dockers nothing works :(

     

    how to check and repair xfs drive ?

    XFS_REPAIR but sdp or sdp1 ?

     

    As mentioned by others, my cache drive now displays as unformatted. Unlike the previous posts, mine was btrfs formatted. Manually mounting the device results in a "bad superblock" message. I'm a long time unRAID user and am happy to financially contribute. That being said, I have a hard time justifying an upgrade from a free/trial license when my entire cache drive has just been compromised by a system upgrade.

     

    Post a system log please.

     

    Send all systemlogs to your email

    please check your email

    unRAID Server Release 6.0-beta13-x86_64 Available

    in Announcements

    Posted

    weird things here

     

    cache drive was XFS

     

    now it says reiser ?

     

    root@R2D2:~# fdisk -l /dev/sdp

     

    Disk /dev/sdp: 500.1 GB, 500107862016 bytes

    1 heads, 63 sectors/track, 15504336 cylinders, total 976773168 sectors

    Units = sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes

    Disk identifier: 0x00000000

     

      Device Boot      Start        End      Blocks  Id  System

    /dev/sdp1              64  976773167  488386552  83  Linux

    root@R2D2:~# file -s /dev/sdp1

    /dev/sdp1: ReiserFS V3.6

    root@R2D2:~#

     

    anything i can do to save my data .... I have a backup but it would take like a whole day to get that restored

    unRAID Server Release 6.0-beta13-x86_64 Available

    in Announcements

    Posted

    EPIC fail...

     

    not sure what i need to do now :(

    Did you clear your browser cache?

     

    i stopped my unraid ....

    put the usb in my windows checked the flash drive .. no errors

    copy pasted the install files from the website to the drive

    booted and same issue

     

    only get this error now on top

     

    Warning: syntax error, unexpected $end, expecting TC_DOLLAR_CURLY or TC_QUOTED_STRING or '"' in state/disks.ini on line 225 in /usr/local/emhttp/plugins/dynamix/template.php on line 36

     

    Dockerization of some popular applications.

    in Docker Containers

    Posted

    Needo.

     

    the Deluge docker...

    how you get that blackhole working ?

    i installed the autoadd plugin...

    put /blackhole and path to my servers blackhole in paths

     

    set the path to blackhole in deluge

     

    but it won't pick up anything

    also nothing in the logs that i can see.....

    so i think there is something with the path ?

     

    any help would be greatly appreciated ...

    beta10a - btrfs loop: Write error

    in Defect Reports [DEPRECATED]

    Posted

    here we go again :(

     

    Nov 30 02:08:44 R2D2 kernel: parent transid verify failed on 525189120 wanted 3970 found 2778 (Minor Issues)
Nov 30 02:08:44 R2D2 kernel: parent transid verify failed on 525189120 wanted 3970 found 2778 (Minor Issues)
Nov 30 02:08:44 R2D2 kernel: parent transid verify failed on 525189120 wanted 3970 found 2778 (Minor Issues)
Nov 30 02:08:44 R2D2 kernel: parent transid verify failed on 525189120 wanted 3970 found 2778 (Minor Issues)
Nov 30 02:08:44 R2D2 kernel: parent transid verify failed on 525189120 wanted 3970 found 2778 (Minor Issues)
Nov 30 02:08:44 R2D2 kernel: parent transid verify failed on 525189120 wanted 3970 found 2778 (Minor Issues)
Nov 30 02:08:44 R2D2 kernel: parent transid verify failed on 525189120 wanted 3970 found 2778 (Minor Issues)
Nov 30 02:08:44 R2D2 kernel: parent transid verify failed on 525189120 wanted 3970 found 2778 (Minor Issues)
Nov 30 02:08:44 R2D2 kernel: parent transid verify failed on 525189120 wanted 3970 found 2778 (Minor Issues)
Nov 30 02:08:44 R2D2 kernel: parent transid verify failed on 525189120 wanted 3970 found 2778 (Minor Issues)

     

     

    trying to recover fails ....

     

    root@R2D2:/#  /etc/rc.d/rc.docker stop

    stopping docker ...

    1e572081f341

    74d39161fafd

    093c54de1be4

    377be3b0d379

    aaf687ddde85

    8587f20a8101

    9034c4ef30d2

    unmounting docker loopback

    root@R2D2:/# btrfs check --repair /dev/loop8

    enabling repair mode

    check_mounted(): Could not open /dev/loop8

    Could not check mount status: No such file or directory

    root@R2D2:/# losetup /dev/loop8 /mnt/cache/dockerimage/docker2.img

    losetup: failed to setup loop device: No such file or directory

    root@R2D2:/# mknod -m 660 /dev/loop8 b 7 8

    root@R2D2:/# losetup /dev/loop8 /mnt/cache/dockerimage/docker2.img

    root@R2D2:/# btrfs check --repair /dev/loop8

    enabling repair mode

    parent transid verify failed on 524779520 wanted 3969 found 2778

    parent transid verify failed on 524779520 wanted 3969 found 2778

    parent transid verify failed on 524779520 wanted 3969 found 2778

    parent transid verify failed on 524779520 wanted 3969 found 2778

    Ignoring transid failure

    Couldn't setup extent tree

    Couldn't setup device tree

    Checking filesystem on /dev/loop8

    UUID: 7d2b78b1-2b82-4afa-bd6d-919af1ba55f3

    Critical roots corrupted, unable to fsck the FS

    Segmentation fault

    root@R2D2:/# btrfs-zero-log /dev/loop8

    parent transid verify failed on 524779520 wanted 3969 found 2778

    parent transid verify failed on 524779520 wanted 3969 found 2778

    parent transid verify failed on 524779520 wanted 3969 found 2778

    parent transid verify failed on 524779520 wanted 3969 found 2778

    Ignoring transid failure

    Couldn't setup extent tree

    root@R2D2:/# Couldn't setup extent tree

    > ^C

    root@R2D2:/# btrfs check --init-csum-tree /dev/loop8

    Creating a new CRC tree

    parent transid verify failed on 524779520 wanted 3969 found 2778

    parent transid verify failed on 524779520 wanted 3969 found 2778

    parent transid verify failed on 524779520 wanted 3969 found 2778

    parent transid verify failed on 524779520 wanted 3969 found 2778

    Ignoring transid failure

    Couldn't setup extent tree

    Couldn't setup device tree

    Checking filesystem on /dev/loop8

    UUID: 7d2b78b1-2b82-4afa-bd6d-919af1ba55f3

    Critical roots corrupted, unable to fsck the FS

    Segmentation fault

    root@R2D2:/# btrfs check --repair --init-csum-tree /dev/loop8

    enabling repair mode

    Creating a new CRC tree

    parent transid verify failed on 524779520 wanted 3969 found 2778

    parent transid verify failed on 524779520 wanted 3969 found 2778

    parent transid verify failed on 524779520 wanted 3969 found 2778

    parent transid verify failed on 524779520 wanted 3969 found 2778

    Ignoring transid failure

    Couldn't setup extent tree

    Couldn't setup device tree

    Checking filesystem on /dev/loop8

    UUID: 7d2b78b1-2b82-4afa-bd6d-919af1ba55f3

    Critical roots corrupted, unable to fsck the FS

    Segmentation fault

    root@R2D2:/# mount -o recovery,ro /dev/loop8 /var/lib/docker

    root@R2D2:/#  /etc/rc.d/rc.docker start

    starting docker ...

    root@R2D2:/#

     

    mounting it in recovery mode mounts  it read only

    all other commands fail

     

    Lime tech please let us know how we can recover these images

    i am getting crazy from this ...

    i have till 132gb free on my cache drive where this image is .... so it is not that the drive fills up

    i think it is more something with the cache drive being busy and that then the btrfs driver fails...

     

    btrfs loop8 issues

    in General Support

    Posted

    last 3 weeks since the upgrade to 10a do i have to create at least 3 new images a week cause the current ones always get corrupted

     

    this is what i see in the syslog

     

    Nov 28 14:08:33 R2D2 kernel: parent transid verify failed on 1048788992 wanted 11774 found 11167 (Minor Issues)
Nov 28 14:08:33 R2D2 kernel: parent transid verify failed on 1048788992 wanted 11774 found 11167 (Minor Issues)
Nov 28 14:08:33 R2D2 kernel: ------------[ cut here ]------------
Nov 28 14:08:33 R2D2 kernel: WARNING: CPU: 3 PID: 1677 at fs/btrfs/super.c:259 __btrfs_abort_transaction+0x4b/0xfb() (Minor Issues)
Nov 28 14:08:33 R2D2 kernel: BTRFS: Transaction aborted (error -5) (Errors)
Nov 28 14:08:33 R2D2 kernel: Modules linked in: veth xt_nat ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 nf_nat iptable_filter ip_tables md_mod tun i2c_i801 pata_jmicron r8169 mii sata_sil24 ahci libahci asus_atk0110 [last unloaded: md_mod] (Drive related)
Nov 28 14:08:33 R2D2 kernel: CPU: 3 PID: 1677 Comm: btrfs-transacti Not tainted 3.16.3-unRAID #3 (Errors)
Nov 28 14:08:33 R2D2 kernel: Hardware name: System manufacturer System Product Name/P7P55D-E LX, BIOS 1701    09/27/2012
Nov 28 14:08:33 R2D2 kernel: 0000000000000000 ffff8800c65efc60 ffffffff815d9532 ffff8800c65efca8
Nov 28 14:08:33 R2D2 kernel: ffff8800c65efc98 ffffffff81040687 ffffffff81294a12 00000000fffffffb
Nov 28 14:08:33 R2D2 kernel: ffff8801cc92e800 ffff8801d16716e0 ffffffff8161f080 ffff8800c65efcf8
Nov 28 14:08:33 R2D2 kernel: Call Trace: (Errors)
Nov 28 14:08:33 R2D2 kernel: [<ffffffff815d9532>] dump_stack+0x45/0x56
Nov 28 14:08:33 R2D2 kernel: [<ffffffff81040687>] warn_slowpath_common+0x75/0x8e
Nov 28 14:08:33 R2D2 kernel: [<ffffffff81294a12>] ? __btrfs_abort_transaction+0x4b/0xfb
Nov 28 14:08:33 R2D2 kernel: [<ffffffff810406e7>] warn_slowpath_fmt+0x47/0x49
Nov 28 14:08:33 R2D2 kernel: [<ffffffff81294a12>] __btrfs_abort_transaction+0x4b/0xfb
Nov 28 14:08:33 R2D2 kernel: [<ffffffff812ad233>] btrfs_update_root+0x120/0x1f9
Nov 28 14:08:33 R2D2 kernel: [<ffffffff812b8320>] commit_fs_roots.isra.18+0x10f/0x142
Nov 28 14:08:33 R2D2 kernel: [<ffffffff812b8faf>] btrfs_commit_transaction+0x3ae/0x86c
Nov 28 14:08:33 R2D2 kernel: [<ffffffff812b54d4>] transaction_kthread+0xf7/0x1c8
Nov 28 14:08:33 R2D2 kernel: [<ffffffff812b53dd>] ? btrfs_cleanup_transaction+0x45b/0x45b
Nov 28 14:08:33 R2D2 kernel: [<ffffffff810588ba>] kthread+0xd6/0xde
Nov 28 14:08:33 R2D2 kernel: [<ffffffff810587e4>] ? kthread_create_on_node+0x168/0x168
Nov 28 14:08:33 R2D2 kernel: [<ffffffff815df3bc>] ret_from_fork+0x7c/0xb0
Nov 28 14:08:33 R2D2 kernel: [<ffffffff810587e4>] ? kthread_create_on_node+0x168/0x168
Nov 28 14:08:33 R2D2 kernel: ---[ end trace 55c16dbfabc95cc5 ]---
Nov 28 14:08:33 R2D2 kernel: BTRFS: error (device loop8) in btrfs_update_root:152: errno=-5 IO failure (Errors)
Nov 28 14:08:33 R2D2 kernel: BTRFS info (device loop8): forced readonly
Nov 28 14:08:33 R2D2 kernel: BTRFS warning (device loop8): Skipping commit of aborted transaction. (Minor Issues)
Nov 28 14:08:33 R2D2 kernel: BTRFS: error (device loop8) in cleanup_transaction:1571: errno=-5 IO failure (Errors)

     

    Beta9 didn't have this problem where i was good for months with same loop8 image

     

    so what screwed this up ?

     

     

    Docker not starting.

    in General Support

    Posted

    Try following ...

    rename your old docker image back to whatever it was

    Power down unraid

    remove your usb stick and put in a windows machine

    check usb drive / repair if necessary

    put usb back in unraid

    power on unraid

    see what happens.... might be that the powersurge did something to the usb drive ....

    Docker not starting.

    in General Support

    Posted

    probably your btrfs image got corrupted....

     

    easiest way is to rename your current docker image...

    once that is done start docker it will create a new image

    and then use the docker page to reinstall all your dockers...

    it is pretty easy with the MY-xxxx templates

    and if you saved all your data outside the image like most of us do then you don't lose a thing....

     

    you can try to rescue your current image but i tried that a number of times and always failed :(

    fix tools for btrfs suck big time ....

     

    beta10a - btrfs loop: Write error

    in Defect Reports [DEPRECATED]

    Posted

    this morning i woke up  again with a BTRFS issue

     

    Nov 24 10:24:16 R2D2 kernel: parent transid verify failed on 1015496704 wanted 23427 found 22558 (Minor Issues)
Nov 24 10:24:16 R2D2 kernel: parent transid verify failed on 1015496704 wanted 23427 found 22558 (Minor Issues)
Nov 24 10:24:16 R2D2 kernel: BTRFS: failed to read tree root on loop8 (Minor Issues)
Nov 24 10:24:16 R2D2 php: Not starting Docker: mount error (Errors)

     

    tried to fix it but again no luck...

    root@R2D2:~# /etc/rc.d/rc.docker start

    mount: wrong fs type, bad option, bad superblock on /dev/loop8,

          missing codepage or helper program, or other error

          In some cases useful info is found in syslog - try

          dmesg | tail  or so

     

    Not starting Docker: mount error

    root@R2D2:~# mount -t btrfs -o ro,recovery /dev/loop8 /var/lib/docker

    root@R2D2:~# mc

     

    root@R2D2:/mnt/cache/dockerfiles# cd /

    root@R2D2:/# /etc/rc.d/rc.docker stop

    stopping docker ...

    unmounting docker loopback

    root@R2D2:/# btrfs-zero-log /dev/loop8

    parent transid verify failed on 1015496704 wanted 23427 found 22558

    parent transid verify failed on 1015496704 wanted 23427 found 22558

    parent transid verify failed on 1015496704 wanted 23427 found 22558

    parent transid verify failed on 1015496704 wanted 23427 found 22558

    Ignoring transid failure

    Couldn't setup extent tree

     

    mounting with the ro option worked but  only thing you can do is take a backup....

     

    so busy again installing all my dockers on a new image :(

     

    beta10a - btrfs loop: Write error

    in Defect Reports [DEPRECATED]

    Posted

    i had same issues after upgrading to 10a

    never had them on 9

    had to make 3 new dockr.img files in the last week :(

     

    tried a few times to get this img repaired but btrfs is not easily repairable as reiserfs is ....

     

    can we get this loop on XFS ? aka will docker run on XFS?

     

    in the hope that xfs is better fixable then btrfs ?

    increase docker img space ?

    in General Support

    Posted

    did you try that with existing dockers installed ?

    are they still there ?

    cause what NAS was suggesting is ok my 20gb was there with dockers

    but when you change the size in the gui

    would it not delete the existing 20gb with dockers and make a new image from 25gb without the dockers there any more ?

     

     

    increase docker img space ?

    in General Support

    Posted

    >:(

    well i ended up doing same as above ...

    i think let's reboot my unraid maybe btrfs will have cleaned up some stuff after a reboot.....

    behold my dissapointment when docker didn't even want to start any more

    and no specific errors in the logs either why docker didn't want to start  :(

     

    so i renamed the docker.img to dockerold.img

    put the size to 25gb in the gui and rebooted unraid

    after that docker started an i had 25gb disk image

    just redid all the templates and everything up and running again ...

     

    took only a few hours to do but there should be an easier solution not ?

     

    i also tried the resize thing  but on /var/lib/docker and got an error message telling me that the size is too big