eaglepigjim

Never mind, after hours of troubleshooting I found out the Roon Client would just hang on the loading screen. I reinstalled it and it worked again because it said I had to revoke the previous installation.

Hi, Thanks for creating this container. It has worked fine for ages, but recently I started getting the same 'get lock file path' error that others are getting. I deleted the docker and the appdata folder and reinstalled, same error. I checked for the double docker path that one user had but it still throws the error. Do you have any idea on how to fix this? Thanks Jim

I cant afford to replace it, so should I just start it and let it erase it as it says?

That is strange it was fine before I rebooted otherwise I wouldn't have done it. Is it getting mixed up with the drive I just witched from reiserfs to xfs?

Here you go. taranis-diagnostics-20170401-1335.zip

The log is strange too. It is calling that disk #29, but there are only 25 including the flash drive in the server: Apr 1 13:20:54 Taranis kernel: md: import disk11: (sde) ST5000DM000-1FK178_W4J13BMJ size: 4883770532 Apr 1 13:20:54 Taranis kernel: mdcmd (13): import 12 sdd 1953514552 0 WDC_WD20EARS-00MVWB0_WD-WMAZA3343353 Apr 1 13:20:54 Taranis kernel: md: import disk12: (sdd) WDC_WD20EARS-00MVWB0_WD-WMAZA3343353 size: 1953514552 Apr 1 13:20:54 Taranis kernel: mdcmd (14): import 13 sdc 1953514552 0 WDC_WD20EARS-00MVWB0_WD-WMAZA2707168 Apr 1 13:20:54 Taranis kernel: md: import disk13: (sdc) WDC_WD20EARS-00MVWB0_WD-WMAZA2707168 size: 1953514552 Apr 1 13:20:54 Taranis kernel: mdcmd (15): import 14 sdy 4883770532 0 ST5000DM000-1FK178_W4J0TA07 Apr 1 13:20:54 Taranis kernel: md: import disk14: (sdy) ST5000DM000-1FK178_W4J0TA07 size: 4883770532 Apr 1 13:20:54 Taranis kernel: mdcmd (16): import 15 sdv 4883770532 0 ST5000DM000-1FK178_W4J1NBTT Apr 1 13:20:54 Taranis kernel: md: import disk15: (sdv) ST5000DM000-1FK178_W4J1NBTT size: 4883770532 Apr 1 13:20:54 Taranis kernel: mdcmd (17): import 16 sdu 3907018532 0 Hitachi_HDS724040ALE640_PK2331PAH1KH7T Apr 1 13:20:54 Taranis kernel: md: import disk16: (sdu) Hitachi_HDS724040ALE640_PK2331PAH1KH7T size: 3907018532 Apr 1 13:20:54 Taranis kernel: mdcmd (18): import 17 sdx 3907018532 0 ST4000DM000-1F2168_S3013ES8 Apr 1 13:20:54 Taranis kernel: md: import disk17: (sdx) ST4000DM000-1F2168_S3013ES8 size: 3907018532 Apr 1 13:20:54 Taranis kernel: mdcmd (19): import 18 sds 3907018532 0 WDC_WD40EZRX-00SPEB0_WD-WCC4E2EC87LY Apr 1 13:20:54 Taranis kernel: md: import disk18: (sds) WDC_WD40EZRX-00SPEB0_WD-WCC4E2EC87LY size: 3907018532 Apr 1 13:20:54 Taranis kernel: mdcmd (20): import 19 sdb 4883770532 0 ST5000DM000-1FK178_W4J0Z1Y8 Apr 1 13:20:54 Taranis kernel: md: import disk19: (sdb) ST5000DM000-1FK178_W4J0Z1Y8 size: 4883770532 Apr 1 13:20:54 Taranis kernel: mdcmd (21): import 20 sdl 3907018532 0 WDC_WD40EZRZ-00WN9B0_WD-WCC4E3KDEK0U Apr 1 13:20:54 Taranis kernel: md: import disk20: (sdl) WDC_WD40EZRZ-00WN9B0_WD-WCC4E3KDEK0U size: 3907018532 Apr 1 13:20:54 Taranis kernel: mdcmd (22): import 21 Apr 1 13:20:54 Taranis kernel: mdcmd (23): import 22 Apr 1 13:20:54 Taranis kernel: mdcmd (24): import 23 Apr 1 13:20:54 Taranis kernel: mdcmd (25): import 24 Apr 1 13:20:54 Taranis kernel: mdcmd (26): import 25 Apr 1 13:20:54 Taranis kernel: mdcmd (27): import 26 Apr 1 13:20:54 Taranis kernel: mdcmd (28): import 27 Apr 1 13:20:54 Taranis kernel: mdcmd (29): import 28 Apr 1 13:20:54 Taranis kernel: mdcmd (30): import 29 sdm 4883770532 0 ST5000DM000-1FK178_W4J13BNL Apr 1 13:20:54 Taranis kernel: md: import disk29: (sdm) ST5000DM000-1FK178_W4J13BNL size: 4883770532 Apr 1 13:20:54 Taranis emhttp: import 30 cache device: sdk Apr 1 13:20:54 Taranis emhttp: import 31 cache device: sdj Apr 1 13:20:54 Taranis emhttp: check_pool: /sbin/btrfs filesystem show f0914f41-d542-45ff-8007-190e8b288950 2>&1 Apr 1 13:20:54 Taranis emhttp: cacheUUID: f0914f41-d542-45ff-8007-190e8b288950 Apr 1 13:20:54 Taranis emhttp: cacheNumDevices: 2 Apr 1 13:20:54 Taranis emhttp: cacheTotDevices: 2 Apr 1 13:20:54 Taranis emhttp: cacheNumMissing: 0 Apr 1 13:20:54 Taranis emhttp: cacheNumMisplaced: 0 Apr 1 13:20:54 Taranis emhttp: cacheNumExtra: 0 Apr 1 13:20:54 Taranis emhttp: import flash device: sda

I didnt move any around. I had a pending resierfs to xfs change on disk 4 which is a 2TB disk. But I haven't touched any of the 5tb disks

I posted in the announcements forum and realized it is probably the wrong place. I just did an upgrade to 6.3.3 and it is telling me that all the data on Parity 1 will be erased. Id this normal?

I rebooted and it is telling me it will delete all the data on the parity drive. Is this normal? Should I start the array?

Hi, I have a Red X on a 5TB drive that is using 3.5TB. I have 7TB of space in the array. I have a spare 4TB drive which I would like to use to replace it but I can't because it is smaller. Can I move the files from the 5TB drive to other drives while the contents are being emulated until it is empty. Then remove the drive and add the 4TB into the slot in the server and bring it back online? I did run a short smart check on the 5TB and it was clean: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 1627 - If I can, I would then like to see if this 5TB is still good and use it as a second parity drive once the array is safe again. Regards Jim

Any luck with this? I need the server for work. Please help.

Here you go taranis-diagnostics-20170216-1539.zip

From the lack of responses, I guess this is a support call to lime tech?

Hi, I posted this in the General support forum. I recently just upgraded to version 6. My server is a 24 bay server, with 3 raid cards. My previous set up was using VMWare. VMWare was using the top 4 drives to 1 raid card (an LSI). Unraid was using the other 20 drives spread across the other 2 raid cards. The smaller of the 2 cards is an M1015, I dont remember the model but the other unraid card is the M1015's big brother with 5 or 6 ports. I never used VMWare, so wanted to use unRaid only on the server. I removed the raid card that VMWare was using, and plugged the cable into the last slot on the raid card. When I started up unRaid all my disks were unassigned. I thought no biggy, I'll just unplug it and switch back, but now all my disks are unassigned and it says my registration key is invalid. Can someone please help me? I would love to add these other 4 disks into unRaid as I don't have a cache on the current array and want to use Docker. 1) How do I get my system to be registered again? I haven't changed the USB stick. 2) How do I add the other 4 drives to the Raid Controller so I can assign them as cache drives? Thanks

I do have all the drives written down by serial number and saved on google drive if I had to put them back in the same order if that helps too.