The new FreeBSD v6.1 can read the XFS file system now. I'm going to set my 2200 up as a std share (No raid) when I get the 4500 in operation and verify it. But it will not help with a raid5 array. But it may be away to read the 1x00 model.
I talked with bug last night and the unit finally showed drive 3 had failed. Which is not the 10004 we were seeing in the log. Just got a fealing that 1 has failed, another may also be, and the disk may not have enough free space for cache. We terminated all operations/boots with the original 30 gig drives, soon as the snap indicated a failed drive. And concluded that it needs to go to a recovery service.
Snap-tech, you offer a lot of negative critism. But you fail to answer any of the PM I sent you early on. Just because you call your self a snap tech, does not prove any creditability. You have yet to contribute to this forum. All you have been trying to do is get work. As far as I now no one from the forum has used your service, or have not posted any feed back.
We have know early on that the Snap OS uses a modified XFS file system. But we all know that a Raid 5 is suppose to run in degraded mode with only 3 of the 4 drives. We were trying to get degraded mode working to recover the data. If you know the cmd to stop the file system check, we would like to know what it is. And we would like to know how to force up a share. The log isolated were the main problem directory/share is. Would just like to mount several shares if that is possiable, since the 60000 (raid5 array) would not mount. Was wanting to know if there is a work around.
Don't get me wrong this forum is used to transfer info between users and help solve problems. If you have something to contribute, we welcome you.
After talking to him, he know what he's talking about. And I'm glad he is on this forum. He has extensive expertise in HD & HD Arrays recovery for Snaps. He use to man the phone for tech support as a lead engineer.