Quote:
|
05/29/2008 3:08:56 38 D SMB | SMB : sesssetup Unicode pwd exceeded max len: 82, truncate to 24
|
I do not see this vert often, but since the snap OS is 9 yrs old it does not like PW over 12chr.
Can you send be the complete log in html and I will take a look.
The Snap is very sensitive to timing issues. So if one drive is having a problem it can cause the server to go into to panic. I have had several through here that this has happened too. I have also seen system board failure too, but these are rare. A unit over heating due to fan failure can cause problems too. I had one that the fan would seam to randomly stop.
This is why I suggested using Spinrite to test the drives. This will either confirm or eliminate any drive problem.
If you don't have Spinrite you can break the array by removing 1 drive and see if the problem exist with a single drive. Then swap the drives and test the second one. If you do this you will have a broken raid array. The easiest way to rebuild the array is to force the mirror to individual config. Then use a utility of your choice to do a quick erase of the second drive. Then with all of the data on the pri (10000) drive you can create a new mirror. So if you decide to replace the HD you do not need to erase.
I like the spinrite. This way the mirror is not broken when the drives are reinstalled in there original position.
Any PC with Vista is not recommended. The SnapOS is not compatable with it. Some have beenable to work around most problems (bugs) but not all.