Date: Thu, 5 Feb 2004 17:59:59 -0800 From: Paul Hoffman <phoffman@proper.com> To: freebsd-questions@FreeBSD.ORG Subject: Disk no longer valid Message-ID: <p0602045dbc48a3736106@[63.202.92.155]>
next in thread | raw e-mail | index | archive | help
Greetings. After rebooting a system that had been up for quite some time, I could not get the second drive (da1) to mount. The drive worked fine before I rebooted. dmesg reported: . . . da1s4: rejecting partition in BSD label: it isn't entirely within the slice da1s4: start 63, end 71132959, size 71132897 da1s4d: start 0, end 71132959, size 71132960 . . . When I tried to access the disk, dmesg said: . . . (da1:ahc0:0:1:0): SCB 0x36 - timed out >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< ahc0: Dumping Card State while idle, at SEQADDR 0x9 Card was paused ACCUM = 0x0, SINDEX = 0x1e, DINDEX = 0xe4, ARG_2 = 0x0 HCNT = 0x0 SCBPTR = 0x17 SCSIPHASE[0x0] SCSISIGI[0x0] ERROR[0x0] SCSIBUSL[0x0] [ lots more debugging info] >>>>>>>>>>>>>>>>> sg[0] - Addr 0x706d000 : Length 4096 sg[1] - Addr 0xdb6e000 : Length 4096 (da1:ahc0:0:1:0): Queuing a BDR SCB (da1:ahc0:0:1:0): no longer in timeout, status = 34a Feb 5 00:01:03 above /kernel: <<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>> >>>>>>> (da1:ahc0:0:1:0): Invalidating pack . . . The drive was inaccessible. I rebooted again. dmesg still says: . . . da1s4: rejecting partition in BSD label: it isn't entirely within the slice da1s4: start 63, end 71132959, size 71132897 da1s4d: start 0, end 71132959, size 71132960 . . . but now I can access the disk fine. Can I fix the drive without losing the information on it? If so, how? --Paul Hoffman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0602045dbc48a3736106>