just for the record: this really seems to be an issue with the ar device. i took one of the drives off from the promise controller (ar), attached it to the onboard controller (ad) and everything works fine.
i'm cc'ing to freebsd-hackers because of this post: http://www.geocrawler.com/mail/msg.php3?msg_id=6949487&list=159 (see below).
now, another question: looking at dmesg i found that ar2 is also given the device name ad7 (don't be confused by my previous post, the order of the disks changed):
ar2: 117246MB <ATA RAID0 array> [14946/255/63] status: READY subdisks:
0 READY ad7: 117246MB <Maxtor 6Y120L0> [238216/16/63] at ata3-slave UDMA100
so i though i might use ad7 instead of ar2 but trying to use /dev/ad7 with disklabel gives me 'Device is busy' error.
please note that this is in fact no raid configuration. the disks just appear as ar because they are attached to the promise controller.
hum... again, any hints how i could build a concatenated vinum volume from the single ar drives ?
thanks and br, jonas
Jonas Sonntag wrote:
hi list
i'm trying to set up a concatenated vinum volume. i read chapter 13 in the handbook and as so often i've found a nice how-to on freebsddiary.org but somehow i'm stuck.
my /etc/vinum.conf file is like this: drive a device /dev/ar1h drive b device /dev/ar2h volume stuff plex org concat sd length 117239m drive a sd length 78528m drive b
disklabels: # /dev/ar1c: type: ESDI disk: ar1s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 14945 sectors/unit: 240107427 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
c: 240107427 0 unused 0 0 # (Cyl. 0 - 14945*)
h: 240107427 0 vinum # (Cyl. 0 - 14945*)
# /dev/ar2c: type: ESDI disk: ar2s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 10010 sectors/unit: 160826652 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
c: 160826652 0 unused 0 0 # (Cyl. 0 - 10010*)
h: 160826652 0 vinum # (Cyl. 0 - 10010*)
fidsk also looks good:
/dev/ar1: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 240107427 (117239 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63
/dev/ar2: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 160826652 (78528 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63
now i seem to be missing something here.. when i do vinum create -f /etc/vinum.conf
what i get is:
1: drive a device /dev/ar1h
** 1 Can't initialize drive a: Operation not supported by device
2: drive b device /dev/ar2h
** 2 Can't initialize drive b: Operation not supported by device
0 drives:
1 volumes:
V stuff State: down Plexes: 1 Size: 191 GB
1 plexes:
P stuff.p0 C State: faulty Subdisks: 2 Size: 191 GB
2 subdisks:
S stuff.p0.s0 State: crashed PO: 0 B Size: 114 GB
S stuff.p0.s1 State: crashed PO: 114 GB Size: 76 GB
messages says: /kernel: vinum: stuff.p0.s0 is crashed /kernel: vinum: stuff.p0 is faulty /kernel: vinum: stuff.p0.s1 is crashed
i have 'obliterated' the volume, i have remade the devices i allways end up with "Operation not supported by device".
something similar happens when i'm using the concat command to vinum:
vinum -> concat -v /dev/ar1h /dev/ar2h
volume vinum0
plex name vinum0.p0 org concat
drive vinumdrive0 device /dev/ar1h
Can't create drive vinumdrive0, device /dev/ar1h: Can't initialize drive vinumdrive0
i have come across this post: http://www.geocrawler.com/mail/msg.php3?msg_id=6949487&list=159
could that be the case with /dev/ar, too? i'm on 4.8-stable.
any hints how to go on would be great. please cc me, as i'm not on the list.
thanks and br jonas
_______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
