Date: Fri, 5 May 2000 18:38:27 -0400 (EDT) From: Jim Weeks <jim@siteplus.net> To: freebsd-fs@freebsd.org Subject: File system lost Message-ID: <Pine.BSF.4.21.0005051822430.1036-100000@discover.siteplus.net>
next in thread | raw e-mail | index | archive | help
I have a problem with a ST39140W Seagate SCSI drive. I have two of these attached to a BT-958 Mylex adapter on a machine running 3.4-stable and after a power outage one of them wouldn't come back up. The only way I can get the machine to boot into multi user mode is to comment out the entry for "/dev/da1s1e" in /etc/fstab. This is a dedicated drive with only one slice mounted as /bak. This was the default slice configuration used by /stand/sysinstall during the initial 3.2-stable snapshot installation about a year ago. I have been rebuilding the system from source on a regular basis ever since, and with no problems. Since the power glitch I can talk to the drive via camcontroll. I did a fsck /dev/da1 and am now able to "mount /dev/da1 /bak" with no problem. I can't however "mount /dev/da1s1e /bak" I get a device not configured error. A copy of dmesg shows that the drive is recognized which in this case is da1, but mount spits out the error not configured. kernel: da0 at bt0 bus 0 target 0 lun 0 kernel: da0: Fixed Direct Access SCSI-2 device kernel: da0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit), Tagged Queueing Enabled kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) kernel: da1 at bt0 bus 0 target 1 lun 0 kernel: da1: Fixed Direct Access SCSI-2 device kernel: da1: 20.000MB/s transfers (10.000MHz, offset 15, 16bit), Tagged Queueing Enabled kernel: da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) /stand/sysinstall also sees the drive, but when I try to configure through the partition manager there is no data listed in the configuration screen. I have also remade the device through MAKEDEV. I know the drive is working because when mounted as "/dev/da1 /bak" I am able to do backup operations with now problem. Another strange point is that /stand/sysinstall sees the drive as da1 but when you try to look at the slice information nothing is there. My question is what about the power glitch has corrupted the mounting of /dev/da1s1e? Any ideas would be appreciated, Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0005051822430.1036-100000>