Originally posted by Tinkster
usually that kind of error comes up when there's problems with either the termination, term power or SCSI parity checks.
I don't have direct access to the server myself at the moment, but the guy who has been checking on it says the termination should be correct. The disk is first on the chain and a cd-rom is after it, which is terminated. It doesn't say on the disk (a Quantum Lightning I think it is) how to terminate it, that's why it is set up like this. The CD-ROM is not needed actually, in fact it is possible that it is broken, it hasn't worked for quite some time but I haven't been bothered to check on it since it is only 4x.
Thanks, I'll read that tutorial, I surely need it. =]
As for your new & old Controller ... was the built in one a SymBios
Adaptec and Symbios use different low-level formats for SCSI HD's, and if you switched from Sym to Adaptec chances are that you'll have to low-level the drives... but first of all make sure termination is set-up right (e.g. that you didn't change the order of your HD's when rebuilding the system without swapping the termination)
Luckily, the old one was also Adaptec, so this doesn't apply to me.
I have been able to start the server with the disk working and reporting no errors and all partition sizes being OK. I don't know if it has something to do with the fact that it's been started with kernel 2.4.2-2, but I don't think so since the scsi card doesn't always find the disk but it did this time.
Since I got the disk mounted I've backed up all data so the the loss won't be so big anymore. But it would be nice if I didn't have to buy a new drive.
I tried to unmount the /home partition (the only one on the problem disk) but it didn't work, and afterwards the size of the last partition on the first disk is screwed up again. The error I got was this:
bash-2.05# umount /home
umount: /home: device is busy
bash-2.05# umount /home -f
umount2: Device or resource busy
umount: /dev/sdb1: not mounted
umount: /home: Illegal seek
I wanted to mount as read-only and try to run reiserfsck on it. But I guess I could erase it and make an ext3 fs on it instead. But I will still have to find out what the actual problem is, so I'll keep trying a bit more.
Thanks for taking your time to help me, it's much appreciated.