Grave vinum problem (at least for me)
Greg 'groggy' Lehey
grog at FreeBSD.org
Tue Feb 10 18:20:40 PST 2004
On Thursday, 5 February 2004 at 6:48:18 +0100, Ole Voss wrote:
> Last night I reinstalled freebsd and obviously somewhere along the way my
> 400GB concat vinum volume wasn't unmounted (at least that's what freebsd
> told me). Now, when I run 'fsck -t ufs /dev/vinum/abyss'
> I get this:
> titan# fsck -t ufs /dev/vinum/abyss
> ** /dev/vinum/abyss
> CANNOT READ BLK: 843781344
> CONTINUE? [yn] y
> THE FOLLOWING DISK SECTORS COULD NOT BE READ: 843781344, 843781345,
> 843781346, 843781347,
> /dev/vinum/abyss: CANNOT FIGURE OUT FILE SYSTEM PARTITION
> It mounted fine last night and everything looked perfect. Then I did a
> reboot and ... well, this is it now.
> Can anybody help me out?
We need more information than this. This message alone could mean
that one of your disks is defective, or that some component of the
Vinum array is down. Take a look at
http://www.vinumvm.org/vinum/how-to-debug.html and supply the info I
ask for there.
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address and phone numbers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20040211/1de4be3e/attachment.bin
More information about the freebsd-questions