Can't run parity check/rebuild?

[anthropoidape]

Hi all, I'm a very long-time user of unraid v4 and v5, but only just this weekend got around to switching to v6.

 

All is well. I am in the process of moving files around to convert to XFS - one 2TB drive down, 9 to go. Got a Windows 7 VM running in Xen... very cool. I just need to get plex going next, then swap in the much gruntier mobo and cpu from my current desktop PC, and I will be done for a while.

 

I hit a snag though. At a couple of points this afternoon, my unraid box completely froze. Totally frozen, ssh disconnected, VNC dead as well. No action at the physical keyboard either. I saw no option but to hard reboot. This actually happened 2 or 3 times in close succession, but has not happened since. The cause is currently a mystery. Anyway, it may or may not be related but I now have a triangle next to Disk 10 which indicates "invalid data content". What I can't see anywhere is an option to run a parity check or rebuild Disk 10. I just have invalid data and that's all I've got.

 

Am I blind? Shouldn't it just be there on the "main" page? Or is this a data failure of a kind that I haven't seen before?

 

I am running 6.0-beta15 with a Pro licence.

 

This problem aside, I am very excited with the new emphasis on virtualisation. My unraid 5 setup suddenly came into its own when I figured out vbox, and Xen is easier and better.

[trurl]

Tools - System Log - Download

 

then attach to your reply along with screenshot

[anthropoidape]

Of course, sorry.

 

syslog.zip

[trurl]

I don't notice anything obvious except for the unclean shutdown and the possible flash corruption. You might try putting it in your PC and letting it checkdisk.

 

What about Main - Disk 10 - Health - Disk attributes ?

[anthropoidape]

Thanks. I can't see anything untoward in the disk attributes.

 

Disk 10 attached to port: sdj
ID#	ATTRIBUTE NAME	FLAG	VALUE	WORST	THRESH	TYPE	UPDATED	FAILED	RAW VALUE
1	Raw Read Error Rate	0x002f	200	200	051	Pre-fail	Always	Never	0
3	Spin Up Time	0x0027	249	160	021	Pre-fail	Always	Never	2541
4	Start Stop Count	0x0032	100	100	000	Old age	Always	Never	779
5	Reallocated Sector Ct	0x0033	200	200	140	Pre-fail	Always	Never	0
7	Seek Error Rate	0x002e	100	253	000	Old age	Always	Never	0
9	Power On Hours	0x0032	093	093	000	Old age	Always	Never	5503
10	Spin Retry Count	0x0032	100	100	000	Old age	Always	Never	0
11	Calibration Retry Count	0x0032	100	100	000	Old age	Always	Never	0
12	Power Cycle Count	0x0032	100	100	000	Old age	Always	Never	638
192	Power-Off Retract Count	0x0032	200	200	000	Old age	Always	Never	585
193	Load Cycle Count	0x0032	200	200	000	Old age	Always	Never	780
194	Temperature Celsius	0x0022	126	112	000	Old age	Always	Never	24
196	Reallocated Event Count	0x0032	200	200	000	Old age	Always	Never	0
197	Current Pending Sector	0x0032	200	200	000	Old age	Always	Never	0
198	Offline Uncorrectable	0x0030	200	200	000	Old age	Offline	Never	0
199	UDMA CRC Error Count	0x0032	200	200	000	Old age	Always	Never	1
200	Multi Zone Error Rate	0x0008	200	200	000	Old age	Offline	Never	0

 

I am about to try rebooting in unraid v5 (as I have two sticks deal) and see what happens. I am not sure how it will handle the one XFS drive.

 

 

[anthropoidape]

Well, in unraid 5, no problem with parity or that disk's data was showing up at all. I am not sure whether that actually means anything though.

 

I ran chkdsk on the unraid 6 stick and it found no errors. I re-copied the v6beta15 files over (other than config) as well. It made no difference.

 

Am I looking in the right place for the parity check or rebuild option?

 

The XFS disk just showed up as "unformatted" btw, in case anyone is interested in what happens when you revert to unraid 5.

[anthropoidape]

Well, I stopped the array, restarted without any Disk 10, then restarted with a Disk 10. It's rebuilding now.