"amnesiac" is disklabel?
Hello... I have three hard drives in my system. One of them (the first) is the system disk. I'm trying to get the other two ready to be a mirrored volume. No matter which of the last two drives is last, that one always is listed as "amnesiac" when I do a disklabel on it: == [root@archive 13:44:07 root]# disklabel ar2 # /dev/ar2: type: unknown disk: amnesiac label: fictitious flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 3737 sectors/unit: 60036417 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 600364170unused0 0 # (Cyl.0 - 3737*) == What does this mean? Whichever drive is last, that's the one I cannot "disklabel -e" to set its fstype to "vinum". Thanks, pete To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: "amnesiac" is disklabel?
On Sunday, 2 February 2003 at 13:50:20 -0500, Pete wrote: > Hello... I have three hard drives in my system. One of them (the first) > is the system disk. I'm trying to get the other two ready to be a > mirrored volume. No matter which of the last two drives is last, that > one always is listed as "amnesiac" when I do a disklabel on it: > > == > [root@archive 13:44:07 root]# disklabel ar2 > # /dev/ar2: > type: unknown > disk: amnesiac > label: fictitious > flags: > bytes/sector: 512 > sectors/track: 63 > tracks/cylinder: 255 > sectors/cylinder: 16065 > cylinders: 3737 > sectors/unit: 60036417 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # milliseconds > track-to-track seek: 0 # milliseconds > drivedata: 0 The only valid information above this point are the geometry specifications, and even they are not very valid. > 8 partitions: > #size offsetfstype [fsize bsize bps/cpg] > c: 600364170unused0 0 # (Cyl.0 - 3737*) > == > > What does this mean? Whichever drive is last, that's the one I cannot > "disklabel -e" to set its fstype to "vinum". There must be some other reason for that. Do you have any disk label at all? Otherwise use the /stand/sysinstall partition editor to create a partition. Greg -- 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: "amnesiac" is disklabel?
Sunday, February 2, 2003, 1:50:20 PM, you wrote: P> Hello... I have three hard drives in my system. One of them (the first) P> is the system disk. I'm trying to get the other two ready to be a P> mirrored volume. No matter which of the last two drives is last, that P> one always is listed as "amnesiac" when I do a disklabel on it: P> == P> [root@archive 13:44:07 root]# disklabel ar2 P> # /dev/ar2: P> type: unknown P> disk: amnesiac P> label: fictitious P> flags: P> bytes/sector: 512 P> sectors/track: 63 P> tracks/cylinder: 255 P> sectors/cylinder: 16065 P> cylinders: 3737 P> sectors/unit: 60036417 P> rpm: 3600 P> interleave: 1 P> trackskew: 0 P> cylinderskew: 0 P> headswitch: 0 # milliseconds P> track-to-track seek: 0 # milliseconds P> drivedata: 0 P> 8 partitions: P> #size offsetfstype [fsize bsize bps/cpg] P> c: 600364170unused0 0 # (Cyl.0 - 3737*) P> == P> What does this mean? Whichever drive is last, that's the one I cannot P> "disklabel -e" to set its fstype to "vinum". P> Thanks, P> pete Maybe I'm being obvious here but have you tried a different cable and/or controller? First step: eliminate hardware as the cause. -- Benmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: "amnesiac" is disklabel?
On Monday, 3 February 2003 at 1:34:02 -0500, Ben Williams wrote: > Sunday, February 2, 2003, 1:50:20 PM, you wrote: > > P> Hello... I have three hard drives in my system. One of them (the first) > P> is the system disk. I'm trying to get the other two ready to be a > P> mirrored volume. No matter which of the last two drives is last, that > P> one always is listed as "amnesiac" when I do a disklabel on it: > > P> == > P> [root@archive 13:44:07 root]# disklabel ar2 > P> # /dev/ar2: > P> type: unknown > P> disk: amnesiac > > Maybe I'm being obvious here but have you tried a different cable > and/or controller? > > First step: eliminate hardware as the cause. This isn't a hardware issue. Greg -- 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: "amnesiac" is disklabel?
On Monday, 3 February 2003 at 2:23:01 -0500, Ben Williams wrote: > Monday, February 3, 2003, 1:59:52 AM, you wrote: > > GgL> On Monday, 3 February 2003 at 1:34:02 -0500, Ben Williams wrote: >>> Sunday, February 2, 2003, 1:50:20 PM, you wrote: >>> >>> P> Hello... I have three hard drives in my system. One of them (the first) >>> P> is the system disk. I'm trying to get the other two ready to be a >>> P> mirrored volume. No matter which of the last two drives is last, that >>> P> one always is listed as "amnesiac" when I do a disklabel on it: >>> >>> P> == >>> P> [root@archive 13:44:07 root]# disklabel ar2 >>> P> # /dev/ar2: >>> P> type: unknown >>> P> disk: amnesiac >>> >>> Maybe I'm being obvious here but have you tried a different cable >>> and/or controller? >>> >>> First step: eliminate hardware as the cause. > > GgL> This isn't a hardware issue. > > Ok. I haven't had the time/need to use vinum yet so I wasn't sure if > this was possibly an esoteric FBSD error. This has nothing to do with Vinum. He hasn't got there yet. The clue to hardware errors here is that there's nothing to suggest it. The names are not random; they suggest some configuration problem. I'm pretty sure that's the case, though admittedly in my case it builds on similar experiences myself. Greg -- 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: "amnesiac" is disklabel?
On Mon, 03 Feb 2003, Greg 'groggy' Lehey wrote: > On Sunday, 2 February 2003 at 13:50:20 -0500, Pete wrote: > > == > > [root@archive 13:44:07 root]# disklabel ar2 > > # /dev/ar2: [snip] > > bytes/sector: 512 > > sectors/track: 63 > > tracks/cylinder: 255 > > sectors/cylinder: 16065 > > cylinders: 3737 > > sectors/unit: 60036417 [snip] > The only valid information above this point are the geometry > specifications, and even they are not very valid. Just a further datapoint... /dev/ar1 and /dev/ar2 are the same disk make and model. disklabel on /dev/ar1 shows one less cylinder (3736) and a corresponding lower number of sectors/unit (60034842). > > What does this mean? Whichever drive is last, that's the one I cannot > > "disklabel -e" to set its fstype to "vinum". > > There must be some other reason for that. Do you have any disk label > at all? Yes, it does. I can even mount /dev/ar2e because I had created a disk label on it when it was attached as /dev/ar1 previously. The problem seems to be accessing /dev/ar2 with disklabel. I've swapped cables and cards. I'm even currently using two cards (one ATA100 and ATA133). I've swapped the drives all around and the only constant factor seems to be ar2. With all three drives on one card (two master and one slave) or spread between the two cards (all three masters), as long as there were three drives, /dev/ar2 would be like this. Is the ar driver only limited to two devices? Thanks, pete To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: "amnesiac" is disklabel?
So it seems that there's a problem with more than two /dev/ar devices, or at least more than two Promise-based /dev/ar devices. Does anyone know more about this or should I take this to freebsd-hackers? Thanks, pete On Mon, 03 Feb 2003, Pete wrote: > On Mon, 03 Feb 2003, Greg 'groggy' Lehey wrote: > > > On Sunday, 2 February 2003 at 13:50:20 -0500, Pete wrote: > > > == > > > [root@archive 13:44:07 root]# disklabel ar2 > > > # /dev/ar2: > [snip] > > > bytes/sector: 512 > > > sectors/track: 63 > > > tracks/cylinder: 255 > > > sectors/cylinder: 16065 > > > cylinders: 3737 > > > sectors/unit: 60036417 > [snip] > > The only valid information above this point are the geometry > > specifications, and even they are not very valid. > > Just a further datapoint... /dev/ar1 and /dev/ar2 are the same disk make > and model. disklabel on /dev/ar1 shows one less cylinder (3736) and a > corresponding lower number of sectors/unit (60034842). > > > > What does this mean? Whichever drive is last, that's the one I cannot > > > "disklabel -e" to set its fstype to "vinum". > > > > There must be some other reason for that. Do you have any disk label > > at all? > > Yes, it does. I can even mount /dev/ar2e because I had created a disk > label on it when it was attached as /dev/ar1 previously. > > The problem seems to be accessing /dev/ar2 with disklabel. I've swapped > cables and cards. I'm even currently using two cards (one ATA100 and > ATA133). I've swapped the drives all around and the only constant > factor seems to be ar2. With all three drives on one card (two master > and one slave) or spread between the two cards (all three masters), as > long as there were three drives, /dev/ar2 would be like this. > > Is the ar driver only limited to two devices? > > Thanks, > pete To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: "amnesiac" is disklabel?
On Monday, 10 February 2003 at 23:11:02 -0500, Pete wrote: > On Mon, 03 Feb 2003, Pete wrote: > >> On Mon, 03 Feb 2003, Greg 'groggy' Lehey wrote: >> >>> On Sunday, 2 February 2003 at 13:50:20 -0500, Pete wrote: What does this mean? Whichever drive is last, that's the one I cannot "disklabel -e" to set its fstype to "vinum". >>> >>> There must be some other reason for that. Do you have any disk label >>> at all? >> >> Yes, it does. I can even mount /dev/ar2e because I had created a disk >> label on it when it was attached as /dev/ar1 previously. >> >> The problem seems to be accessing /dev/ar2 with disklabel. I've swapped >> cables and cards. I'm even currently using two cards (one ATA100 and >> ATA133). I've swapped the drives all around and the only constant >> factor seems to be ar2. With all three drives on one card (two master >> and one slave) or spread between the two cards (all three masters), as >> long as there were three drives, /dev/ar2 would be like this. >> >> Is the ar driver only limited to two devices? > > So it seems that there's a problem with more than two /dev/ar devices, > or at least more than two Promise-based /dev/ar devices. Does anyone > know more about this or should I take this to freebsd-hackers? Hmm, yes, that's a possibility. -hackers won't help you there, but a bug report might. Greg -- 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 msg18824/pgp0.pgp Description: PGP signature
Re[2]: "amnesiac" is disklabel?
Monday, February 3, 2003, 1:59:52 AM, you wrote: GgL> On Monday, 3 February 2003 at 1:34:02 -0500, Ben Williams wrote: >> Sunday, February 2, 2003, 1:50:20 PM, you wrote: >> >> P> Hello... I have three hard drives in my system. One of them (the first) >> P> is the system disk. I'm trying to get the other two ready to be a >> P> mirrored volume. No matter which of the last two drives is last, that >> P> one always is listed as "amnesiac" when I do a disklabel on it: >> >> P> == >> P> [root@archive 13:44:07 root]# disklabel ar2 >> P> # /dev/ar2: >> P> type: unknown >> P> disk: amnesiac >> >> Maybe I'm being obvious here but have you tried a different cable >> and/or controller? >> >> First step: eliminate hardware as the cause. GgL> This isn't a hardware issue. GgL> Greg GgL> -- GgL> When replying to this message, please copy the original recipients. GgL> If you don't, I may ignore the reply or reply to the original recipients. GgL> For more information, see http://www.lemis.com/questions.html GgL> See complete headers for address and phone numbers Ok. I haven't had the time/need to use vinum yet so I wasn't sure if this was possibly an esoteric FBSD error. -- Benmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
