March 23, 201016 yr You may also see 2 parity errors, this is also normal. Huh? Should I be worried about 2 parity errors?
March 24, 201016 yr Author Well, all is mostly returned to normal and now is as good a time as any to thank Joe for all his help. I know it's a community, but I swear it's like he runs this site sometimes. Many thanks! One "quirky" thing I have going on: even though my array shows as disks 1, 2, and 3 now...when I go into my Network, I still see a share for disk 5...which is supposed to be gone now. OK, no big deal I thought; probably just a "phantom" share, and either it won't have any data in it, won't let me get in at all, or the data that it "thinks" is there will already be over on the new disks, or at the very least in my User shares. However...there are files there that AREN'T anywhere else...and when I try to copy and paste one from it to one of the new drives, it's doing it. WTF? How does it even see this supposed disk 5; it's not there anymore. uMP
March 24, 201016 yr You may also see 2 parity errors, this is also normal. Huh? Should I be worried about 2 parity errors? It is not unusual to see RaiserFS journaling actions to result in a few parity errors when starting after an unclean shutdown. For peace of mind (and overkill), I would do a clean shutdown, startup and run a parity check. Or (slightly less overkill) run another parity check. These should not result in any parity errors.
Archived
This topic is now archived and is closed to further replies.