I am the administrator for a PWS600au box with a few disk
drives attached. Today I tried to upgrade one of them from
an Elite9 Seagate disk to a Barracuda9 Seagate disk drive.
First I added the Barracuda disk to the SCSI chain, wrote
a disklabel, created a new filessystem (both disks just have
an ufs partition on the c slice), mounted the new filesystem
and copied the data. That all worked perfectly. The problem
I have is that when I put the Barracuda9 filesystem into
/etc/fstab, I get an error from ufs_fsck which interrupts
the boot process. Here is the error (the Barracuda9 is rz24) :
ufs_fsck -p
<output from other filesystems>
Can't open /dev/rrz24c: No such device or address
/dev/rrz24c: CAN'T CHECK FILE SYSTEM.
Once the system dumped me to the single user
prompt, the error is gone, eg. 'ufs_fsck -p'
works and I can mount /dev/rrz24c.
My suspicion was that the Barracuda9 was jumpered
to delay the spindle motor start and somhow the
disk wasn't ready when the first ufs_fsck ran
but was when I had the single user mode prompt.
After opening up the external enclosure I found
that the drive is jumpered for motor start on
powerup. At this point I abondened the disk
update since I didn't know what to do anymore.
Since the Elite9 disk is very old/slow compared
to the Barracuda9 and another Elite9 already
died on me, I really want to this update asap
and would appreciate any suggestions how to
fix my problem.
Thanks
Dirk Hufnagel
Received on Sat Jan 19 2002 - 20:30:21 NZDT