HidYn

Back up and running I disabled Virtualization in the BIOS. I concur this would be a good solution.

Literally just read the release notes and had the 'doh' moment. Just working through now apologies

Hi Guys, I've been using 6.10 without too many issues but today I updated to 6.10.2 and I have no network connection. Any ideas?

Hi Guys, Been using LanCache for over 6 months now and it's been fantastic for a family of 6. Today it seems to be broken all of a sudden. I get these errors in the nginx error log 2020/11/14 00:09:11 [emerg] 2349#2349: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:11 [emerg] 2349#2349: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:11 [emerg] 2349#2349: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:11 [emerg] 2349#2349: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:11 [emerg] 2349#2349: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:11 [emerg] 2349#2349: still could not bind() 2020/11/14 00:09:15 [emerg] 2370#2370: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:15 [emerg] 2370#2370: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:15 [emerg] 2370#2370: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:15 [emerg] 2370#2370: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:15 [emerg] 2370#2370: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:15 [emerg] 2370#2370: still could not bind() 2020/11/14 00:09:18 [emerg] 2372#2372: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:18 [emerg] 2372#2372: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:18 [emerg] 2372#2372: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:18 [emerg] 2372#2372: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:18 [emerg] 2372#2372: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:18 [emerg] 2372#2372: still could not bind() 2020/11/14 00:09:22 [emerg] 2374#2374: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:22 [emerg] 2374#2374: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:22 [emerg] 2374#2374: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:22 [emerg] 2374#2374: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:22 [emerg] 2374#2374: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:22 [emerg] 2374#2374: still could not bind() Any ideas?

Thanks I'll get on this now. Really do appreciate the help.

Still having issues. I left the array down and tried to leave it running some smart extended tests. All the disks vanished after a day of it running and went to unassigned devices. I've attached the logs. Can you help me pin it down to exactly what I need to replace. Thanks again. alpha-diagnostics-20190906-1740.zip

You might be on to something, Disabled the HPE Smart Array and now rebuilding the disk again. Looks much more promising with it's estimations - 2 days to rebuild 8tb. Fingers crossed this sorts it and thanks again for the help.

It’s just finished the rebuild and the drive is still listed as unmountable and now I have 4 unassigned devices. No idea what’s going on.

I ran it again. I’ve attached a screenshot. 2 drives have appeared as unassigned devices. Will look at removing that message that floods when I get in from work thanks for the advice. Excuse the screenshot from an iPad. Best I can do whist in work.

I stopped the rebuild when the reads/writes shot up to over 22 million and read errors went to over 82k according to the GUI. I'll start a rebuild again and take a screenshot and another diagnostic. Thanks for the reply.

I've got a HP Gen8 and have exactly the same issue. 2 disks appeared in unassigned devices. I'm still trying to fix the issue it seems like in my state of panic I might have broken things. I didn't think about taking a diagnostic at the time either.

Hi Guys, Came home from a camping trip today to a horror show. I had disk errors and a disabled disk. Following a few guides from the forums I'm trying to rebuild the disk that got disabled but I'm getting read errors from my parity. All disks seem to pass S.M.A.R.T fine. I do a parity check on the 1st of the month and it looks like that completed fine this morning from the e-mail I was sent. Should also mention I'm using a HP Micro Gen8 and seem the have the same issue as an earlier poster with 2 disks appearing in unassigned devices. I didn't use my brain and take a diagnostics before the inital reboot and panic to try and fix the issue. Stupid of me I know but never had any issues for the last 2 years. I've attached a diagnostics of the current state of play in the hope that someone can help. Any help would be really appreciated. You live and learn. Thanks in advance alpha-diagnostics-20190901-1828.zip