ridley

Where are you suggesting running that command?

I thought I had setup the backup but it would appear that there is nothing in the Backup folder, sod. Can I copy the data as a backup? According to the config it is in /mnt/cache/appdata/roonserver/data I can find a cache folder on the server but there doesn't appear to be anything in it.

over on the roon community they seem to be indicating that this may be a corrupted update "That usually means that Roon Server didn’t update properly… Can you try reinstalling (over the current install is fine) Roon Server from our downloads page" However, how can I try the reinstall when it is in a docker?

Yes in the docker log

Hi, I have been running the ROON Docker on unraid for a couple of months and it has been working well. But today the core seems to have been corrupted of something. The core was starting this afternoon but I could not connect to it, but it wont even start anymore. If I look in the logs all that seems to be there is "Initialising Corrupt Build Initialising Corrupt Buiild" Which does not look promising. Any suggestions as to my options?

binhex-sabnzbd has been running fine for ages, recently I changed my server to a Dell r710 and it ran fine for a week or more. However today it seems very flaky, when I click on the gui to change something or whatever invariably it pops up "Lost connection to sabnzbd" and after a few 10s of seconds it pops back up but if I click again, it loses connection again. When I start the GUI from the dashboard it takes ages to appear, it used to be nigh on instantaneous. I managed to pick up this error message "Traceback (most recent call last): File "/opt/sabnzbd/cherrypy/_cprequest.py", line 670, in respond response.body = self.handler() File "/opt/sabnzbd/cherrypy/lib/encoding.py", line 220, in __call__ self.body = self.oldhandler(*args, **kwargs) File "/opt/sabnzbd/cherrypy/_cpdispatch.py", line 60, in __call__ return self.callable(*self.args, **self.kwargs) File "/opt/sabnzbd/sabnzbd/interface.py", line 127, in internal_wrap return wrap_func(*args, **kwargs) File "/opt/sabnzbd/sabnzbd/interface.py", line 413, in index history['slots'], fetched_items, history['noofslots'] = build_history(limit=cfg.history_limit(), output='json') File "/opt/sabnzbd/sabnzbd/api.py", line 1797, in build_history items, fetched_items, total_items = history_db.fetch_history(h_start, h_limit, search, failed_only, categories) File "/opt/sabnzbd/sabnzbd/database.py", line 289, in fetch_history res = self.execute(cmd + post, tuple(command_args)) File "/opt/sabnzbd/sabnzbd/database.py", line 132, in execute error = str(sys.exc_value) AttributeError: 'module' object has no attribute 'exc_value'" Behind the scenes it seems to be working, I think. Any idea on where to look?

I have several 8Tb drives (mixture Seagate and WD) as well as a WD 14TB parity all working fine, well they were until I wrote that.

Can it download Radio Shows as well as TV Shows? I have added a few radio shows to the list and although it seems to have searched for them it didn't pick them up, is there a way to tell it it is a Radio Show?

"Media" share has 32Tb free "Downloads" share has 9.15Tb free yet disk space on Sonarr is showing 13.7Gb free, why?

I have installed Sonarr from scratch and I think I have got it sort of right this time but under system it is telling me I have 20Gb of free space, but the share that I have the "media" pointed to has terabytes free. I must have some setting wrong, but any idea where?

I have just tried hot swapping, stopped the array, installed disks and restarted. Disks were picked up in UnAssigned devices before I got back to my PC. However I was not able to delete the partitions using UnAssigned devices on those drives until I rebooted.

Does this have a WebUI? I am used to Get-iPlayer on a PC but cannot see how to interact with this

well that would be the reason why then , thanks.

I do not know what I am doing wrong here but I have installed the pack but when I telnet in to the server and try to run Screen it says it cannot find the command. I know I am probably being a Noob but any suggestions?

The drive that is clearing was the Parity drive, before I replaced it with a new larger parity drive (and checked parity), is that why it is clearing the old parity drive?

I am trying to move from ReiserFS to xfs on my date drives and am following http://lime-technology.com/wiki/index.php/File_System_Conversion#Mirroring_procedure_to_convert_drives when I add a swap drive as described in the above it does not give me the option to format the drive, but states "Clearing in Progress" does this mean that every time I use one of the "reiserfs" drives as the new swap it is going to clear the drive first? Clearing a 3Tb drive will take ages never mind transferring the data then repeating, I have 15 drives to do this could take months!

Well after some fiddling about, reseating cables, swapping the order of the cards it now seems to be working. (Fingers crossed) Running some checks now.

OK I seem to have flashed my Dell H200 correctly, it all seemed to go well and I got the "enjoy your..." message. But when I put it into the server it does not show anything onscreen about a LSI or Dell card being present and once booted the hard drives are not visible. Anything I should look for? Try?

It is a large amount of data from one user share to another, so not necessarily the same disks.

Bump

I am also trying t install Krusader. What should I set the "Host path1" and "Host Path 2" to?

Can Dolphin move as apposed to copy? I have it loaded and cannot see a way. I will not have enough space to copy.

I am after a way of relatively quickly moving a large amount of data from a folder on one user share to another user share. Recommendations please.

I had a Red BAll on a 2Tb WD Red drive this week which was succesfully replaced and all is well with the array. However I have now ran Pre-Clear on the drive that had had read errors for 4 passes with the following results, does that make it safe to resuse in the array? ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sda = cycle 3 of 3, partition start on sector 64 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 19C, Elapsed Time: 53:14:13 ========================================================================1.13 == WDC WD20EFRX-68AX9N0 WD-WMC301458571 == Disk /dev/sda has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Temperature_Celsius = 128 127 0 ok 19 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. root@Tower:/boot# ****************

The Unraid system/drives were in a different case previously and were getting too hot. Hence the move to a larger cooler case some time ago, could that be it? Ridley