MrLondon

normally I just test that it's running this way. but even with Sick beard I cannot send notifications on port 8089 18:12:16 T:47361672959040 NOTICE: special://profile/ is mapped to: special://masterprofile/ 18:12:16 T:47361672959040 NOTICE: ----------------------------------------------------------------------- 18:12:16 T:47361672959040 NOTICE: Starting Kodi (14.0 Git:2014-12-30-ad747d9-dirty). Platform: Linux x86 64-bit 18:12:16 T:47361672959040 NOTICE: Using Release Kodi x64 build 18:12:16 T:47361672959040 NOTICE: Kodi compiled Dec 30 2014 by GCC 4.8.2 for Linux x86 64-bit version 3.13.11 (199947) 18:12:16 T:47361672959040 NOTICE: Running on Ubuntu 14.04.1 LTS, kernel: Linux x86 64-bit version 3.17.4-unRAID 18:12:16 T:47361672959040 NOTICE: FFmpeg statically linked, version: 14.0-Helix-xbmc-2.4.4-Helix 18:12:16 T:47361672959040 NOTICE: Host CPU: Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz, 4 cores available 18:12:16 T:47361672959040 NOTICE: special://xbmc/ is mapped to: /opt/kodi-server/share/kodi/ 18:12:16 T:47361672959040 NOTICE: special://xbmcbin/ is mapped to: /opt/kodi-server/lib/kodi 18:12:16 T:47361672959040 NOTICE: special://masterprofile/ is mapped to: /opt/kodi-server/share/kodi/portable_data/userdata 18:12:16 T:47361672959040 NOTICE: special://home/ is mapped to: /opt/kodi-server/share/kodi/portable_data 18:12:16 T:47361672959040 NOTICE: special://temp/ is mapped to: /opt/kodi-server/share/kodi/portable_data/temp 18:12:16 T:47361672959040 NOTICE: The executable running is: /opt/kodi-server/lib/kodi/kodi.bin 18:12:16 T:47361672959040 NOTICE: Local hostname: 0febb3265895 18:12:16 T:47361672959040 NOTICE: Log File is located: /opt/kodi-server/share/kodi/portable_data/temp/kodi.log 18:12:16 T:47361672959040 NOTICE: ----------------------------------------------------------------------- 18:12:16 T:47361672959040 ERROR: CXRandR::Query - unable to open xrandr xml 18:12:16 T:47361672959040 NOTICE: load settings... 18:12:16 T:47361672959040 WARNING: CSettingInt: unknown options filler "audiocdactions" of "audiocds.autoaction" 18:12:16 T:47361672959040 NOTICE: CAESinkOSS::EnumerateDevicesEx - No OSS mixer device present: /dev/mixer 18:12:16 T:47361672959040 NOTICE: No Devices found - retry: 4 18:12:18 T:47361672959040 NOTICE: CAESinkOSS::EnumerateDevicesEx - No OSS mixer device present: /dev/mixer 18:12:18 T:47361672959040 NOTICE: No Devices found - retry: 3 18:12:19 T:47361672959040 NOTICE: CAESinkOSS::EnumerateDevicesEx - No OSS mixer device present: /dev/mixer 18:12:19 T:47361672959040 NOTICE: No Devices found - retry: 2 18:12:21 T:47361672959040 NOTICE: CAESinkOSS::EnumerateDevicesEx - No OSS mixer device present: /dev/mixer 18:12:21 T:47361672959040 NOTICE: No Devices found - retry: 1 18:12:22 T:47361672959040 NOTICE: CAESinkOSS::EnumerateDevicesEx - No OSS mixer device present: /dev/mixer 18:12:22 T:47361672959040 NOTICE: Found 0 Lists of Devices 18:12:22 T:47361672959040 NOTICE: CAESinkOSS::EnumerateDevicesEx - No OSS mixer device present: /dev/mixer 18:12:22 T:47361672959040 NOTICE: No Devices found - retry: 4 18:12:24 T:47361672959040 NOTICE: CAESinkOSS::EnumerateDevicesEx - No OSS mixer device present: /dev/mixer 18:12:24 T:47361672959040 NOTICE: No Devices found - retry: 3 18:12:25 T:47361672959040 NOTICE: CAESinkOSS::EnumerateDevicesEx - No OSS mixer device present: /dev/mixer 18:12:25 T:47361672959040 NOTICE: No Devices found - retry: 2 18:12:27 T:47361672959040 NOTICE: CAESinkOSS::EnumerateDevicesEx - No OSS mixer device present: /dev/mixer 18:12:27 T:47361672959040 NOTICE: No Devices found - retry: 1 18:12:28 T:47361672959040 NOTICE: CAESinkOSS::EnumerateDevicesEx - No OSS mixer device present: /dev/mixer 18:12:28 T:47361672959040 NOTICE: Found 0 Lists of Devices 18:12:28 T:47361672959040 NOTICE: No settings file to load (special://xbmc/system/advancedsettings.xml) 18:12:28 T:47361672959040 NOTICE: Loaded settings file from special://profile/advancedsettings.xml 18:12:28 T:47361672959040 NOTICE: Contents of special://profile/advancedsettings.xml are... <advancedsettings> <!-- ##################################################### ############ DON'T EDIT OR DELETE THIS BLOCK ######## --> <videodatabase> <type>mysql</type> <host>192.168.0.24</host> <port>3306</port> <user>xbmc</user> <pass>xbmc</pass> </videodatabase> <musicdatabase> <type>mysql</type> <host>192.168.0.24</host> <port>3306</port> <user>xbmc</user> <pass>xbmc</pass> </musicdatabase> <services> <devicename>XBMC Server</devicename> <esallinterfaces>false</esallinterfaces> <escontinuousdelay>25</escontinuousdelay> <esenabled>true</esenabled> <esinitialdelay>750</esinitialdelay> <esmaxclients>20</esmaxclients> <esport>9777</esport> <esportrange>10</esportrange> <upnpannounce>true</upnpannounce> <upnprenderer>false</upnprenderer> <upnpserver>true</upnpserver> <webserver>true</webserver> <webserverpassword>xbmc</webserverpassword> <webserverport>8089</webserverport> <webserverusername>xbmc</webserverusername> <webskin>webinterface.default</webskin> <zeroconf>true</zeroconf> </services> <!-- ############ OR THINGS WILL BREAK ################### ##################################################### ########### THINGS BELOW ARE HOWEVER EDITABLE ####### refer to http://kodi.wiki/view/Advancedsettings.xml for info on the various settings --> <videolibrary> <importresumepoint>true</importresumepoint> <!-- import previously exported resume point from .nfo files --> <importwatchedstate>true</importwatchedstate> <!-- import previously exported playdate and playcount from .nfo files --> <backgroundupdate>true</backgroundupdate> <dateadded>0</dateadded> <!-- 0 results in using the current datetime when adding a video; 1 (default) results in prefering to use the files mtime (if it's valid) and only using the file's ctime if the mtime isn't valid; 2 results in using the newer datetime of the file's mtime and ctime --> </videolibrary> <musiclibrary> <backgroundupdate>true</backgroundupdate> </musiclibrary> <videoscanner> <ignoreerrors>true</ignoreerrors> <!-- Set to true to silently ignore errors while scanning videos. This prevents the error dialogue box, so you don't have to keep hitting "yes" to keep scanning.--> </videoscanner> <splash>false</splash> <bginfoloadermaxthreads>2</bginfoloadermaxthreads> <myvideos> <extractflags>false</extractflags> <extractthumb>false</extractthumb> </myvideos> <lookandfeel> <enablerssfeeds>false</enablerssfeeds> </lookandfeel> <audiooutput> <guisoundmode>0</guisoundmode> <ac3passthrough>false</ac3passthrough> <dtspassthrough>false</dtspassthrough> <multichannellpcm>false</multichannellpcm> <truehdpassthrough>false></truehdpassthrough> <dtshdpassthrough>false</dtshdpassthrough> <mode>2</mode> </audiooutput> <videoscreen> <vsync>2</vsync> </videoscreen> <input> <enablemouse>false</enablemouse> <remoteaskeyboard>false</remoteaskeyboard> </input> <general> <addonnotifications>false</addonnotifications> </general> <skinsettings> <setting type="bool" name="skin.confluence.FirstTimeRun">false</setting> </skinsettings> </advancedsettings> 18:12:28 T:47361672959040 WARNING: VIDEO database configuration is experimental. 18:12:28 T:47361672959040 WARNING: CSettingsManager: unable to read value of setting "audiooutput.truehdpassthrough" 18:12:28 T:47361672959040 NOTICE: Default DVD Player: dvdplayer 18:12:28 T:47361672959040 NOTICE: Default Video Player: dvdplayer 18:12:28 T:47361672959040 NOTICE: Default Audio Player: paplayer 18:12:28 T:47361672959040 NOTICE: Disabled debug logging due to GUI setting. Level 0. 18:12:28 T:47361672959040 NOTICE: Log level changed to "LOG_LEVEL_NORMAL" 18:12:28 T:47361672959040 NOTICE: Loading player core factory settings from special://xbmc/system/playercorefactory.xml. 18:12:28 T:47361672959040 NOTICE: Loaded playercorefactory configuration 18:12:28 T:47361672959040 NOTICE: Loading player core factory settings from special://masterprofile/playercorefactory.xml. 18:12:28 T:47361672959040 NOTICE: special://masterprofile/playercorefactory.xml does not exist. Skipping. 18:12:29 T:47362044126976 NOTICE: Thread ActiveAE start, auto delete: false 18:12:29 T:47362046228224 NOTICE: Thread AESink start, auto delete: false 18:12:29 T:47362044126976 NOTICE: CAESinkOSS::EnumerateDevicesEx - No OSS mixer device present: /dev/mixer 18:12:29 T:47362044126976 NOTICE: No Devices found - retry: 4 18:12:30 T:47362044126976 NOTICE: CAESinkOSS::EnumerateDevicesEx - No OSS mixer device present: /dev/mixer 18:12:30 T:47362044126976 NOTICE: No Devices found - retry: 3 18:12:32 T:47362044126976 NOTICE: CAESinkOSS::EnumerateDevicesEx - No OSS mixer device present: /dev/mixer 18:12:32 T:47362044126976 NOTICE: No Devices found - retry: 2 18:12:33 T:47362044126976 NOTICE: CAESinkOSS::EnumerateDevicesEx - No OSS mixer device present: /dev/mixer 18:12:33 T:47362044126976 NOTICE: No Devices found - retry: 1 18:12:35 T:47362044126976 NOTICE: CAESinkOSS::EnumerateDevicesEx - No OSS mixer device present: /dev/mixer 18:12:35 T:47362044126976 NOTICE: Found 0 Lists of Devices 18:12:35 T:47362048329472 NOTICE: Thread AESinkNull start, auto delete: false 18:12:35 T:47361672959040 NOTICE: Running database version Addons16 18:12:35 T:47361672959040 NOTICE: ADDONS: Using repository repository.xbmc.org 18:12:35 T:47361672959040 NOTICE: Running database version Addons16 18:12:35 T:47361672959040 NOTICE: Running database version ViewModes6 18:12:35 T:47361672959040 NOTICE: Running database version Textures13 18:12:36 T:47361672959040 NOTICE: Running database version MyMusic48 18:12:36 T:47361672959040 NOTICE: Running database version MyVideos90 18:12:36 T:47361672959040 NOTICE: Running database version TV26 18:12:36 T:47361672959040 NOTICE: Running database version Epg8 18:12:36 T:47361672959040 WARNING: JSONRPC: Could not parse type "PVR.Details.Channel" 18:12:36 T:47361672959040 WARNING: JSONRPC: Could not parse type "PVR.Details.ChannelGroup.Extended" 18:12:36 T:47361672959040 WARNING: JSONRPC: Could not parse type "GUI.Property.Value" 18:12:36 T:47361672959040 WARNING: JSONRPC: Could not parse type "Setting.Details.SettingList" 18:12:36 T:47361672959040 ERROR: JSONRPC: Could not parse method "Files.AddSource" 18:12:36 T:47362073745152 NOTICE: Thread LanguageInvoker start, auto delete: false 18:12:36 T:47361672959040 NOTICE: initialize done 18:12:36 T:47361672959040 NOTICE: Running the application... 18:12:36 T:47361672959040 NOTICE: Webserver: Starting... 18:12:36 T:47361672959040 NOTICE: WebServer: Started the webserver 18:12:36 T:47361672959040 NOTICE: starting upnp server 18:12:36 T:47361672959040 NOTICE: ES: Starting event server 18:12:36 T:47362422613760 NOTICE: Thread EventServer start, auto delete: false 18:12:36 T:47362424715008 NOTICE: Thread TCPServer start, auto delete: false 18:12:36 T:47362422613760 NOTICE: ES: Starting UDP Event server on 0.0.0.0:9777 18:12:36 T:47362422613760 NOTICE: UDP: Listening on port 9777 18:12:36 T:47362073745152 NOTICE: -->Python Interpreter Initialized<-- This is from my kodi log when I start the docker, don't see any errors and the dockerlog shows this *** Running /etc/my_init.d/firstrun.sh... using existing datafiles using existing advancedsettings.xml *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 16 Can't open display The command finished successfully!

hi there, I updated the container today and when I open the web interface it shows for about 2 sec Kodi but then it goes straight to lost connection to server, and when I click on on of the headers it just spins, but I cannot see any error messages in the kodi.log file. Any hints?

thanks was not aware of this, changed this now, and now the output has changed to this root@localhost:# /usr/bin/docker logs --tail=350 KODI-Headless *** Running /etc/my_init.d/firstrun.sh... creating datafiles creating advancedsettings.xml *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 18 Can't open display terminate called after throwing an instance of 'dbiplus::DbErrors' Can't open display The command finished successfully!

-v "/mnt/cache/appdata/kodi":"/root/.kodi":rw it's there

I am using the normal repro, no private one root@localhost:# /usr/bin/docker run -d --name="KODI-Headless" --net="bridge" --privileged="true" -e MYSQLip="192.168.0.24" -e MYSQLport="3306" -e MYSQLuser="xbmc" -e MYSQLpass="xbmc" -e TZ="Europe/London" -p 8089:8080/tcp -v "/mnt/cache/appdata/kodi":"/root/.kodi":rw sparklyballs/headless-kodi-helix 3788b29dea96d5867957bbb5ed3aa7056a78d207d4da82f36bcc291aa86d2dd4 The command finished successfully! shortly afterwards this again root@localhost:# /usr/bin/docker logs --tail=350 KODI-Headless *** Running /etc/my_init.d/firstrun.sh... creating datafiles cp: target '/opt/kodi-server/share/kodi/portable_data/' is not a directory creating advancedsettings.xml cp: cannot create regular file '/opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml': No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory *** /etc/my_init.d/firstrun.sh failed with status 2 *** Killing all processes... root@Tower:/mnt/cache/appdata/kodi# ls -ltr total 0 root@Tower:/mnt/cache/appdata/kodi# cd .. root@Tower:/mnt/cache/appdata# ls -ltr total 0 drwxrwxrwx 1 nobody users 0 Dec 30 12:30 kodi/

I tried your docker from the template, but I am getting errors *** Killing all processes... *** Running /etc/my_init.d/firstrun.sh... creating datafiles cp: target '/opt/kodi-server/share/kodi/portable_data/' is not a directory creating advancedsettings.xml cp: cannot create regular file '/opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml': No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory *** /etc/my_init.d/firstrun.sh failed with status 2 *** Killing all processes... I changed the port to 8089 and I changed the kodi path to /mnt/cache/kodi which has been created but it's empty. so I don't quite know where else to look.

Any update on this docker... I really would like to test beets on my collection which is very disorganized.

you also have to add the template location within the docker page manually and save afterwards otherwise it's not shown.

digiKam exists on Linux but not seen a docker for that

Parity finally completed this morning after connecting the parity drive to the motherboards sata port and connecting a data drive to the AOC controller

RobJ, sorry I changed the parity disk to another 3TB drive and the old parity drive was connected to the motherboard the new parity was not. So now I connected the new parity disk to the motherboard and started the parity sync again will see if that now goes through. Parity building is currently at 30% and no errors yet.

The last syslog I posted I am sure the parity is connected to motherboard but currently out of country so can only verify on Saturday

Actually I have two sas controllers plus onboard controller and the AoC took hours to fail and onboard quickly so don't think it's one controller giving issues

ok still not better, I have now fixed the md8 drive issues which was the only drive which failed the reiserfsck --check all others passed successfully. I have also formatted 4 drives as xfs successfully, just to make sure they don't give me further grief. However when I started the parity build it almost instantly failed with same errors. So the parity drive failed on a AOC-SASLP-MV8 - Supermicro port, actually two different ports on 2 different cables and now I moved it to a 3gb motherboard SATA port and it's actually failing faster than before. I highly doubt that all these ports could be faulty. But I don't know what else to try right now. I have now shutdown the server again and again I am getting errors from a reiserfs now from md16 which the check passed successfully. syslog-2014-09-14.zip

yeah I tried to copy the files from that drive but it was constantly hanging so I started the rebuild-tree now and will see how many of the files are actually good and how many corrupted. It appears that this was one of the drives I did a successful rebuild, but now it might not have been so successful with this corruption.

Will read-only check consistency of the filesystem on /dev/md8 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Fri Sep 12 13:32:21 2014 ########### Replaying journal: Trans replayed: mountid 212, transid 62314, desc 7440, len 1, commit 7442, next trans offset 7425 Trans replayed: mountid 212, transid 62315, desc 7443, len 1, commit 7445, next trans offset 7428 Replaying journal: Done. Reiserfs journal '/dev/md8' in blocks [18..8211]: 2 transactions replayed Zero bit found in on-disk bitmap after the last valid bit. Checking internal tree.. \/ 1 (of 22|/ 9 (of 91// 31 (of 88|block 348880938: The level of the node (0) is not correct, (1) expected the problem in the internal node occured (348880938), whole subtree/ 10 (of 91/block 322338874: The level of the node (0) is not correct, (2) expected the problem in the internal node occured (322338874), whole subtree/ 2 (of 22-block 305863291: The level of the node (0) is not correct, (3) expected the problem in the internal node occured (305863291), whole subtree is skipped finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 3 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Fri Sep 12 13:34:26 2014 ########### so that is already one drive where it claims there is corruption, should I run the rebuild-tree? I have tested all other md1-18 and all of them pass besides this one... so there appears to be only md8 which has this corruption...

I am now running the reiserfsck for all my 19 drives just to make sure they all pass before attempting another parity build.

I have now mounted the md15 drive into another machine and am running reiserfsck --check /dev/md1 against that one. see if I get anything from that drive. ########### reiserfsck --check started at Fri Sep 12 04:13:27 2014 ########### Replaying journal: Done. Reiserfs journal '/dev/md1' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 683156 Internal nodes 4412 Directories 1478 Other files 19289 Data block pointers 687587240 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Fri Sep 12 04:32:06 2014 seems all ok SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 178 176 021 Pre-fail Always - 6075 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 834 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 5784 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 144 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 25 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 808 194 Temperature_Celsius 0x0022 115 106 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 5784 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing

anybody have any idea how I can get the parity build complete successfully, would beta9 help me here? I am getting desperate here. Any help greatly appreciated.

Yeah especially as I already moved off the sas card onto the motherboard and still get same errors. The md14 was a failed drive replacement rebuilt which I only noticed after the failed drive had been shipped back. I have sent tom an email asking for help as I am fresh out of ideas seems to be getting worse now... the monitor connected to it is being flooded with these messages Sep 10 16:15:42 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 40958 does not match to the expected one 1 Sep 10 16:15:42 Tower kernel: REISERFS error (device md15): vs-5150 search_by_key: invalid format found in block 472002343. Fsck? Sep 10 16:15:42 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 40958 does not match to the expected one 1 Sep 10 16:15:42 Tower kernel: REISERFS error (device md15): vs-5150 search_by_key: invalid format found in block 472002343. Fsck? Sep 10 16:15:42 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 40958 does not match to the expected one 1 Sep 10 16:15:42 Tower kernel: REISERFS error (device md15): vs-5150 search_by_key: inva I have decided to shutdown the array now... before I lose more data. I used the powerdown script however that did not even work, had to hard power down the array.. something very strange going on.

now I am even more confused. I have now connected the parity drive to the mainboard SATA port which is another sata cable and still the parity build is aborted and the drive is shown with a red x. I need urgent help here. syslog-2014-09-102.zip

so another parity build failed with another 3TB drive which beforehand worked fine with preclear, this is with beta 6. now I don;'t know anymore syslog-2014-09-101.zip

ok I finished the rebuild-tree and it found some files. However when I now try to run the resync I have the 3TB parity drop from the system. I have already reseated the drive, used a different port, I even moved it out of my Norco 5x3 cage, but still same problem. Any suggestions? done a new configuration once again and used a different 3tb drive as a parity drive, lets see if that works. syslog-2014-09-10.zip

the reiserfsck asked me to run the --rebuild-tree so doing that right now... takes forever.

I actually believe that drive was the failed rebuild from a failed drive, but still don't know how to fix this now as the parity build process is running but it has lots of corruption on here.