One of two HD on a FreeBSD system 8.1-RELEASE has bad sectors. The HD are configured as follow:
ad1 (/usr) has bad sectors. This problem started about one month ago, the day after I updated from 8.0-RELEASE-p2 to 8.0-RELEASE-p4 then to 8.1-RELEASE. Yesterday I made the patch update of 8.1-RELEASE. All updates were made using freebsd-update with default configuration file. The system notify bad sectors in daily e-mail reports, it never changed from the first notification about one month ago (this is the last one):
Today the system does not mount /usr and starts in single user mode.
I decided to change the HD with another of the same brand/type Maxtor ATA 80 GB model 6Y080P0. I executed fdisk, changed geometry to right values (16383/16/63) created one partition (all space), then ran label and created two slices: swap 2GB and /usr2 76GB. During newfs formatting some system messages came out, stating bad sectors exists on the new drive and newfs work aborted.
The system is quite old, the new HD was used on a Windows system with a single NTFS partition. I need to start the machine in multi user and modified the fstab to not check the drive (change fields 5th and 6th from 2 to 0) in the hope the system restart in multi user but it does not work. Is there a way to bypass the filesystem check and mount the bad HD?
Code:
ad0
/
/var
/tmp
swap
ad1
/usr
swap
Code:
+++ /tmp/security.UXrgMx73 2010-10-17 03:11:46.000000000 +0200
+ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=11440891
+g_vfs_done():ad1s1d[READ(offset=3710220288, length=2048)]error = 5
+ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=30928447
+g_vfs_done():ad1s1d[READ(offset=13687848960, length=2048)]error = 5
+ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=32058047
+g_vfs_done():ad1s1d[READ(offset=14266204160, length=2048)]error = 5
+ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=32057915
+g_vfs_done():ad1s1d[READ(offset=14266136576, length=2048)]error = 5
+ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=34691499
+g_vfs_done():ad1s1d[READ(offset=15614531584, length=2048)]error = 5
+ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=34691623
+g_vfs_done():ad1s1d[READ(offset=15614595072, length=2048)]error = 5
+ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=11440891
+g_vfs_done():ad1s1d[READ(offset=3710220288, length=2048)]error = 5
+ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=30928447
+g_vfs_done():ad1s1d[READ(offset=13687848960, length=2048)]error = 5
+ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=32058047
+g_vfs_done():ad1s1d[READ(offset=14266204160, length=2048)]error = 5
+ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=32057915
+g_vfs_done():ad1s1d[READ(offset=14266136576, length=2048)]error = 5
+ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=34691499
+g_vfs_done():ad1s1d[READ(offset=15614531584, length=2048)]error = 5
+ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=34691623
+g_vfs_done():ad1s1d[READ(offset=15614595072, length=2048)]error = 5
Today the system does not mount /usr and starts in single user mode.
I decided to change the HD with another of the same brand/type Maxtor ATA 80 GB model 6Y080P0. I executed fdisk, changed geometry to right values (16383/16/63) created one partition (all space), then ran label and created two slices: swap 2GB and /usr2 76GB. During newfs formatting some system messages came out, stating bad sectors exists on the new drive and newfs work aborted.
The system is quite old, the new HD was used on a Windows system with a single NTFS partition. I need to start the machine in multi user and modified the fstab to not check the drive (change fields 5th and 6th from 2 to 0) in the hope the system restart in multi user but it does not work. Is there a way to bypass the filesystem check and mount the bad HD?