Interesting disk issue

[david1701]

My fileserver is pretty normal I guess, its an ancient gaming rig (I built it up with a vista BETA first time round) thats been repurposed a few times and now it lives with a 1tb OS driveand 3x3tb drives for storage.

I had the storage drives and the os drives/optical (removed as I'm using it elsewhere atm) on the two different sata busses (90% sure they're diff busses as they're a few inches apart and ones 4 ports the other 2).

Sometimes if I reboot it then it gives me a disk error because it can't find the OS drive (I can't find it in the bios either), I pulled the drive and dropped it into a caddy where it reads fine, back in the machine and it boots fine, so I write it off as a weirdness and keep going. A spell later I need to do another reboot and same issue, leave it 10 minutes grumpily and it boots.

tried using both busses (as bios always reads the file drives so I had to assume that that bus is fine) and I only have one sata power cable in there (told you it was old ) but I tried both ports.

All I can come to is some crazy temperature issue so I've cranked the fans up a bit and the case isn't getting hot at all :s (touched the drive to see how hot and its warm but not 70+ or anything)

 

[rusky]

get the manufacturer's diagnostic software & run that to see if it shows any errors.

 

[david1701]

nb the disk is only about 12 months old (file disks are 2 weeks old) which is why I was laying the blame at the door of other components

will run the checks. This is part of what worries me about the software raid I have running, I really really like being able to just pull a hd and drop it in my editing rig or a usb caddy and still being able access the data....

 

[2Loose]

On an older machine I had similiar issues due to (I assumed) HD spin up time.
I changed the boot order to check the optical drive first (empty) and never had the problem again. ymmv.

 

[david1701]

hm I like that idea a lot, I recently reshuffled the boot order to save time, that might just be it

the drive reads as healthy and works perfectly when its running, the crashing was due to a damaged file, everytime an automated program opened it the system fell over so thats fixed.