Unstable File Server

[Marcel Grandemange]

If you see in forum I had replaced all cables with brand new ones, upgraded
the PSU three times, and even tried multiple PCI controllers. The only place
I have not picked up issues yet is with the aacd array, almost everything
else has been giving issues on and off, however only under heavy data
transfer.

The drive im receiving the most issues from is also brand new and worked
perfectly under windows.
The 250gb Maxtor drive also works without hassels under windows.

I have also recently replaced the DVD rom because for no apparent reason it
started giving issues aswell.
(Even though it wasn't in use or even mounted)

I havant had issues with small drives, the boot drive has never reported any
form of errors and I replaced the Maxtor 250 with an old 20gb Seagate to
test and that worked flawlessly aswell.


I have no idea anymore of what to do.

-----Original Message-----
From: Tim Daneliuk [mailto:tundra at tundraware.com] 
Sent: Wednesday, June 25, 2008 4:19 PM
To: Marcel Grandemange
Cc: freebsd-questions at freebsd.org
Subject: Re: Unstable File Server

Marcel Grandemange wrote:
> Good day!
> 
> I hope someone might be able to assist me over here!
> 
>  
> 
> I have a multipurpose FreeBSD server, and one of the roles is being a file
> server.
> 
> This role however seems to continuously bring the machine to it's knees.
> 
>  
> 
> I have tried seeking help elsewhere namely
> 
> http://www.daemonforums.org/showthread.php?t=980
> 
>  
> 
> But still can't seem to get this going. Id really appreciate some input,
> thank you!

Have you tried swapping out the drive cables with new/UDMA133 ones.  Every
time I think
I've found a problem w/FBSD disk handling it ends up being the cables :)


__________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
"freebsd-questions-unsubscribe at freebsd.org"


__________ NOD32 3205 (20080621) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com