it's been a couple years since, but i remember well trying to migrate file service from a w2k server to samba, and the thorny problems that arose, .pst file corruption among them. things got happier when i just put the .pst files back on the w2k server. i tried keeping much of the rest of file service on samba, and had fewer problems, consistent with .pst files getting the heaviest hammering. it seemed that w2k clients would easily give up on samba and fail to complete writes occasionally. and it seemed the samba server would then become inaccessible to that particular w2k client for a period of time. never any such trouble with the w2k server. On Tue, Oct 27, 2009 at 9:49 AM, Raymond Norton <admin at lctn.org> wrote: > This is the third time that a pst file has become corrupted for the same > network admin. They are one of a few users who have their files on the > new 2TB Sans Digital box. This really bothers me, and makes me nervous > to move other users over. My files are on the same box, but I have not > had any problems. Not sure what is causing the problem. > > > Sorry if you've already gone through this but I've seen that PST files > > are often the most used area of a file system/drive on a given > > workstation. Try a chkdsk on the drive connected to another machine. > > Also for some reason Vista/Windows 7 chkdsk has been more successful > > for us than the XP version. > > > > Another thing that seems to work well, although we're not entirely > > sure why, is copying the same file using a an IDE/SATA -> USB device. > > Not sure if it's the slower speed or what but some problematic files > > do better that way. > > > > Failing any of that, you could run the drive through SpinRite which > > will hammer every sector and hopefully mark that sector bad, recover > > the data it needs and move it to another sector. Back up anything > > else you have on the drive as SpinRite whacks it pretty hard and if > > it's close to failing already, it might be the last nail. > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20091027/9a1db1a7/attachment.htm