Re: Can't fdisk newly installed disks
Jerry McAllister wrote: On Mon, Aug 13, 2007 at 05:38:04PM -0700, Simon Gao wrote: Hi, I am running into some problem with fdisk newly installed drives. From boot message, these drives are found without problem: da3 at mpt0 bus 0 target 2 lun 0 da3: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da3: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da3: 2048000MB (4194304000 512 byte sectors: 255H 63S/T 261083C) da4 at mpt0 bus 0 target 2 lun 1 da4: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da4: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da4: 2048000MB (4194304000 512 byte sectors: 255H 63S/T 261083C) da5 at mpt0 bus 0 target 2 lun 2 da5: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da5: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da5: 670790MB (1373777920 512 byte sectors: 255H 63S/T 85513C) There are device files in /dev: crw-r- 1 root operator4, 14 Aug 13 17:14 /dev/da3 crw-r- 1 root operator4, 15 Aug 13 17:14 /dev/da4 crw-r- 1 root operator4, 16 Aug 13 17:14 /dev/da5 However, when trying to fdisk one of drives, I got following error: # fdisk -BI da5 fdisk: cannot open disk /dev/da5: No such file or directory sysintall failed also. The system runs FreeBSD 5.2.1-RELEASE. Any help is appreciated. Did you try doing a dd(1) if some blocks of zeros to the drive before doing the fdisk.On some older FreeBSD - don't remember which - I had trouble with some brands of SCSI disks and writing some zeros to it seemed to make it work. I don't know why or even why I first tried it. But it is simple enough to be worth giving it a try to see if anything improves. dd if=/devf/zero of=/dev/da5 bs=512 count=1024 jerry This is what I got: # dd if=/dev/zero of=/dev/da5 bs=512 count=1024 dd: /dev/da5: Operation not permitted If I use sysinstall -- config -- fdisk to partition /dev/da5, I got following warning: WARNING: A geometry of 85513/255/63 for da5 is incorrect. Using │ │a more likely geometry. If this geometry is incorrect or you │ │are unsure as to whether or not it's correct, please consult │ │the Hardware Guide in the Documentation submenu or use the │ │(G)eometry command to change it now. │ │ │ │Remember: you need to enter whatever your BIOS thinks the │ │geometry is! For IDE, it's what you were told in the BIOS │ │setup. For SCSI, it's the translation mode your controller is │ │using. Do NOT use a ``physical geometry''. The cylinder, heads and sectors match what's found during boot up. Simon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't fdisk newly installed disks
does anything else works. like dd if=/dev/disk of=/dev/null bs=1m count=1 On Mon, 13 Aug 2007, Simon Gao wrote: Hi, I am running into some problem with fdisk newly installed drives. From boot message, these drives are found without problem: da3 at mpt0 bus 0 target 2 lun 0 da3: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da3: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da3: 2048000MB (4194304000 512 byte sectors: 255H 63S/T 261083C) da4 at mpt0 bus 0 target 2 lun 1 da4: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da4: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da4: 2048000MB (4194304000 512 byte sectors: 255H 63S/T 261083C) da5 at mpt0 bus 0 target 2 lun 2 da5: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da5: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da5: 670790MB (1373777920 512 byte sectors: 255H 63S/T 85513C) There are device files in /dev: crw-r- 1 root operator4, 14 Aug 13 17:14 /dev/da3 crw-r- 1 root operator4, 15 Aug 13 17:14 /dev/da4 crw-r- 1 root operator4, 16 Aug 13 17:14 /dev/da5 However, when trying to fdisk one of drives, I got following error: # fdisk -BI da5 fdisk: cannot open disk /dev/da5: No such file or directory sysintall failed also. The system runs FreeBSD 5.2.1-RELEASE. Any help is appreciated. Simon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't fdisk newly installed disks
On 13/08/07, Simon Gao [EMAIL PROTECTED] wrote: Hi, I am running into some problem with fdisk newly installed drives. . . . # fdisk -BI da5 fdisk: cannot open disk /dev/da5: No such file or directory What is your securelevel? For example: % sysctl kern.securelevel kern.securelevel: -1 man init for more about securelevels. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't fdisk newly installed disks
On Mon, Aug 13, 2007 at 11:32:40PM -0700, Simon Gao wrote: Jerry McAllister wrote: On Mon, Aug 13, 2007 at 05:38:04PM -0700, Simon Gao wrote: Hi, I am running into some problem with fdisk newly installed drives. From boot message, these drives are found without problem: da3 at mpt0 bus 0 target 2 lun 0 da3: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da3: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da3: 2048000MB (4194304000 512 byte sectors: 255H 63S/T 261083C) da4 at mpt0 bus 0 target 2 lun 1 da4: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da4: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da4: 2048000MB (4194304000 512 byte sectors: 255H 63S/T 261083C) da5 at mpt0 bus 0 target 2 lun 2 da5: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da5: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da5: 670790MB (1373777920 512 byte sectors: 255H 63S/T 85513C) There are device files in /dev: crw-r- 1 root operator4, 14 Aug 13 17:14 /dev/da3 crw-r- 1 root operator4, 15 Aug 13 17:14 /dev/da4 crw-r- 1 root operator4, 16 Aug 13 17:14 /dev/da5 However, when trying to fdisk one of drives, I got following error: # fdisk -BI da5 fdisk: cannot open disk /dev/da5: No such file or directory sysintall failed also. The system runs FreeBSD 5.2.1-RELEASE. Any help is appreciated. Did you try doing a dd(1) if some blocks of zeros to the drive before doing the fdisk.On some older FreeBSD - don't remember which - I had trouble with some brands of SCSI disks and writing some zeros to it seemed to make it work. I don't know why or even why I first tried it. But it is simple enough to be worth giving it a try to see if anything improves. dd if=/devf/zero of=/dev/da5 bs=512 count=1024 jerry This is what I got: # dd if=/dev/zero of=/dev/da5 bs=512 count=1024 dd: /dev/da5: Operation not permitted OK. sorry that didn't help. If I use sysinstall -- config -- fdisk to partition /dev/da5, I got following warning: WARNING: A geometry of 85513/255/63 for da5 is incorrect. Using ??? ???a more likely geometry. If this geometry is incorrect or you ??? ???are unsure as to whether or not it's correct, please consult ??? ???the Hardware Guide in the Documentation submenu or use the ??? ???(G)eometry command to change it now. ??? ??? ??? ???Remember: you need to enter whatever your BIOS thinks the ??? ???geometry is! For IDE, it's what you were told in the BIOS ??? ???setup. For SCSI, it's the translation mode your controller is ??? ???using. Do NOT use a ``physical geometry''. The cylinder, heads and sectors match what's found during boot up. Simon I am sure it has nothing to do with those geometry messages. I always get them and never have had to do anything about it. So, back to square n where n=don't know. Hopefully someone else will have something useful to say. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't fdisk newly installed disks
[EMAIL PROTECTED] wrote: On 13/08/07, Simon Gao [EMAIL PROTECTED] wrote: Hi, I am running into some problem with fdisk newly installed drives. . . . # fdisk -BI da5 fdisk: cannot open disk /dev/da5: No such file or directory What is your securelevel? For example: % sysctl kern.securelevel kern.securelevel: -1 man init for more about securelevels. # sysctl kern.securelevel kern.securelevel: 3 Does higher security level prevent one from adding new file system? Simon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't fdisk newly installed disks
Wojciech Puchar wrote: does anything else works. like dd if=/dev/disk of=/dev/null bs=1m count=1 Yes. # dd if=/dev/da5 of=/dev/null bs=1m count=1 1+0 records in 1+0 records out 1048576 bytes transferred in 0.155479 secs (6744167 bytes/sec) On Mon, 13 Aug 2007, Simon Gao wrote: Hi, I am running into some problem with fdisk newly installed drives. From boot message, these drives are found without problem: da3 at mpt0 bus 0 target 2 lun 0 da3: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da3: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da3: 2048000MB (4194304000 512 byte sectors: 255H 63S/T 261083C) da4 at mpt0 bus 0 target 2 lun 1 da4: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da4: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da4: 2048000MB (4194304000 512 byte sectors: 255H 63S/T 261083C) da5 at mpt0 bus 0 target 2 lun 2 da5: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da5: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da5: 670790MB (1373777920 512 byte sectors: 255H 63S/T 85513C) There are device files in /dev: crw-r- 1 root operator4, 14 Aug 13 17:14 /dev/da3 crw-r- 1 root operator4, 15 Aug 13 17:14 /dev/da4 crw-r- 1 root operator4, 16 Aug 13 17:14 /dev/da5 However, when trying to fdisk one of drives, I got following error: # fdisk -BI da5 fdisk: cannot open disk /dev/da5: No such file or directory sysintall failed also. The system runs FreeBSD 5.2.1-RELEASE. Any help is appreciated. Simon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't fdisk newly installed disks
On Tue, Aug 14, 2007 at 11:48:29AM -0700, Simon Gao wrote: [EMAIL PROTECTED] wrote: On 13/08/07, Simon Gao [EMAIL PROTECTED] wrote: Hi, I am running into some problem with fdisk newly installed drives. . . . # fdisk -BI da5 fdisk: cannot open disk /dev/da5: No such file or directory What is your securelevel? For example: % sysctl kern.securelevel kern.securelevel: -1 man init for more about securelevels. # sysctl kern.securelevel kern.securelevel: 3 Does higher security level prevent one from adding new file system? It can prevent you from making almost any changes. A secure level of 3 is very high and may be what you want for your production - depending on what you are doing, but will make any installation or development very difficult or impossible. jerry Simon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't fdisk newly installed disks
Jerry McAllister wrote: On Tue, Aug 14, 2007 at 11:48:29AM -0700, Simon Gao wrote: [EMAIL PROTECTED] wrote: On 13/08/07, Simon Gao [EMAIL PROTECTED] wrote: Hi, I am running into some problem with fdisk newly installed drives. . . . # fdisk -BI da5 fdisk: cannot open disk /dev/da5: No such file or directory What is your securelevel? For example: % sysctl kern.securelevel kern.securelevel: -1 man init for more about securelevels. # sysctl kern.securelevel kern.securelevel: 3 Does higher security level prevent one from adding new file system? It can prevent you from making almost any changes. A secure level of 3 is very high and may be what you want for your production - depending on what you are doing, but will make any installation or development very difficult or impossible. jerry Thanks, Jerry. I tried to lower secure level, but still run into similar error: # sysctl kern.securelevel=-1 kern.securelevel: 3 sysctl: kern.securelevel: Operation not permitted Is there other way to reduce secure level to -1 without reboot the machine or drop into single user mode? Simon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't fdisk newly installed disks
Simon Gao writes: Is there other way to reduce secure level to -1 without reboot the machine or drop into single user mode? As I understand it: no. And that's a carefully considered choice. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't fdisk newly installed disks
Jerry McAllister wrote: It can prevent you from making almost any changes. A secure level of 3 is very high and may be what you want for your production - depending on what you are doing, but will make any installation or development very difficult or impossible. jerry That's it. A secure level of 3 setting was the problem. Once changed secure level to -1, everything worked. Thanks. Simon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Can't fdisk newly installed disks
Hi, I am running into some problem with fdisk newly installed drives. From boot message, these drives are found without problem: da3 at mpt0 bus 0 target 2 lun 0 da3: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da3: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da3: 2048000MB (4194304000 512 byte sectors: 255H 63S/T 261083C) da4 at mpt0 bus 0 target 2 lun 1 da4: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da4: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da4: 2048000MB (4194304000 512 byte sectors: 255H 63S/T 261083C) da5 at mpt0 bus 0 target 2 lun 2 da5: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da5: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da5: 670790MB (1373777920 512 byte sectors: 255H 63S/T 85513C) There are device files in /dev: crw-r- 1 root operator4, 14 Aug 13 17:14 /dev/da3 crw-r- 1 root operator4, 15 Aug 13 17:14 /dev/da4 crw-r- 1 root operator4, 16 Aug 13 17:14 /dev/da5 However, when trying to fdisk one of drives, I got following error: # fdisk -BI da5 fdisk: cannot open disk /dev/da5: No such file or directory sysintall failed also. The system runs FreeBSD 5.2.1-RELEASE. Any help is appreciated. Simon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't fdisk newly installed disks
On Mon, Aug 13, 2007 at 05:38:04PM -0700, Simon Gao wrote: Hi, I am running into some problem with fdisk newly installed drives. From boot message, these drives are found without problem: da3 at mpt0 bus 0 target 2 lun 0 da3: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da3: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da3: 2048000MB (4194304000 512 byte sectors: 255H 63S/T 261083C) da4 at mpt0 bus 0 target 2 lun 1 da4: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da4: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da4: 2048000MB (4194304000 512 byte sectors: 255H 63S/T 261083C) da5 at mpt0 bus 0 target 2 lun 2 da5: IFT A12U-G2421 347D Fixed Direct Access SCSI-3 device da5: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da5: 670790MB (1373777920 512 byte sectors: 255H 63S/T 85513C) There are device files in /dev: crw-r- 1 root operator4, 14 Aug 13 17:14 /dev/da3 crw-r- 1 root operator4, 15 Aug 13 17:14 /dev/da4 crw-r- 1 root operator4, 16 Aug 13 17:14 /dev/da5 However, when trying to fdisk one of drives, I got following error: # fdisk -BI da5 fdisk: cannot open disk /dev/da5: No such file or directory sysintall failed also. The system runs FreeBSD 5.2.1-RELEASE. Any help is appreciated. Did you try doing a dd(1) if some blocks of zeros to the drive before doing the fdisk.On some older FreeBSD - don't remember which - I had trouble with some brands of SCSI disks and writing some zeros to it seemed to make it work. I don't know why or even why I first tried it. But it is simple enough to be worth giving it a try to see if anything improves. dd if=/devf/zero of=/dev/da5 bs=512 count=1024 jerry Simon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't fdisk newly installed disks
On Mon, 13 Aug 2007, Simon Gao wrote: [snip] The system runs FreeBSD 5.2.1-RELEASE. Have you considered updating to something a little less long in the tooth? 5.2.1 hasn't been officially supported for some time now, and these problems may have been solved in the last three years. Just saying. -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging | ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
