minidlna not starting after BETA3 to BETA 4 upgrade, tranmission starts but errors

[borisattva]

beta3 had successful installation of transmission and minidlna.
after seemingly successful UI upgrade method to BETA4, transmission is indicated to starts fine(blue on) under Control Services. but the minidlna does not (red off).

accessing the transmission ip yields no result. when i click on Transmission under plugins management, i get Red exclamation with "Sorry, an error occured."

saw the http://forums.freenas.org/showthread.php?7515-Beta4-Minidlna-Not-Starting thread, but the remedy there did not resolve my issue.

more /var/log/messages gets me this:

Jun 28 09:59:02 freenas mountd[3353]: can't delete exports for /mnt/caviar/jail/
plugins/usr/pbi/transmission-amd64/etc/transmission/home/Downloads: Invalid argu
ment
Jun 28 10:14:21 freenas ntpd[1514]: kernel time sync status change 2001
Jun 28 10:44:49 freenas manage.py: [freeadmin.navtree:413] Couldn't retrieve htt
p://192.168.1.115:80/plugins/minidlna/_s/treemenu: HTTP Error 500: Internal Serv
er Error
Jun 28 10:44:57 freenas manage.py: [services.views:79] Couldn't retrieve http://
192.168.1.115:80/plugins/minidlna/_s/status: HTTP Error 500: Internal Server Err
or
Jun 28 16:52:21 freenas ntpd[1514]: kernel time sync status change 6001
Jun 28 17:00:54 freenas ntpd[1514]: kernel time sync status change 2001
Jun 29 12:11:43 freenas manage.py: [freeadmin.navtree:413] Couldn't retrieve htt
p://192.168.1.115:80/plugins/minidlna/_s/treemenu: HTTP Error 500: Internal Serv
er Error
Jun 29 12:11:50 freenas manage.py: [services.views:79] Couldn't retrieve http://
192.168.1.115:80/plugins/minidlna/_s/status: HTTP Error 500: Internal Server Err
or

where do i start?

thank you

 

[William Grzybowski]

Did you upgrade the plugins as well?

Also, are you running x86 or x64

 

[borisattva]

i'm running x64. i considered upgrading the plugins but noticed that their version remained the same as what i had previously so i didnt.

just attempted to upgrade the jail itself and got this error:

Jun 29 19:15:51 freenas manage.py: [freeadmin.navtree:413] Couldn't retrieve http://192.168.1.115:80/plugins/transmission/_s/treemenu: <urlopen error timed out>
Jun 29 19:15:52 freenas manage.py: [freeadmin.navtree:413] Couldn't retrieve http://192.168.1.115:80/plugins/minidlna/_s/treemenu: <urlopen error timed out>
Jun 29 19:16:34 freenas manage.py: [middleware.exceptions:38] [MiddlewareError: The command /usr/local/sbin/pbi_add -e -f -p /mnt/caviar/jail/plugins --no-checksig /var/tmp/firmware/pbifile.pbi failed: "chown: /usr/pbi: Read-only file system chmod: /usr/pbi: Read-only file system rm: /mnt/caviar/jail/plugins/sbin/init: Operation not permitted rm: /mnt/caviar/jail/plugins/sbin: Directory not empty rm: /mnt/caviar/jail/plugins/var/empty: Operation not permitted rm: /mnt/caviar/jail/plugins/var: Directory not empty rm: /mnt/caviar/jail/plugins/libexec/ld-elf32.so.1: Operation not permitted rm: /mnt/caviar/jail/plugins/libexec/ld-elf.so.1: Operation not permitted rm: /mnt/caviar/jail/plugins/libexec: Directory not empty rm: /mnt/caviar/jail/plugins/usr/lib32/libc.so.7: Operation not permitted rm: /mnt/caviar/jail/plugins/usr/lib32/libthr.so.3: Operation not permitted rm: /mnt/caviar/jail/plugins/usr/lib32/libcrypt.so.5: Operation not permitted rm: /mnt/caviar/jail/plugins/usr/lib32/librt.so.1: Operation not permitte
Jun 29 19:16:34 freenas kernel: t permitte

when i tried to upgrade the plugins individually, i got:

Jun 29 19:20:53 freenas notifier: security.jail.allow_raw_sockets: 0 -> 1
Jun 29 19:20:53 freenas notifier: Configuring jails: sysvipc_allow=YES.
Jun 29 19:20:54 freenas mountd[2866]: can't delete exports for /mnt/caviar/jail/plugins/usr/pbi/transmission-amd64/etc/transmission/home/Downloads: Invalid argument
Jun 29 19:20:54 freenas mountd[2866]: can't delete exports for /mnt/caviar/jail/plugins/usr/pbi/transmission-amd64/etc/transmission/home/Downloads: Invalid argument
Jun 29 19:20:54 freenas notifier: Starting jails: plugins.
Jun 29 19:20:55 freenas notifier: add net default: gateway 192.168.1.1
Jun 29 19:20:55 freenas kernel: bridge0: Ethernet address: 96:66:9d:19:04:9e
Jun 29 19:20:55 freenas kernel: epair0a: Ethernet address: 02:dc:08:00:04:0a
Jun 29 19:20:55 freenas kernel: epair0b: Ethernet address: 02:dc:08:00:05:0b
Jun 29 19:20:55 freenas kernel: epair0a: link state changed to UP
Jun 29 19:20:55 freenas kernel: epair0b: link state changed to UP
Jun 29 19:20:55 freenas kernel: epair0a: promiscuous mode enabled
Jun 29 19:20:55 freenas kernel: bge0: promiscuous mode enabled
Jun 29 19:21:03 freenas manage.py: [services.views:79] Couldn't retrieve http://192.168.1.115:80/plugins/minidlna/_s/status: HTTP Error 500: Internal Server Error
Jun 29 19:21:17 freenas manage.py: [middleware.exceptions:38] [MiddlewareError: There was a problem creating the PBI]
Jun 29 19:21:17 freenas manage.py: [services.views:79] Couldn't retrieve http://192.168.1.115:80/plugins/minidlna/_s/status: HTTP Error 500: Internal Server Error
Jun 29 19:21:18 freenas manage.py: [freeadmin.navtree:413] Couldn't retrieve http://192.168.1.115:80/plugins/minidlna/_s/treemenu: HTTP Error 500: Internal Server Error
Jun 29 19:21:30 freenas manage.py: [middleware.exceptions:38] [MiddlewareError: There was a problem creating the PBI]
Jun 29 19:21:31 freenas manage.py: [services.views:79] Couldn't retrieve http://192.168.1.115:80/plugins/minidlna/_s/status: HTTP Error 500: Internal Server Error
Jun 29 19:21:31 freenas manage.py: [freeadmin.navtree:413] Couldn't retrieve http://192.168.1.115:80/plugins/minidlna/_s/treemenu: HTTP Error 500: Internal Server Error

the verbiage seems to imply that previous jail should be rm'd. is the only way to upgrade to replace the existing jail and the plugins entirely? or am i misunderstanding it.

 

[borisattva]

funny development. at this point i'm not sure if i continue here, or make a new thread.

basically i could not figure out the errors, so i decided to delete and simply re-install both plug ins.

deleted, and re-installed minidlna. was happy to find out that mounting points someone remained and weren't gone. do i installed the plug via the UI, and successfully selected the folders for it to monitor.

proceeded to delete transmission, and reinstall as well. in the course of configuring it after the install discovered that its mounting points were gone (on the jail)
went to browse for the path, only to discover that my main storage drive which is a 2 2tb ZFS mirror set, is completely clean. 5-10 minutes ago there was about 1 TB of data on it. and now its clean as a whistle. i looked at stats, and sure enough the capacity was around 1tb. and few minutes ago plummeted down to 45 mb or so.

so, while i would be quite curious to figure out what exactly happened and how to avoid it in the future,,.. any idea how i can get my data back, if at all? auto mount is not showing me a drive. i'm not comfortable unmounting tank until i know what to do ..

 

[ProtoSD]

I believe that was a know bug with Beta-2, your data getting wiped out when deleting a jail. Maybe you found another variation of that with Beta-3?

Sorry to hear that...

 

[borisattva]

i wondered that. the mount points were going to something like /tank/media/video/ <-> /jail/minidlna/media. essentially this allowed the minidlna from inside the jail to access and stream the videos which are actually stored in the tank. i can totally imagine (in hindsight) minidlna deletion wiping out the internal /media, and with it the mounted /video/ on the tank. but i'm not getting how that would wipe out all of the root on the tank along with it. is that feasible?

if so,

1) is there any way i can contribute anything at this stage about my instance of freenas, to help identifying the bug?

2) my limited understanding of data is that until its written over its not really gone. is there any possible way to restore the data since there was not overwrite, or is ZFS different in this sense?

 

[borisattva]

*bump*

i held on to both the drives of this mirror with hopes that some method of recovery comes up down the road.

i have come across some experimental proof-of-concept successes, but does anyone know if something more robust have come along since then?
or if not so far, is a method of recovery even *hypothetically* possible, to justify me hanging on to the drives still?

 

[SweetAndLow]

If your data got deleted and it sounds like yours did there will be no chance of getting it back and probably never will be. Sorry to hear it got deleted that was just a stupid bug.

 

[borisattva]

thank you for replying SweetAndLow.

one more question in this regard, i understand that chance of recovery is unlikely to ever occur, but since this was a mirror zfs, should i be able to wipe one of the drives, and keep the other one for that slim-to-none chance that some time in the future it MIGHT be recoverable?

in other words, are the 2 parts of the same mirror identical, and can be preserved without each other, or is there something between/about mirrors that makes them complementary to each other in regard to forensic data efforts?

 

[SweetAndLow]

thank you for replying SweetAndLow.

one more question in this regard, i understand that chance of recovery is unlikely to ever occur, but since this was a mirror zfs, should i be able to wipe one of the drives, and keep the other one for that slim-to-none chance that some time in the future it MIGHT be recoverable?

in other words, are the 2 parts of the same mirror identical, and can be preserved without each other, or is there something between/about mirrors that makes them complementary to each other in regard to forensic data efforts?

You they are exact copies of each other but it is probably more complicated than that. If the data means that much to you that you will keep 1 drive around then you should keep both drives around to double your chances.

 

[borisattva]

it's several GBs of family photos, videos, of people passed, etc. irreplaceable stuff.
and i agree with your rationale. i'll hang on to both minuscule chance or not.

thank you for your time.
cheers