Re: Disklabel problem IBM SCSI3 disks, vinum too
Date sent: Mon, 24 Nov 2003 09:16:49 +1030 From: Greg 'groggy' Lehey [EMAIL PROTECTED] To: Bob Collins [EMAIL PROTECTED] Organization: The FreeBSD Project Copies to: FreeBSD [EMAIL PROTECTED] Subject:Re: Disklabel problem IBM SCSI3 disks, vinum too [Format recovered--see http://www.lemis.com/email/email-format.html] Single-line paragraphs. On Sunday, 23 November 2003 at 13:03:47 -0500, Bob Collins wrote: At 07:30 PM 11/21/2003, you wrote: On Friday, 21 November 2003 at 9:25:58 -0500, Bob Collins wrote: vinum - list 4 drives: D d State: up Device /dev/da1s1h Avail: 0/8747 MB (0%) D c State: up Device /dev/da2s1h Avail: 0/8747 MB (0%) D b State: up Device /dev/da3s1h Avail: 0/8747 MB (0%) D a State: up Device /dev/da4s1h Avail: 0/8747 MB (0%) 1 volumes: V raid State: down Plexes: 1 Size: 25 GB 1 plexes: P raid.p0R5 State: init Subdisks: 4 Size: 25 GB 4 subdisks: S raid.p0.s0State: emptyPO:0 B Size: 8747 MB S raid.p0.s1State: emptyPO: 512 kB Size: 8747 MB S raid.p0.s2State: emptyPO: 1024 kB Size: 8747 MB S raid.p0.s3State: emptyPO: 1536 kB Size: 8747 MB This doesn't agree with what you say above. It also looks fine to me. My apologies, Greg. Quite right. I was messing with the system right before the response about sa4 device nodes in /dev. Once I made the da4 devices, then the disklabel worked. My mistake jumping the gun. One follow-up question if I may. I assume that the init process for a RAID5 takes quite some time, no? This has been in the init stage for 3 days. The vinum daemon is running as I can see it listed in ps -ax. This is the init state, which means it needs initializing. To initialize, issue the 'init' command. The state will change from 'init' to 'initializing', and the list command shows the progress of the initialization. This writes zeroes to the drives in parallel; expect it to take an hour or two on drives of this size. Greg -- Thanks Greg, that did the trick. The initialization only took 19 minutes. The newfs took about 5 minutes, and it is now running perfectly. Thank you again. Bob -- Bob Collins Anything-inc.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disklabel problem IBM SCSI3 disks, vinum too
At 07:30 PM 11/21/2003, you wrote: [Format recovered--see http://www.lemis.com/email/email-format.html] Quotation broken. On Friday, 21 November 2003 at 9:25:58 -0500, Bob Collins wrote: At 08:41 PM 11/19/2003, Greg 'groggy' Lehey wrote: [Format recovered--see http://www.lemis.com/email/email-format.html] Quotation broken. On Wednesday, 19 November 2003 at 9:13:43 -0500, Bob Collins wrote: At 10:46 PM 11/17/2003, Greg 'groggy' Lehey wrote: Do you have device nodes for da4? Has it been labelled at all? I did not have `all' the nodes for da4 in /dev. So, I ran #sh MAKEDEV da4 in the /dev directory. After that, there were what appeared to be all the device nodes for da4. I was able to label the drive and use it with vinum under 5.0-RELEASE FWIW. Under 4.9-RELEASE (which is what I now run) it will not label through /stand/sysinstall. I can now newfs the drive and mount it and copy files to and fro, however I cannot use it with vinum. I did umount the drive and then disklabel -e da4 and changed the e: to h: and the filesystem type to vinum. It was da4s1e. When I create the vinum configuration, I either get that drive d (da4s1h) is referenced and in the down state while the other three drives are up, or the other three drives a b c are referenced and in the down state while drive d is up. I need the information I ask for in http://www.vinumvm.org/vinum/how-to-debug.html. FreeBSD 4.9 RELEASE No changes to sources vinum - list 4 drives: D d State: up Device /dev/da1s1h Avail: 0/8747 MB (0%) D c State: up Device /dev/da2s1h Avail: 0/8747 MB (0%) D b State: up Device /dev/da3s1h Avail: 0/8747 MB (0%) D a State: up Device /dev/da4s1h Avail: 0/8747 MB (0%) 1 volumes: V raid State: down Plexes: 1 Size: 25 GB 1 plexes: P raid.p0R5 State: init Subdisks: 4 Size: 25 GB 4 subdisks: S raid.p0.s0State: emptyPO:0 B Size: 8747 MB S raid.p0.s1State: emptyPO: 512 kB Size: 8747 MB S raid.p0.s2State: emptyPO: 1024 kB Size: 8747 MB S raid.p0.s3State: emptyPO: 1536 kB Size: 8747 MB This doesn't agree with what you say above. It also looks fine to me. Greg -- My apologies, Greg. Quite right. I was messing with the system right before the response about sa4 device nodes in /dev. Once I made the da4 devices, then the disklabel worked. My mistake jumping the gun. One follow-up question if I may. I assume that the init process for a RAID5 takes quite some time, no? This has been in the init stage for 3 days. The vinum daemon is running as I can see it listed in ps -ax. Thank you Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disklabel problem IBM SCSI3 disks, vinum too
[Format recovered--see http://www.lemis.com/email/email-format.html] Single-line paragraphs. On Sunday, 23 November 2003 at 13:03:47 -0500, Bob Collins wrote: At 07:30 PM 11/21/2003, you wrote: On Friday, 21 November 2003 at 9:25:58 -0500, Bob Collins wrote: vinum - list 4 drives: D d State: up Device /dev/da1s1h Avail: 0/8747 MB (0%) D c State: up Device /dev/da2s1h Avail: 0/8747 MB (0%) D b State: up Device /dev/da3s1h Avail: 0/8747 MB (0%) D a State: up Device /dev/da4s1h Avail: 0/8747 MB (0%) 1 volumes: V raid State: down Plexes: 1 Size: 25 GB 1 plexes: P raid.p0R5 State: init Subdisks: 4 Size: 25 GB 4 subdisks: S raid.p0.s0State: emptyPO:0 B Size: 8747 MB S raid.p0.s1State: emptyPO: 512 kB Size: 8747 MB S raid.p0.s2State: emptyPO: 1024 kB Size: 8747 MB S raid.p0.s3State: emptyPO: 1536 kB Size: 8747 MB This doesn't agree with what you say above. It also looks fine to me. My apologies, Greg. Quite right. I was messing with the system right before the response about sa4 device nodes in /dev. Once I made the da4 devices, then the disklabel worked. My mistake jumping the gun. One follow-up question if I may. I assume that the init process for a RAID5 takes quite some time, no? This has been in the init stage for 3 days. The vinum daemon is running as I can see it listed in ps -ax. This is the init state, which means it needs initializing. To initialize, issue the 'init' command. The state will change from 'init' to 'initializing', and the list command shows the progress of the initialization. This writes zeroes to the drives in parallel; expect it to take an hour or two on drives of this size. 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. pgp0.pgp Description: PGP signature
Re: Disklabel problem IBM SCSI3 disks, vinum too
At 08:41 PM 11/19/2003, Greg 'groggy' Lehey wrote: [Format recovered--see http://www.lemis.com/email/email-format.html] Quotation broken. On Wednesday, 19 November 2003 at 9:13:43 -0500, Bob Collins wrote: At 10:46 PM 11/17/2003, Greg 'groggy' Lehey wrote: Do you have device nodes for da4? Has it been labelled at all? I did not have `all' the nodes for da4 in /dev. So, I ran #sh MAKEDEV da4 in the /dev directory. After that, there were what appeared to be all the device nodes for da4. I was able to label the drive and use it with vinum under 5.0-RELEASE FWIW. Under 4.9-RELEASE (which is what I now run) it will not label through /stand/sysinstall. I can now newfs the drive and mount it and copy files to and fro, however I cannot use it with vinum. I did umount the drive and then disklabel -e da4 and changed the e: to h: and the filesystem type to vinum. It was da4s1e. When I create the vinum configuration, I either get that drive d (da4s1h) is referenced and in the down state while the other three drives are up, or the other three drives a b c are referenced and in the down state while drive d is up. I need the information I ask for in http://www.vinumvm.org/vinum/how-to-debug.html. 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. FreeBSD 4.9 RELEASE No changes to sources vinum - list 4 drives: D d State: up Device /dev/da1s1h Avail: 0/8747 MB (0%) D c State: up Device /dev/da2s1h Avail: 0/8747 MB (0%) D b State: up Device /dev/da3s1h Avail: 0/8747 MB (0%) D a State: up Device /dev/da4s1h Avail: 0/8747 MB (0%) 1 volumes: V raid State: down Plexes: 1 Size: 25 GB 1 plexes: P raid.p0R5 State: init Subdisks: 4 Size: 25 GB 4 subdisks: S raid.p0.s0State: emptyPO:0 B Size: 8747 MB S raid.p0.s1State: emptyPO: 512 kB Size: 8747 MB S raid.p0.s2State: emptyPO: 1024 kB Size: 8747 MB S raid.p0.s3State: emptyPO: 1536 kB Size: 8747 MB 18 Nov 2003 21:03:29.947426 *** vinum started *** 18 Nov 2003 21:03:29.948250 *** Created devices *** 18 Nov 2003 21:03:30.242946 create -f /etc/vinum.conf # Vinum configuration of freebie, Wed Nov 13 drive /dev/a device /dev/da1s1h drive /dev/b device /dev/da2s1h drive /dev/c device /dev/da3s1h drive /dev/d device /dev/da4s1h volume raid plex org raid5 512k sd len 8747m drive /dev/a sd len 8747m drive /dev/b sd len 8747m drive /dev/c sd len 8747m drive /dev/d 18 Nov 2003 21:03:30.407281 *** Created devices *** 18 Nov 2003 21:03:29.948250 *** Created devices *** Nov 18 21:03:24 freebie /kernel: vinum: loaded Nov 18 21:03:30 freebie /kernel: vinum: drive /dev/a is up Nov 18 21:03:30 freebie /kernel: vinum: drive /dev/b is up Nov 18 21:03:30 freebie /kernel: vinum: drive /dev/c is up Nov 18 21:03:30 freebie /kernel: vinum: raid.p0.s3 is crashed Nov 18 21:03:30 freebie /kernel: vinum: raid.p0 is initializing Nov 18 21:03:24 freebie /kernel: vinum: loaded Nov 18 21:03:30 freebie /kernel: vinum: drive /dev/a is up Nov 18 21:03:30 freebie /kernel: vinum: drive /dev/b is up Nov 18 21:03:30 freebie /kernel: vinum: drive /dev/c is up Nov 18 21:03:30 freebie /kernel: vinum: raid.p0.s3 is crashed Nov 18 21:03:30 freebie /kernel: vinum: raid.p0 is initializing ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disklabel problem IBM SCSI3 disks, vinum too
[Format recovered--see http://www.lemis.com/email/email-format.html] Quotation broken. On Friday, 21 November 2003 at 9:25:58 -0500, Bob Collins wrote: At 08:41 PM 11/19/2003, Greg 'groggy' Lehey wrote: [Format recovered--see http://www.lemis.com/email/email-format.html] Quotation broken. On Wednesday, 19 November 2003 at 9:13:43 -0500, Bob Collins wrote: At 10:46 PM 11/17/2003, Greg 'groggy' Lehey wrote: Do you have device nodes for da4? Has it been labelled at all? I did not have `all' the nodes for da4 in /dev. So, I ran #sh MAKEDEV da4 in the /dev directory. After that, there were what appeared to be all the device nodes for da4. I was able to label the drive and use it with vinum under 5.0-RELEASE FWIW. Under 4.9-RELEASE (which is what I now run) it will not label through /stand/sysinstall. I can now newfs the drive and mount it and copy files to and fro, however I cannot use it with vinum. I did umount the drive and then disklabel -e da4 and changed the e: to h: and the filesystem type to vinum. It was da4s1e. When I create the vinum configuration, I either get that drive d (da4s1h) is referenced and in the down state while the other three drives are up, or the other three drives a b c are referenced and in the down state while drive d is up. I need the information I ask for in http://www.vinumvm.org/vinum/how-to-debug.html. FreeBSD 4.9 RELEASE No changes to sources vinum - list 4 drives: D d State: up Device /dev/da1s1h Avail: 0/8747 MB (0%) D c State: up Device /dev/da2s1h Avail: 0/8747 MB (0%) D b State: up Device /dev/da3s1h Avail: 0/8747 MB (0%) D a State: up Device /dev/da4s1h Avail: 0/8747 MB (0%) 1 volumes: V raid State: down Plexes: 1 Size: 25 GB 1 plexes: P raid.p0R5 State: init Subdisks: 4 Size: 25 GB 4 subdisks: S raid.p0.s0State: emptyPO:0 B Size: 8747 MB S raid.p0.s1State: emptyPO: 512 kB Size: 8747 MB S raid.p0.s2State: emptyPO: 1024 kB Size: 8747 MB S raid.p0.s3State: emptyPO: 1536 kB Size: 8747 MB This doesn't agree with what you say above. It also looks fine to me. 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. pgp0.pgp Description: PGP signature
Re: Disklabel problem IBM SCSI3 disks, vinum too
At 10:46 PM 11/17/2003, Greg 'groggy' Lehey wrote: On Friday, 14 November 2003 at 11:50:09 -0500, Bob Collins wrote: Running FBSD 4.9 on an Intel SMP mobo w/ 2 Intel PII 350s. Onboard SCSI is recognized and sees all my drives. One SCSI 3 drive is 4.5G for the OS and /usr. I have 4 identical IBM SCSI3 disks 9G each, however one of those 4 will not disklabel. The other three will. This leads to troubles then, obviously, to setting the 4 drives for vinum use. Was using these 4 drives on 5.0-RELEASE with vinum previously no troublesdowngraded for some backup software (bacula) compatibility reasons. In dmesg, da1, da2, da3, da4 all show as identical drives, model number, capacity, etc. I have not removed the drive to see if there is a special jumper to protect such things, I shall do this later today. When I try to `disklabel -e da4', I get the info open, I can change whatever I like, then when I save the file it complains; that the device does not support this feature. The other 3 drives all did `disklabel -e dax' with no trouble. Do you have device nodes for da4? Has it been labelled at all? Greg -- I did not have `all' the nodes for da4 in /dev. So, I ran #sh MAKEDEV da4 in the /dev directory. After that, there were what appeared to be all the device nodes for da4. I was able to label the drive and use it with vinum under 5.0-RELEASE FWIW. Under 4.9-RELEASE (which is what I now run) it will not label through /stand/sysinstall. I can now newfs the drive and mount it and copy files to and fro, however I cannot use it with vinum. I did umount the drive and then disklabel -e da4 and changed the e: to h: and the filesystem type to vinum. It was da4s1e. When I create the vinum configuration, I either get that drive d (da4s1h) is referenced and in the down state while the other three drives are up, or the other three drives a b c are referenced and in the down state while drive d is up. Thank you. Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disklabel problem IBM SCSI3 disks, vinum too
[Format recovered--see http://www.lemis.com/email/email-format.html] Quotation broken. On Wednesday, 19 November 2003 at 9:13:43 -0500, Bob Collins wrote: At 10:46 PM 11/17/2003, Greg 'groggy' Lehey wrote: Do you have device nodes for da4? Has it been labelled at all? I did not have `all' the nodes for da4 in /dev. So, I ran #sh MAKEDEV da4 in the /dev directory. After that, there were what appeared to be all the device nodes for da4. I was able to label the drive and use it with vinum under 5.0-RELEASE FWIW. Under 4.9-RELEASE (which is what I now run) it will not label through /stand/sysinstall. I can now newfs the drive and mount it and copy files to and fro, however I cannot use it with vinum. I did umount the drive and then disklabel -e da4 and changed the e: to h: and the filesystem type to vinum. It was da4s1e. When I create the vinum configuration, I either get that drive d (da4s1h) is referenced and in the down state while the other three drives are up, or the other three drives a b c are referenced and in the down state while drive d is up. I need the information I ask for in http://www.vinumvm.org/vinum/how-to-debug.html. 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. pgp0.pgp Description: PGP signature
Re: Disklabel problem IBM SCSI3 disks, vinum too
On Friday, 14 November 2003 at 11:50:09 -0500, Bob Collins wrote: Running FBSD 4.9 on an Intel SMP mobo w/ 2 Intel PII 350s. Onboard SCSI is recognized and sees all my drives. One SCSI 3 drive is 4.5G for the OS and /usr. I have 4 identical IBM SCSI3 disks 9G each, however one of those 4 will not disklabel. The other three will. This leads to troubles then, obviously, to setting the 4 drives for vinum use. Was using these 4 drives on 5.0-RELEASE with vinum previously no troublesdowngraded for some backup software (bacula) compatibility reasons. In dmesg, da1, da2, da3, da4 all show as identical drives, model number, capacity, etc. I have not removed the drive to see if there is a special jumper to protect such things, I shall do this later today. When I try to `disklabel -e da4', I get the info open, I can change whatever I like, then when I save the file it complains; that the device does not support this feature. The other 3 drives all did `disklabel -e dax' with no trouble. Do you have device nodes for da4? Has it been labelled at all? 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. pgp0.pgp Description: PGP signature
Re: disklabel problem
hello i am trying to add some more hd space to my system. I have an extra disk wich is /dev/sda0s2. I used disklabel to partition it into seven partitions. Now i want to insert these partitions to my system, but i can not find all the device files /dev/sda0s2a - /dev/sda0s2h By default, only a subset of devices are already made. Presuming you are using a versin of FreeBSD before 5.0 (I haven't had a chance to install a 5.x or use the new devfs stuff yet) do the following: cd /dev ./MAKEDEV da0s2a That should get you all the da0s2_ set. Then fix up your /etc/fstab file and it should all work nicely. jerry But disklabel -r /dev/da0s2 shows me # /dev/da0s2: type: SCSI disk: da0s2 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 53400 sectors/unit: 857887002 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] a: 12255528604.2BSD0 0 0 # (Cyl.0 - 7628*) b: 122555286 1225552864.2BSD0 0 0 # (Cyl. 7628*- 15257*) c: 8578870020unused0 0# (Cyl.0 - 53400*) d: 122555286 2451105724.2BSD0 0 0 # (Cyl. 15257*- 22886*) e: 122555286 3676658584.2BSD0 0 0 # (Cyl. 22886*- 30514*) f: 122555286 4902211444.2BSD0 0 0 # (Cyl. 30514*- 38143*) g: 122555286 6127764304.2BSD0 0 0 # (Cyl. 38143*- 45772*) h: 122555286 7353317164.2BSD0 0 0 # (Cyl. 45772*- 53400*) and an ls /dev/da0s2* shows me only : /dev/da0s2 My question is, how do i get the device files for all my partitions, because without them i can not use newfs. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
