sacretagent

Members
  • Content Count

    943
  • Joined

  • Last visited

Everything posted by sacretagent

  1. 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 ?
  2. 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: tomm@lime-technology.com. But this shouldn't happen Thanks guys, I took the ju
  3. 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 ?
  4. 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
  5. 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/
  6. 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
  7. 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
  8. 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 ?
  9. 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
  10. 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 ...
  11. bonienl, any chanceto make a plugin from your version of the bitrot script integrated in dynamix ? was just thinking the script with a small gui would be helpfull
  12. ubuntu is just easier as it has more rpms ready made... most of the will work i debian but then you need to import ubuntu packages in debian and for what ? better stay with ubuntu
  13. bonienl, is the powerdown package installed with dynamix? i thought it was before.. just want to make sure....
  14. 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:
  15. 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) No
  16. 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 ....
  17. 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 ....
  18. see -> http://lime-technology.com/forum/index.php?topic=36273.msg338709#new
  19. 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... mounting with the ro option worked but only thing you can do is take a backup.... so busy again installin
  20. 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 ?
  21. great job... somebody should add that to the wiki ... or a sticky somewhere .... never thought about the easy solution LOL
  22. 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 ?
  23. 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 ?
  24. all data is outside of the image .... but i upgrade dockers constantly and i have 12 dockers running on this machine so i just need some extra space