RE: Can't add new 1TB disk in FreeBSD 6.1
> > The hardware I have is the built in SATA controller on the > > motherboard, which is GIGABYTE GA-M61P-S3. With the NVIDIA GeForce > > 6100 / nForce 430 and Super I/O chip: ITE IT8716. > > > > Oct 4 04:07:30 kermit kernel: atapci0: controller> port > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on > > pci0 Oct 4 04:07:30 kermit kernel: ata0: > on atapci0 > > Oct 4 04:07:30 kermit kernel: ata1: on > atapci0 Oct 4 > > 04:07:30 kermit kernel: pci0: at device 7.0 (no driver > > attached) Oct 4 04:07:30 kermit kernel: atapci1: > controller> port > > 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd000-0xd00f mem > > 0xf7004000-0xf7004fff irq 20 at device 8.0 on pci0 Oct 4 04:07:30 > > kermit kernel: ata2: on atapci1 Oct 4 > 04:07:30 kermit > > kernel: ata3: on atapci1 Oct 4 04:07:30 kermit > > kernel: atapci2: port > > 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xe400-0xe40f mem > > 0xf700-0xf7000fff irq 21 at device 8.1 on pci0 Oct 4 04:07:30 > > kermit kernel: ata4: on atapci2 Oct 4 > 04:07:30 kermit > > kernel: ata5: on atapci2 Oct 4 04:07:30 kermit > > kernel: ad0: 76293MB at > ata0-master UDMA33 > > Oct 4 04:07:30 kermit kernel: ad4: 953869MB > SD15> at ata2-master UDMA33 > > This motherboard uses the nForce 430, but the SATA portion is > actually a subset chip called the MCP61. I've confirmed this > by looking at PRs 116880 and 108830. > > I can see two things from the dmesg: > > 1) FreeBSD has no idea what this controller is, or any "quirks" > surrounding the controller (meaning it's possible that disk > or block addressing is being done incorrectly), > > 2) The disks are seen as classic PATA disks and not SATA. > This could be a result of there being no nForce 430 support > in 6.1, but it could also be due to a BIOS setting on that > motherboard. > > I'm looking at the User Manual for this motherboard, but I > can't find the BIOS option that I'm used to seeing on other > nForce-based boards, and Intel ICH-based boards: > > A feature where you can change the way the OS sees the > underlying SATA controller; it's called "Emulated" or > "Emulation" mode. The controller is able to interface with > SATA disks, but the OS sees the controller as a classic > PATA/IDE controller. This is often used for OSes which lack > SATA support or native SATA drivers, such as MS-DOS. > > The only thing in the User Manual I see which sets off red > flags is the "Serial-ATA RAID Config" item under the > Integrated Peripherals menu. I really hope the "NV SATA Raid > Function" is set to Disabled on your box. > > Looking at CVS commit logs for src/sys/dev/ata/ata-chipset.c, > I can see that MCP61 support was officially added to HEAD on > on 2007/06/26. I'm having a difficult time determining what > HEAD meant at that date. I can't figure out for the life of > me if it was referring to RELENG_6 or RELENG_7. > > Either way, point is, FreeBSD 6.1 flat out does not have > support for that chip, even a 6.1 dated August 2006. I can't > help but wonder if that's what's causing the odd problem. > > I also found another LBA48-related issue, dated 2007/10/04, > labelled "fix the LBA28/LBA48 crossover bug". I'm still not > sure what that is. > > And I haven't even begun to look at GEOM changes/bugfixes, > which might be a more likely place. > > > This is actually a FreeBSD-Stable install... From 08/2006 I > > realize it's probably time to do an OS upgrade, but this is > the ONLY > > issue I've run into running this code base. Some of the > software I'm > > running hasn't been tested with 7.X, so I'm not comfortable > going there yet. > > What this means is that it's a 6.1-RELEASE install which follows the > RELENG_6 tag, and has been cvsup'd at least up until August 2006. > > I understand you're not comfortable upgrading to FreeBSD 7, > but it would be worthwhile if you could download FreeBSD > 7.1-PRERELEASE (specifically disc 1 or a live CD), and see if > that reports the same problem as 6.1. > > I still can't explain why booting the 6.1 installer and using > a fixit image lets you work around the problem. That is just > flat out bizarre. > > You have to understand: there's been a lot of > evolution/bugfixes applied between 6.1 and 7.1. There's > almost too much for me to try and track down. I'm trying > very hard, but it's difficult. Thanks for all the clarifications, I didn't realize there have been that many changes since 6.1. I suppose its time to upgrade. What I need to do is build an identical server to that one and test it all out locally. Since the drive is currently 500 miles away it will take me some time, but I'll see what I can do. I'll also check my BIOS settings to make sure the RAID is disabled. I'm almost positive it is, but who knows. Jerry pointed out that the boot process is seeing it as a regular ATA device, so it may be running in some sort of compatibility mode li
Re: Can't add new 1TB disk in FreeBSD 6.1
On Mon, Oct 06, 2008 at 11:08:34AM -0700, Don O'Neil wrote:
> > On Mon, Oct 06, 2008 at 09:45:52AM -0700, Jeremy Chadwick wrote:
> > > There is one thing about later FreeBSDs which I am aware of: 48-bit
> > > LBA addressing. I'm left wondering if what you're running
> > into is a
> > > bug or a problem with older FreeBSD (6.1) not supporting this. I
> > > would have to go back through CVS commit lots for ata(4) to
> > find out
> > > when 48-bit LBA was added. I think 48-bit LBA support is
> > required for disks >500GB.
> >
> > The issue I'm referring to has been touched on many times.
> >
> > First and foremost, 6.1-RELEASE was released in May 2006.
> > Keep that date in mind when reading the below.
> >
> > The first incident, according to CVS commit logs, was adding
> > 48-bit LBA support, supporting disks >137GB. That would've
> > been in RELENG_4, dated 2002/01/05. FreeBSD 6.1 should have this.
> >
> > Next, we have a commit dated 2003/01/19, affecting 48-bit LBA
> > support on Promise 66/100 controllers. FreeBSD 6.1 should have this.
> >
> > Next, 2004/12/09, talking about disk firmware bugs affecting
> > 48-bit LBA addressing, which was affecting a significant
> > number of users. That was applied to HEAD and RELENG_5, so
> > FreeBSD 6.1 ("HEAD" at that time) should have this.
> >
> > Next, 2005/04/14, something about "read back the real
> > taskfile register values when in 48-bit mode". Committed to
> > HEAD, which would've been during days shortly before RELENG_6
> > was tagged (6.0).
> >
> > Next, 2005/08/17, "support for working around controllers
> > that can't do DMA in 48-bit LBA mode", forcing the disk to
> > use PIO mode allowing the disk to address >137GB. This was
> > added to HEAD and RELENG_6, so this should also exist in 6.1.
> >
> > Next, 2007/12/13, "also fix 48-bit LBA addressing issues,
> > apparently newe chips need 16-bit writes and not the usual
> > FIFO thing". This was committed to HEAD first, RELENG_7 on
> > 2008/01/09, and RELENG_6 on 2008/01/09.
> >
> > This is one which FreeBSD 6.1 *would not* have fixes for.
> >
> > I do not know if this is the problem -- I'm just speculating.
> >
> > Because dmesg output was not provided ("nothing
> > interesting"), we can't tell what sort of controller your
> > disks are hooked to, yadda yadda.
> > This is explicitly why I asked for that information.
> >
> > If you could please try 7.0-STABLE or 7.1-PRERELEASE, that
> > would be highly recommended. It would at least allow us to
> > determine if you're being affected by a bug in older FreeBSD,
> > or if this is something that is unique to your environment or
> > applies to present-day FreeBSD.
>
> The hardware I have is the built in SATA controller on the motherboard,
> which is GIGABYTE GA-M61P-S3. With the NVIDIA GeForce 6100 / nForce 430 and
> Super I/O chip: ITE IT8716.
>
> Dmesg had no output pertaining to the partition/format/dd, etc... Just
> messages from my ftp daemon. If you're wanting to see the boot messages,
> this is from the last time I rebooted when I installed the disk:
Dmesg never has anything pertaining to the slicing/partitioning/newfsing
a disk. But, it should have information about the physical drive
and the controller and such.Do you see the drive even show up
in dmesg? Also, what does the controller look like in dmesg?
Namely, your drives seem to be:
> Oct 4 04:07:30 kermit kernel: ad0: 76293MB at
> ata0-master UDMA33
> Oct 4 04:07:30 kermit kernel: ad4: 953869MB at
> ata2-master UDMA33
etc.
jerry
>
> Oct 4 04:07:30 kermit kernel: Copyright (c) 1992-2006 The FreeBSD Project.
> Oct 4 04:07:30 kermit kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988,
> 1989, 1991, 1992, 1993, 1994
> Oct 4 04:07:30 kermit kernel: The Regents of the University of California.
> All rights reserved.
> Oct 4 04:07:30 kermit kernel: FreeBSD 6.1-STABLE-200608 #0: Mon Mar 19
> 22:52:31 PDT 2007
> Oct 4 04:07:30 kermit kernel:
> [EMAIL PROTECTED]:/usr/src/sys/i386/compile/KERMIT
> Oct 4 04:07:30 kermit kernel: ACPI APIC Table:
> Oct 4 04:07:30 kermit kernel: Timecounter "i8254" frequency 1193182 Hz
> quality 0
> Oct 4 04:07:30 kermit kernel: CPU: AMD Athlon(tm) 64 X2 Dual Core Processor
> 5200+ (2611.90-MHz 686-class CPU)
> Oct 4 04:07:30 kermit kernel: Origin = "AuthenticAMD" Id = 0x40f32
> Stepping = 2
> Oct 4 04:07:30 kermit kernel:
> Features=0x178bfbff ,CMOV,PAT,PSE36,CLFLUSH,MMX,F
> XSR,SSE,SSE2,HTT>
> Oct 4 04:07:30 kermit kernel: Features2=0x2001
> Oct 4 04:07:30 kermit kernel: AMD
> Features=0xea500800
> Oct 4 04:07:30 kermit kernel: AMD Features2=0x1f,,CR8>
> Oct 4 04:07:30 kermit kernel: Cores per package: 2
> Oct 4 04:07:30 kermit kernel: real memory = 3724476416 (3551 MB)
> Oct 4 04:07:30 kermit kernel: avail memory = 3647496192 (3478 MB)
> Oct 4 04:07:30 kermit kernel: FreeBSD/SMP: Multiprocessor System Detected:
> 2 CPUs
> Oct 4 04:07:30 kermit kernel: cpu0 (BSP): APIC ID: 0
Re: Can't add new 1TB disk in FreeBSD 6.1
On Mon, Oct 06, 2008 at 11:08:34AM -0700, Don O'Neil wrote: > The hardware I have is the built in SATA controller on the motherboard, > which is GIGABYTE GA-M61P-S3. With the NVIDIA GeForce 6100 / nForce 430 and > Super I/O chip: ITE IT8716. > > Oct 4 04:07:30 kermit kernel: atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0 > Oct 4 04:07:30 kermit kernel: ata0: on atapci0 > Oct 4 04:07:30 kermit kernel: ata1: on atapci0 > Oct 4 04:07:30 kermit kernel: pci0: at device 7.0 (no driver > attached) > Oct 4 04:07:30 kermit kernel: atapci1: port > 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd000-0xd00f mem > 0xf7004000-0xf7004fff irq 20 at device 8.0 on pci0 > Oct 4 04:07:30 kermit kernel: ata2: on atapci1 > Oct 4 04:07:30 kermit kernel: ata3: on atapci1 > Oct 4 04:07:30 kermit kernel: atapci2: port > 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xe400-0xe40f mem > 0xf700-0xf7000fff irq 21 at device 8.1 on pci0 > Oct 4 04:07:30 kermit kernel: ata4: on atapci2 > Oct 4 04:07:30 kermit kernel: ata5: on atapci2 > Oct 4 04:07:30 kermit kernel: ad0: 76293MB at > ata0-master UDMA33 > Oct 4 04:07:30 kermit kernel: ad4: 953869MB at > ata2-master UDMA33 This motherboard uses the nForce 430, but the SATA portion is actually a subset chip called the MCP61. I've confirmed this by looking at PRs 116880 and 108830. I can see two things from the dmesg: 1) FreeBSD has no idea what this controller is, or any "quirks" surrounding the controller (meaning it's possible that disk or block addressing is being done incorrectly), 2) The disks are seen as classic PATA disks and not SATA. This could be a result of there being no nForce 430 support in 6.1, but it could also be due to a BIOS setting on that motherboard. I'm looking at the User Manual for this motherboard, but I can't find the BIOS option that I'm used to seeing on other nForce-based boards, and Intel ICH-based boards: A feature where you can change the way the OS sees the underlying SATA controller; it's called "Emulated" or "Emulation" mode. The controller is able to interface with SATA disks, but the OS sees the controller as a classic PATA/IDE controller. This is often used for OSes which lack SATA support or native SATA drivers, such as MS-DOS. The only thing in the User Manual I see which sets off red flags is the "Serial-ATA RAID Config" item under the Integrated Peripherals menu. I really hope the "NV SATA Raid Function" is set to Disabled on your box. Looking at CVS commit logs for src/sys/dev/ata/ata-chipset.c, I can see that MCP61 support was officially added to HEAD on on 2007/06/26. I'm having a difficult time determining what HEAD meant at that date. I can't figure out for the life of me if it was referring to RELENG_6 or RELENG_7. Either way, point is, FreeBSD 6.1 flat out does not have support for that chip, even a 6.1 dated August 2006. I can't help but wonder if that's what's causing the odd problem. I also found another LBA48-related issue, dated 2007/10/04, labelled "fix the LBA28/LBA48 crossover bug". I'm still not sure what that is. And I haven't even begun to look at GEOM changes/bugfixes, which might be a more likely place. > This is actually a FreeBSD-Stable install... From 08/2006 I realize it's > probably time to do an OS upgrade, but this is the ONLY issue I've run into > running this code base. Some of the software I'm running hasn't been tested > with 7.X, so I'm not comfortable going there yet. What this means is that it's a 6.1-RELEASE install which follows the RELENG_6 tag, and has been cvsup'd at least up until August 2006. I understand you're not comfortable upgrading to FreeBSD 7, but it would be worthwhile if you could download FreeBSD 7.1-PRERELEASE (specifically disc 1 or a live CD), and see if that reports the same problem as 6.1. I still can't explain why booting the 6.1 installer and using a fixit image lets you work around the problem. That is just flat out bizarre. You have to understand: there's been a lot of evolution/bugfixes applied between 6.1 and 7.1. There's almost too much for me to try and track down. I'm trying very hard, but it's difficult. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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 add new 1TB disk in FreeBSD 6.1
> On Mon, Oct 06, 2008 at 09:45:52AM -0700, Jeremy Chadwick wrote:
> > There is one thing about later FreeBSDs which I am aware of: 48-bit
> > LBA addressing. I'm left wondering if what you're running
> into is a
> > bug or a problem with older FreeBSD (6.1) not supporting this. I
> > would have to go back through CVS commit lots for ata(4) to
> find out
> > when 48-bit LBA was added. I think 48-bit LBA support is
> required for disks >500GB.
>
> The issue I'm referring to has been touched on many times.
>
> First and foremost, 6.1-RELEASE was released in May 2006.
> Keep that date in mind when reading the below.
>
> The first incident, according to CVS commit logs, was adding
> 48-bit LBA support, supporting disks >137GB. That would've
> been in RELENG_4, dated 2002/01/05. FreeBSD 6.1 should have this.
>
> Next, we have a commit dated 2003/01/19, affecting 48-bit LBA
> support on Promise 66/100 controllers. FreeBSD 6.1 should have this.
>
> Next, 2004/12/09, talking about disk firmware bugs affecting
> 48-bit LBA addressing, which was affecting a significant
> number of users. That was applied to HEAD and RELENG_5, so
> FreeBSD 6.1 ("HEAD" at that time) should have this.
>
> Next, 2005/04/14, something about "read back the real
> taskfile register values when in 48-bit mode". Committed to
> HEAD, which would've been during days shortly before RELENG_6
> was tagged (6.0).
>
> Next, 2005/08/17, "support for working around controllers
> that can't do DMA in 48-bit LBA mode", forcing the disk to
> use PIO mode allowing the disk to address >137GB. This was
> added to HEAD and RELENG_6, so this should also exist in 6.1.
>
> Next, 2007/12/13, "also fix 48-bit LBA addressing issues,
> apparently newe chips need 16-bit writes and not the usual
> FIFO thing". This was committed to HEAD first, RELENG_7 on
> 2008/01/09, and RELENG_6 on 2008/01/09.
>
> This is one which FreeBSD 6.1 *would not* have fixes for.
>
> I do not know if this is the problem -- I'm just speculating.
>
> Because dmesg output was not provided ("nothing
> interesting"), we can't tell what sort of controller your
> disks are hooked to, yadda yadda.
> This is explicitly why I asked for that information.
>
> If you could please try 7.0-STABLE or 7.1-PRERELEASE, that
> would be highly recommended. It would at least allow us to
> determine if you're being affected by a bug in older FreeBSD,
> or if this is something that is unique to your environment or
> applies to present-day FreeBSD.
The hardware I have is the built in SATA controller on the motherboard,
which is GIGABYTE GA-M61P-S3. With the NVIDIA GeForce 6100 / nForce 430 and
Super I/O chip: ITE IT8716.
Dmesg had no output pertaining to the partition/format/dd, etc... Just
messages from my ftp daemon. If you're wanting to see the boot messages,
this is from the last time I rebooted when I installed the disk:
Oct 4 04:07:30 kermit kernel: Copyright (c) 1992-2006 The FreeBSD Project.
Oct 4 04:07:30 kermit kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988,
1989, 1991, 1992, 1993, 1994
Oct 4 04:07:30 kermit kernel: The Regents of the University of California.
All rights reserved.
Oct 4 04:07:30 kermit kernel: FreeBSD 6.1-STABLE-200608 #0: Mon Mar 19
22:52:31 PDT 2007
Oct 4 04:07:30 kermit kernel:
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/KERMIT
Oct 4 04:07:30 kermit kernel: ACPI APIC Table:
Oct 4 04:07:30 kermit kernel: Timecounter "i8254" frequency 1193182 Hz
quality 0
Oct 4 04:07:30 kermit kernel: CPU: AMD Athlon(tm) 64 X2 Dual Core Processor
5200+ (2611.90-MHz 686-class CPU)
Oct 4 04:07:30 kermit kernel: Origin = "AuthenticAMD" Id = 0x40f32
Stepping = 2
Oct 4 04:07:30 kermit kernel:
Features=0x178bfbff
Oct 4 04:07:30 kermit kernel: Features2=0x2001
Oct 4 04:07:30 kermit kernel: AMD
Features=0xea500800
Oct 4 04:07:30 kermit kernel: AMD Features2=0x1f,,CR8>
Oct 4 04:07:30 kermit kernel: Cores per package: 2
Oct 4 04:07:30 kermit kernel: real memory = 3724476416 (3551 MB)
Oct 4 04:07:30 kermit kernel: avail memory = 3647496192 (3478 MB)
Oct 4 04:07:30 kermit kernel: FreeBSD/SMP: Multiprocessor System Detected:
2 CPUs
Oct 4 04:07:30 kermit kernel: cpu0 (BSP): APIC ID: 0
Oct 4 04:07:30 kermit kernel: cpu1 (AP): APIC ID: 1
Oct 4 04:07:30 kermit kernel: ioapic0: Changing APIC ID to 2
Oct 4 04:07:30 kermit kernel: ioapic0 irqs 0-23 on
motherboard
Oct 4 04:07:30 kermit kernel: kbd1 at kbdmux0
Oct 4 04:07:30 kermit kernel: acpi0: on motherboard
Oct 4 04:07:30 kermit kernel: acpi_bus_number: can't get _ADR
Oct 4 04:07:30 kermit kernel: acpi_bus_number: can't get _ADR
Oct 4 04:07:30 kermit kernel: acpi0: Power Button (fixed)
Oct 4 04:07:30 kermit kernel: acpi_bus_number: can't get _ADR
Oct 4 04:07:30 kermit kernel: acpi_bus_number: can't get _ADR
Oct 4 04:07:30 kermit kernel: Timecounter "ACPI-fast" frequency 3579545 Hz
quality 1000
Oct 4 04:07:30 kermit kernel: acpi_timer0: <24-bit timer at 3.579545MHz>
port 0x
RE: Can't add new 1TB disk in FreeBSD 6.1
> > > > I just swapped out an old 500G disk with a 1TB one and I'm > > > > trying to label it and mount it... > > > > > > > > If I run bsdlabel -w ad4, I get: > > > > > > > > bsdlabel: Geom not found > > > > > > > > If I run sysinstall, it tells me that it can't write to the disk. > > > > > > > > I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but > > > > that didn't help. > > > > > > > > Can anyone help me get this new disk installed without having to > > > > boot off a recovery CD? The server is 500 miles away from me and > > > > I don't have direct console access. > > > > Can you provide output from dmesg, as well as "geom disk list"? > > > > > > OK... I tried: > > > > > > # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000 > > > dd: /dev/ad4: Operation not permitted > > > > > > # fdisk /dev/ad4 > > > *** Working on device /dev/ad4 *** parameters extracted > > > from in-core disklabel are: > > > cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) > > > > > > Figures below won't work with BIOS for partitions not in cyl 1 > > > parameters to be used for BIOS calculations are: > > > cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) > > > > > > fdisk: invalid fdisk partition table found Media sector size is > > > 512 > > > Warning: BIOS sector numbering starts with sector 1 Information > > > from DOS bootblock is: > > > The data for partition 1 is: > > > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > > > start 63, size 1953525105 (953869 Meg), flag 80 (active) > > > beg: cyl 0/ head 1/ sector 1; > > > end: cyl 612/ head 15/ sector 63 The data for partition 2 > > > is: > > > > > > The data for partition 3 is: > > > > > > The data for partition 4 is: > > > > > > > > > OK. That looks pretty normal. > > > > Well, except for not allowing the dd to the disk. > > I haven't had that happen on a disk. (I used to see that a lot on > > DAT > tapes) > > > > So, maybe, as someone else suggested, you also need: > > > > > OK... I tried: > > > > > > # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000 > > > dd: /dev/ad4: Operation not permitted > > > > > Did you "sysctl kern.geom.debugflags=16" before doing this? > > > > > What's happening here is that GEOM isn't letting you overwrite the > > MBR on the disk. Setting kern.geom.debugflags=16 should permit that > > to happen. > > > > > > But, do the following too. > > > > > > Did you try doing an: fdisk -I ad4 or maybe fdisk -BI ad4 > > > > It takes that to get fdisk to initialize the disk. > > (the -B puts the master boot block there. > > > > Just doing anfdisk ad4 only had fdisk read out stuff > > and there isn't anything there yet to read - so of course it is > > invalid. > > > > > > > > > > Geometry output: > > > > > > Geom name: ad4 > > > Providers: > > > 1. Name: ad4 > > >Mediasize: 1000204886016 (932G) > > >Sectorsize: 512 > > >Mode: r0w0e0 > > >fwsectors: 63 > > >fwheads: 16 > > > > > > Nothing exciting coming from dmesg. > > I tried kern.geom.debugflags=16 originally, still doesn't help. > Can you please do it and then attempt the exact dd you ran above? # sysctl kern.geom.debugflags=16 kern.geom.debugflags: 16 -> 16 # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000 dd: /dev/ad4: Operation not permitted >The reason I'm hounding: you're not providing a lot of detail between whatever it is you're doing. Just a lot of >one-liner responses "No didn't work, next". It's very difficult to discern what exactly you're doing; for example, >you could've run the sysctl and then attempted an install, rather than re-execute the dd. I did exactly as you suggested, and I've posed all my results here... I'm scratching my head on this one as much as you are. >I can refer you to historic data that shows people have gotten the exact error you're seeing when attempting to >write to block 0 (MBR), stopped by GEOM, which is why I'm a little wary. >> Someone else recommended running sade(8) and properly configuring this disk. >> What is sade(8)? I don't have such an application on 6.1, and there is >> nothing in the ports. I think that sade is a 7.0+ tool. >6.1? Why? This is a new install, right? Is there some reason you're installing 6.1 and not 6.3, or better yet, >7.0? That's a separate question, but it does make me wonder if something was fixed between 6.1 and 6.3/7.0 which >might address this problem. No, it's not a new install, I'm just trying to add a new disk on an older server. I REALLY don't want to do an OS upgrade at this point on a production box that is running fine. We do that 1x a year, and I'm not in the mood to do it just to add a bigger disk. >There is one thing about later FreeBSDs which I am aware of: 48-bit LBA addressing. I'm left wondering if what >you're running into is a bug or a problem with older FreeBSD (6.1) not supporting this. I would have to go back> through CVS commit lots for ata(4) to find out when 48-bit LBA w
Re: Can't add new 1TB disk in FreeBSD 6.1
On Mon, Oct 06, 2008 at 09:45:52AM -0700, Jeremy Chadwick wrote:
> There is one thing about later FreeBSDs which I am aware of: 48-bit LBA
> addressing. I'm left wondering if what you're running into is a bug or
> a problem with older FreeBSD (6.1) not supporting this. I would have to
> go back through CVS commit lots for ata(4) to find out when 48-bit LBA
> was added. I think 48-bit LBA support is required for disks >500GB.
The issue I'm referring to has been touched on many times.
First and foremost, 6.1-RELEASE was released in May 2006. Keep that
date in mind when reading the below.
The first incident, according to CVS commit logs, was adding 48-bit
LBA support, supporting disks >137GB. That would've been in
RELENG_4, dated 2002/01/05. FreeBSD 6.1 should have this.
Next, we have a commit dated 2003/01/19, affecting 48-bit LBA support
on Promise 66/100 controllers. FreeBSD 6.1 should have this.
Next, 2004/12/09, talking about disk firmware bugs affecting 48-bit LBA
addressing, which was affecting a significant number of users. That was
applied to HEAD and RELENG_5, so FreeBSD 6.1 ("HEAD" at that time)
should have this.
Next, 2005/04/14, something about "read back the real taskfile
register values when in 48-bit mode". Committed to HEAD, which would've
been during days shortly before RELENG_6 was tagged (6.0).
Next, 2005/08/17, "support for working around controllers that can't
do DMA in 48-bit LBA mode", forcing the disk to use PIO mode allowing
the disk to address >137GB. This was added to HEAD and RELENG_6, so
this should also exist in 6.1.
Next, 2007/12/13, "also fix 48-bit LBA addressing issues, apparently
newe chips need 16-bit writes and not the usual FIFO thing". This
was committed to HEAD first, RELENG_7 on 2008/01/09, and RELENG_6
on 2008/01/09.
This is one which FreeBSD 6.1 *would not* have fixes for.
I do not know if this is the problem -- I'm just speculating.
Because dmesg output was not provided ("nothing interesting"), we can't
tell what sort of controller your disks are hooked to, yadda yadda.
This is explicitly why I asked for that information.
If you could please try 7.0-STABLE or 7.1-PRERELEASE, that would be
highly recommended. It would at least allow us to determine if you're
being affected by a bug in older FreeBSD, or if this is something that
is unique to your environment or applies to present-day FreeBSD.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
___
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 add new 1TB disk in FreeBSD 6.1
On Mon, Oct 06, 2008 at 09:36:19AM -0700, Don O'Neil wrote: > > > On Mon, Oct 06, 2008 at 08:03:46AM -0700, Don O'Neil wrote: > > > > > > I just swapped out an old 500G disk with a 1TB one and I'm trying > > > > to label it and mount it... > > > > > > > > If I run bsdlabel -w ad4, I get: > > > > > > > > bsdlabel: Geom not found > > > > > > > > If I run sysinstall, it tells me that it can't write to the disk. > > > > > > > > I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but > > > > that didn't help. > > > > > > > > Can anyone help me get this new disk installed without having to > > > > boot off a recovery CD? The server is 500 miles away from me and I > > > > don't have direct console access. > > > > Can you provide output from dmesg, as well as "geom disk list"? > > > > > > OK... I tried: > > > > > > # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000 > > > dd: /dev/ad4: Operation not permitted > > > > > > # fdisk /dev/ad4 > > > *** Working on device /dev/ad4 *** parameters extracted from > > > in-core disklabel are: > > > cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) > > > > > > Figures below won't work with BIOS for partitions not in cyl 1 > > > parameters to be used for BIOS calculations are: > > > cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) > > > > > > fdisk: invalid fdisk partition table found Media sector size is 512 > > > Warning: BIOS sector numbering starts with sector 1 Information from > > > DOS bootblock is: > > > The data for partition 1 is: > > > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > > > start 63, size 1953525105 (953869 Meg), flag 80 (active) > > > beg: cyl 0/ head 1/ sector 1; > > > end: cyl 612/ head 15/ sector 63 The data for partition 2 > > > is: > > > > > > The data for partition 3 is: > > > > > > The data for partition 4 is: > > > > > > > > > OK. That looks pretty normal. > > > > Well, except for not allowing the dd to the disk. > > I haven't had that happen on a disk. (I used to see that a lot on DAT > tapes) > > > > So, maybe, as someone else suggested, you also need: > > > > > OK... I tried: > > > > > > # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000 > > > dd: /dev/ad4: Operation not permitted > > > > > Did you "sysctl kern.geom.debugflags=16" before doing this? > > > > > What's happening here is that GEOM isn't letting you overwrite the MBR > > on the disk. Setting kern.geom.debugflags=16 should permit that to > > happen. > > > > > > But, do the following too. > > > > > > Did you try doing an: fdisk -I ad4 or maybe fdisk -BI ad4 > > > > It takes that to get fdisk to initialize the disk. > > (the -B puts the master boot block there. > > > > Just doing anfdisk ad4 only had fdisk read out stuff > > and there isn't anything there yet to read - so of course it is > > invalid. > > > > > > > > > > Geometry output: > > > > > > Geom name: ad4 > > > Providers: > > > 1. Name: ad4 > > >Mediasize: 1000204886016 (932G) > > >Sectorsize: 512 > > >Mode: r0w0e0 > > >fwsectors: 63 > > >fwheads: 16 > > > > > > Nothing exciting coming from dmesg. > > I tried kern.geom.debugflags=16 originally, still doesn't help. Can you please do it and then attempt the exact dd you ran above? The reason I'm hounding: you're not providing a lot of detail between whatever it is you're doing. Just a lot of one-liner responses "No didn't work, next". It's very difficult to discern what exactly you're doing; for example, you could've run the sysctl and then attempted an install, rather than re-execute the dd. I can refer you to historic data that shows people have gotten the exact error you're seeing when attempting to write to block 0 (MBR), stopped by GEOM, which is why I'm a little wary. > Someone else recommended running sade(8) and properly configuring this disk. > What is sade(8)? I don't have such an application on 6.1, and there is > nothing in the ports. I think that sade is a 7.0+ tool. 6.1? Why? This is a new install, right? Is there some reason you're installing 6.1 and not 6.3, or better yet, 7.0? That's a separate question, but it does make me wonder if something was fixed between 6.1 and 6.3/7.0 which might address this problem. There is one thing about later FreeBSDs which I am aware of: 48-bit LBA addressing. I'm left wondering if what you're running into is a bug or a problem with older FreeBSD (6.1) not supporting this. I would have to go back through CVS commit lots for ata(4) to find out when 48-bit LBA was added. I think 48-bit LBA support is required for disks >500GB. sade(8) is the "famous" console UI for disk partitioning and labelling inside of sysinstall. It's a separate application, and was introduced in FreeBSD 6.3. You can get the exact same functionality out of sysinstall on earlier FreeBSDs. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://ww
RE: Can't add new 1TB disk in FreeBSD 6.1
> On Mon, Oct 06, 2008 at 08:03:46AM -0700, Don O'Neil wrote: > > > > I just swapped out an old 500G disk with a 1TB one and I'm trying > > > to label it and mount it... > > > > > > If I run bsdlabel -w ad4, I get: > > > > > > bsdlabel: Geom not found > > > > > > If I run sysinstall, it tells me that it can't write to the disk. > > > > > > I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but > > > that didn't help. > > > > > > Can anyone help me get this new disk installed without having to > > > boot off a recovery CD? The server is 500 miles away from me and I > > > don't have direct console access. > > > Can you provide output from dmesg, as well as "geom disk list"? > > > > OK... I tried: > > > > # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000 > > dd: /dev/ad4: Operation not permitted > > > > # fdisk /dev/ad4 > > *** Working on device /dev/ad4 *** parameters extracted from > > in-core disklabel are: > > cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) > > > > Figures below won't work with BIOS for partitions not in cyl 1 > > parameters to be used for BIOS calculations are: > > cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) > > > > fdisk: invalid fdisk partition table found Media sector size is 512 > > Warning: BIOS sector numbering starts with sector 1 Information from > > DOS bootblock is: > > The data for partition 1 is: > > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > > start 63, size 1953525105 (953869 Meg), flag 80 (active) > > beg: cyl 0/ head 1/ sector 1; > > end: cyl 612/ head 15/ sector 63 The data for partition 2 > > is: > > > > The data for partition 3 is: > > > > The data for partition 4 is: > > > > > OK. That looks pretty normal. > > Well, except for not allowing the dd to the disk. > I haven't had that happen on a disk. (I used to see that a lot on DAT tapes) > > So, maybe, as someone else suggested, you also need: > > > OK... I tried: > > > > # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000 > > dd: /dev/ad4: Operation not permitted > > > Did you "sysctl kern.geom.debugflags=16" before doing this? > > > What's happening here is that GEOM isn't letting you overwrite the MBR > on the disk. Setting kern.geom.debugflags=16 should permit that to > happen. > > > But, do the following too. > > > Did you try doing an: fdisk -I ad4 or maybe fdisk -BI ad4 > > It takes that to get fdisk to initialize the disk. > (the -B puts the master boot block there. > > Just doing anfdisk ad4 only had fdisk read out stuff > and there isn't anything there yet to read - so of course it is > invalid. > > > > > > Geometry output: > > > > Geom name: ad4 > > Providers: > > 1. Name: ad4 > >Mediasize: 1000204886016 (932G) > >Sectorsize: 512 > >Mode: r0w0e0 > >fwsectors: 63 > >fwheads: 16 > > > > Nothing exciting coming from dmesg. I tried kern.geom.debugflags=16 originally, still doesn't help. Someone else recommended running sade(8) and properly configuring this disk. What is sade(8)? I don't have such an application on 6.1, and there is nothing in the ports. I think that sade is a 7.0+ tool. Any other ideas? ___ 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 add new 1TB disk in FreeBSD 6.1
On Mon, Oct 06, 2008 at 12:07:08PM -0400, Jerry McAllister wrote: > On Mon, Oct 06, 2008 at 08:03:46AM -0700, Don O'Neil wrote: > > > > I just swapped out an old 500G disk with a 1TB one and I'm trying to > > > label it and mount it... > > > > > > If I run bsdlabel -w ad4, I get: > > > > > > bsdlabel: Geom not found > > > > > > If I run sysinstall, it tells me that it can't write to the disk. > > > > > > I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but that > > > didn't help. > > > > > > Can anyone help me get this new disk installed without having to boot > > > off a recovery CD? The server is 500 miles away from me and I don't > > > have direct console access. > > > Can you provide output from dmesg, as well as "geom disk list"? > > > > OK... I tried: > > > > # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000 > > dd: /dev/ad4: Operation not permitted > > > > # fdisk /dev/ad4 > > *** Working on device /dev/ad4 *** > > parameters extracted from in-core disklabel are: > > cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) > > > > Figures below won't work with BIOS for partitions not in cyl 1 > > parameters to be used for BIOS calculations are: > > cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) > > > > fdisk: invalid fdisk partition table found > > Media sector size is 512 > > Warning: BIOS sector numbering starts with sector 1 > > Information from DOS bootblock is: > > The data for partition 1 is: > > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > > start 63, size 1953525105 (953869 Meg), flag 80 (active) > > beg: cyl 0/ head 1/ sector 1; > > end: cyl 612/ head 15/ sector 63 > > The data for partition 2 is: > > > > The data for partition 3 is: > > > > The data for partition 4 is: > > > > > OK. That looks pretty normal. Well, except for not allowing the dd to the disk. I haven't had that happen on a disk. (I used to see that a lot on DAT tapes) So, maybe, as someone else suggested, you also need: > > OK... I tried: > > > > # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000 > > dd: /dev/ad4: Operation not permitted > > > Did you "sysctl kern.geom.debugflags=16" before doing this? > > > What's happening here is that GEOM isn't letting you overwrite the MBR > on the disk. Setting kern.geom.debugflags=16 should permit that to > happen. > But, do the following too. > > Did you try doing an: fdisk -I ad4 or maybe fdisk -BI ad4 > > It takes that to get fdisk to initialize the disk. > (the -B puts the master boot block there. > > Just doing anfdisk ad4 only had fdisk read out stuff > and there isn't anything there yet to read - so of course > it is invalid. > > jerry > > > > > > > Geometry output: > > > > Geom name: ad4 > > Providers: > > 1. Name: ad4 > >Mediasize: 1000204886016 (932G) > >Sectorsize: 512 > >Mode: r0w0e0 > >fwsectors: 63 > >fwheads: 16 > > > > Nothing exciting coming from dmesg. > > > > > > ___ > > 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 add new 1TB disk in FreeBSD 6.1
On Mon, Oct 06, 2008 at 08:03:46AM -0700, Don O'Neil wrote: > > I just swapped out an old 500G disk with a 1TB one and I'm trying to > > label it and mount it... > > > > If I run bsdlabel -w ad4, I get: > > > > bsdlabel: Geom not found > > > > If I run sysinstall, it tells me that it can't write to the disk. > > > > I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but that > > didn't help. > > > > Can anyone help me get this new disk installed without having to boot > > off a recovery CD? The server is 500 miles away from me and I don't > > have direct console access. > > Can you provide output from dmesg, as well as "geom disk list"? > > OK... I tried: > > # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000 > dd: /dev/ad4: Operation not permitted > > # fdisk /dev/ad4 > *** Working on device /dev/ad4 *** > parameters extracted from in-core disklabel are: > cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) > > fdisk: invalid fdisk partition table found > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 63, size 1953525105 (953869 Meg), flag 80 (active) > beg: cyl 0/ head 1/ sector 1; > end: cyl 612/ head 15/ sector 63 > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > OK. That looks pretty normal. Did you try doing an: fdisk -I ad4 or maybe fdisk -BI ad4 It takes that to get fdisk to initialize the disk. (the -B puts the master boot block there. Just doing anfdisk ad4 only had fdisk read out stuff and there isn't anything there yet to read - so of course it is invalid. jerry > > Geometry output: > > Geom name: ad4 > Providers: > 1. Name: ad4 >Mediasize: 1000204886016 (932G) >Sectorsize: 512 >Mode: r0w0e0 >fwsectors: 63 >fwheads: 16 > > Nothing exciting coming from dmesg. > > > ___ > 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 add new 1TB disk in FreeBSD 6.1
On Mon, Oct 06, 2008 at 08:03:46AM -0700, Don O'Neil wrote: > > I just swapped out an old 500G disk with a 1TB one and I'm trying to > > label it and mount it... > > > > If I run bsdlabel -w ad4, I get: > > > > bsdlabel: Geom not found > > > > If I run sysinstall, it tells me that it can't write to the disk. > > > > I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but that > > didn't help. > > > > Can anyone help me get this new disk installed without having to boot > > off a recovery CD? The server is 500 miles away from me and I don't > > have direct console access. > > Can you provide output from dmesg, as well as "geom disk list"? > > OK... I tried: > > # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000 > dd: /dev/ad4: Operation not permitted Did you "sysctl kern.geom.debugflags=16" before doing this? What's happening here is that GEOM isn't letting you overwrite the MBR on the disk. Setting kern.geom.debugflags=16 should permit that to happen. > # fdisk /dev/ad4 > *** Working on device /dev/ad4 *** > parameters extracted from in-core disklabel are: > cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) > > fdisk: invalid fdisk partition table found This line right here looks very bad. I would recommend running sade(8) and properly configuring this disk. > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 63, size 1953525105 (953869 Meg), flag 80 (active) > beg: cyl 0/ head 1/ sector 1; > end: cyl 612/ head 15/ sector 63 This portion looks okay, although I guess the addressing mode chosen is different on your system. Most of my systems show the end CHS as 1023/254/63. > Geometry output: > > Geom name: ad4 > Providers: > 1. Name: ad4 >Mediasize: 1000204886016 (932G) >Sectorsize: 512 >Mode: r0w0e0 >fwsectors: 63 >fwheads: 16 This looks okay. > Nothing exciting coming from dmesg. Thanks for providing the output like I requested. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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 add new 1TB disk in FreeBSD 6.1
> I just swapped out an old 500G disk with a 1TB one and I'm trying to > label it and mount it... > > If I run bsdlabel -w ad4, I get: > > bsdlabel: Geom not found > > If I run sysinstall, it tells me that it can't write to the disk. > > I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but that > didn't help. > > Can anyone help me get this new disk installed without having to boot > off a recovery CD? The server is 500 miles away from me and I don't > have direct console access. > Can you provide output from dmesg, as well as "geom disk list"? OK... I tried: # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000 dd: /dev/ad4: Operation not permitted # fdisk /dev/ad4 *** Working on device /dev/ad4 *** parameters extracted from in-core disklabel are: cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 1953525105 (953869 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 612/ head 15/ sector 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: Geometry output: Geom name: ad4 Providers: 1. Name: ad4 Mediasize: 1000204886016 (932G) Sectorsize: 512 Mode: r0w0e0 fwsectors: 63 fwheads: 16 Nothing exciting coming from dmesg. ___ 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 add new 1TB disk in FreeBSD 6.1
On Sun, Oct 05, 2008 at 03:42:53AM -0700, Jeremy Chadwick wrote: > On Sun, Oct 05, 2008 at 11:07:58AM +0200, Wojciech Puchar wrote: > >>> > >>> > >>> I tried using fdisk first, same problem, won't let me write to the disk. > >> > >> Do you will use the entire disk in one partition ? If so, just do: > >> newfs /dev/ad4 > >> > > yes you can. i actually do this > > Isn't this what's called "Dangerously Dedicated" mode, and is considered > "very risky behaviour" on FreeBSD nowadays? It is what is called 'dangerously dedicated' but the 'nowdays' thing is not relevant. It is as old as the slice/partition framework. It is probably not a good name for it because it is not risky for the system you are using it on.It's only problem is if you want to read/write the disk in a different system. You might not be able to do it because it does not follow the most standard way.It is not a problem for a disk that is only used on FreeBSD. On the other hand, I see no reason to not use the slice+partition system that is most standard. fdisk to create slices and bsdlabel to create partitions and then newfs each partition except swap. jerry > > I would be wary of doing it that way. Using slices is the preferred > method, e.g. newfs /dev/ad4s1a. > > -- > | Jeremy Chadwickjdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > ___ > 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 add new 1TB disk in FreeBSD 6.1
On Sun, Oct 05, 2008 at 03:42:53AM -0700, Jeremy Chadwick wrote: > On Sun, Oct 05, 2008 at 11:07:58AM +0200, Wojciech Puchar wrote: > >>> > >>> > >>> I tried using fdisk first, same problem, won't let me write to the disk. > >> > >> Do you will use the entire disk in one partition ? If so, just do: > >> newfs /dev/ad4 > >> > > yes you can. i actually do this > > Isn't this what's called "Dangerously Dedicated" mode, and is considered > "very risky behaviour" on FreeBSD nowadays? > > I would be wary of doing it that way. Using slices is the preferred > method, e.g. newfs /dev/ad4s1a. Specific details are covered in the FAQ: http://www.freebsd.org/doc/en/books/faq/disks.html#DANGEROUSLY-DEDICATED The bottom line should be obvious: do not use this method. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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 add new 1TB disk in FreeBSD 6.1
On Sun, Oct 05, 2008 at 11:07:58AM +0200, Wojciech Puchar wrote: >>> >>> >>> I tried using fdisk first, same problem, won't let me write to the disk. >> >> Do you will use the entire disk in one partition ? If so, just do: >> newfs /dev/ad4 >> > yes you can. i actually do this Isn't this what's called "Dangerously Dedicated" mode, and is considered "very risky behaviour" on FreeBSD nowadays? I would be wary of doing it that way. Using slices is the preferred method, e.g. newfs /dev/ad4s1a. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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 add new 1TB disk in FreeBSD 6.1
I tried using fdisk first, same problem, won't let me write to the disk. Do you will use the entire disk in one partition ? If so, just do: newfs /dev/ad4 yes you can. i actually do this ___ 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 add new 1TB disk in FreeBSD 6.1
On Sat, Oct 04, 2008 at 04:43:14AM -0700, Don O'Neil wrote: > I just swapped out an old 500G disk with a 1TB one and I'm trying to label > it and mount it... > > If I run bsdlabel -w ad4, I get: > > bsdlabel: Geom not found > > If I run sysinstall, it tells me that it can't write to the disk. > > I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but that didn't > help. > > Can anyone help me get this new disk installed without having to boot off a > recovery CD? The server is 500 miles away from me and I don't have direct > console access. Can you provide output from dmesg, as well as "geom disk list"? -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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 add new 1TB disk in FreeBSD 6.1
On Sat, Oct 04, 2008 at 04:43:14AM -0700, Don O'Neil wrote: > I just swapped out an old 500G disk with a 1TB one and I'm trying to label > it and mount it... > > If I run bsdlabel -w ad4, I get: > > bsdlabel: Geom not found > > If I run sysinstall, it tells me that it can't write to the disk. > > I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but that didn't > help. > > Can anyone help me get this new disk installed without having to boot off a > recovery CD? The server is 500 miles away from me and I don't have direct > console access. did you try doing a dd to the disk? Sometimes a new unwritten disk seems to need it. I don't know why. It is mentioned in the man page for bsdlabel - near the bottom in an example. dd f=/dev/zero of=/dev/ad4 bs=512 count=1000 or something like that. I have run in to this a couple of times in the past where the dd seemed to fix it. Anyway, it is getting near Halloween, so these mystery fixes may be appropriate... jerry > > Thanks!!! > > ___ > 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 add new 1TB disk in FreeBSD 6.1
> >>> I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but > >>> that > >>> didn't help. > >>> > >>> Can anyone help me get this new disk installed without having to > boot >>> off a recovery CD? The server is 500 miles away from me and > I don't >>> have direct console access. > >>> > >> > >> Uhmm... This may seem silly, but did you use fdisk to create a > slice >> first before you tried partitioning? > >> > >this is NOT needed. actually i don't do it anywhere. > > > >it just may be sysinstall problem, anything else. > > > I tried using fdisk first, same problem, won't let me write to the disk. Do you will use the entire disk in one partition ? If so, just do: newfs /dev/ad4 Maybe you should to use gjournal for this large filesystem I tried newfs before, same issue: # newfs /dev/ad4 newfs: /dev/ad4: failed to open disk for writing ___ 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 add new 1TB disk in FreeBSD 6.1
On 10/4/08, Don O'Neil <[EMAIL PROTECTED]> wrote: > >>> I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but that > >>> didn't help. > >>> > >>> Can anyone help me get this new disk installed without having to boot > >>> off a recovery CD? The server is 500 miles away from me and I don't > >>> have direct console access. > >>> > >> > >> Uhmm... This may seem silly, but did you use fdisk to create a slice > >> first before you tried partitioning? > >> > >this is NOT needed. actually i don't do it anywhere. > > > >it just may be sysinstall problem, anything else. > > > I tried using fdisk first, same problem, won't let me write to the disk. Do you will use the entire disk in one partition ? If so, just do: newfs /dev/ad4 Maybe you should to use gjournal for this large filesystem ___ 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 add new 1TB disk in FreeBSD 6.1
>>> I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but that >>> didn't help. >>> >>> Can anyone help me get this new disk installed without having to boot >>> off a recovery CD? The server is 500 miles away from me and I don't >>> have direct console access. >>> >> >> Uhmm... This may seem silly, but did you use fdisk to create a slice >> first before you tried partitioning? >> >this is NOT needed. actually i don't do it anywhere. > >it just may be sysinstall problem, anything else. I tried using fdisk first, same problem, won't let me write to the disk. ___ 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 add new 1TB disk in FreeBSD 6.1
I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but that didn't help. Can anyone help me get this new disk installed without having to boot off a recovery CD? The server is 500 miles away from me and I don't have direct console access. Uhmm... This may seem silly, but did you use fdisk to create a slice first before you tried partitioning? this is NOT needed. actually i don't do it anywhere. it just may be sysinstall problem, anything else. ___ 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 add new 1TB disk in FreeBSD 6.1
Don O'Neil wrote: > I just swapped out an old 500G disk with a 1TB one and I'm trying to label > it and mount it... > > If I run bsdlabel -w ad4, I get: > > bsdlabel: Geom not found > > If I run sysinstall, it tells me that it can't write to the disk. > > I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but that > didn't help. > > Can anyone help me get this new disk installed without having to boot off > a recovery CD? The server is 500 miles away from me and I don't have > direct console access. > Uhmm... This may seem silly, but did you use fdisk to create a slice first before you tried partitioning? -Mike- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Can't add new 1TB disk in FreeBSD 6.1
I just swapped out an old 500G disk with a 1TB one and I'm trying to label it and mount it... If I run bsdlabel -w ad4, I get: bsdlabel: Geom not found If I run sysinstall, it tells me that it can't write to the disk. I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but that didn't help. Can anyone help me get this new disk installed without having to boot off a recovery CD? The server is 500 miles away from me and I don't have direct console access. Thanks!!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
