Re: OpenBSD 4.4-release installation hangs on large disk (x86)

2008-12-01 Thread Chris
On Mon, Dec 1, 2008 at 12:19 AM, Richard Toohey
[EMAIL PROTECTED] wrote:
 I've got a couple of Dell SC440s with the same sort of set-up, and
 no problems here.

 Two 500Gb drives, wd0 and wd1:

I have resolved this issue. I tried the installation again and this
time selected fdisk before selecting disk label. Under fdisk I could
see 4 partitions 0, 1, 2 and 3 (#3 is where OpenBSD was installed); 0,
1 and 2 were labeled as unused. I flagged 0, 1 and 2 as disable and
the installation went smoothly.



Re: OpenBSD 4.4-release installation hangs on large disk (x86)

2008-11-30 Thread Chris
 2) in an earlier message you indicated that there was some kind of
 RAID on this system, I think it is safe to say that it is a BIOS-assisted
 software RAID, which COULD be causing you problems if it is still
 configured in the BIOS.  And even if it isn't causing this problem,
 it WILL bite you in the future when the BIOS decides top copy something
 from one drive to the other...

Sorry about my previous post but there is no RAID.

 So, start by disabling the BIOS RAID do-hickey thing and unplug
 the second drive.  I suspect you will have no problems then.

I have tried pulling the plug on the second disk (wd1) with no luck.

 Once you convince yourself the size of the drive is not directly
 an issue, I'd suggest starting over with a more sane partitioning
 plan.  Just because you have a cheap 500G disk doesn't mean you
 need to allocate all or most of it.  For one, the bigger the disk,
 the longer it takes to fsck after you trip over the power cord.

I actually have two cheap 500GB; so that makes it 1 terabyte. I
don't mind fsck doing its thing when I trip over the cable. But I
really do need a large /data1 partition to rsync stuff over from other
places. Here's the last disk partition I tried (and it didn't work): /
10g, swap 3g, /tmp 20g, /home 100g, /var/ 50g, /usr/ 50g. It was
sitting there for 30 minutes after the last file set was installed
(xserv44.tgz) and then I turned it off.

Thanks for any further help.



Re: OpenBSD 4.4-release installation hangs on large disk (x86)

2008-11-30 Thread Dieter
 Just because you have a cheap 500G disk doesn't mean you
 need to allocate all or most of it.  For one, the bigger the disk,
 the longer it takes to fsck after you trip over the power cord.

Wait for fsck?  So OpenBSD doesn't have background fsck?  :-(



Re: OpenBSD 4.4-release installation hangs on large disk (x86)

2008-11-30 Thread Richard Toohey

On 1/12/2008, at 9:24 AM, Chris wrote:


2) in an earlier message you indicated that there was some kind of
RAID on this system, I think it is safe to say that it is a BIOS- 
assisted

software RAID, which COULD be causing you problems if it is still
configured in the BIOS.  And even if it isn't causing this problem,
it WILL bite you in the future when the BIOS decides top copy  
something

from one drive to the other...


Sorry about my previous post but there is no RAID.


So, start by disabling the BIOS RAID do-hickey thing and unplug
the second drive.  I suspect you will have no problems then.


I have tried pulling the plug on the second disk (wd1) with no luck.


Once you convince yourself the size of the drive is not directly
an issue, I'd suggest starting over with a more sane partitioning
plan.  Just because you have a cheap 500G disk doesn't mean you
need to allocate all or most of it.  For one, the bigger the disk,
the longer it takes to fsck after you trip over the power cord.


I actually have two cheap 500GB; so that makes it 1 terabyte. I
don't mind fsck doing its thing when I trip over the cable. But I
really do need a large /data1 partition to rsync stuff over from other
places. Here's the last disk partition I tried (and it didn't work): /
10g, swap 3g, /tmp 20g, /home 100g, /var/ 50g, /usr/ 50g. It was
sitting there for 30 minutes after the last file set was installed
(xserv44.tgz) and then I turned it off.

Thanks for any further help.


I've got a couple of Dell SC440s with the same sort of set-up, and
no problems here.

Two 500Gb drives, wd0 and wd1:

# df -h
Filesystem SizeUsed   Avail Capacity  Mounted on
/dev/wd0a 84.4M   36.6M   43.6M46%/
/dev/wd0h 1008M2.7M955M 0%/home
/dev/wd0i  436G121G294G29%/public
/dev/wd1a  458G116G320G27%/public2
/dev/wd0d 1008M2.0K958M 0%/tmp
/dev/wd0g  9.8G1.9G7.4G21%/usr
/dev/wd0e  9.8G   31.2M9.3G 0%/var

I wanted one large dumping ground on wd0, and another on wd1,
and had no trouble creating them (I cannot recall any lengthy delay;
not the same as saying there wasn't one, but I don't remember it.)

And yes, fsck does take a long time.

Thanks.

dmesg (sd0 is an 8Gb USB memstick):

OpenBSD 4.4 (GENERIC) #0: Tue Nov 11 10:18:14 NZDT 2008
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) D CPU 3.00GHz (GenuineIntel 686-class) 3 GHz
cpu0:  
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36, 
CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS- 
CPL,EST,CNXT-ID,CX16,xTPR

real mem  = 1071722496 (1022MB)
avail mem = 1027870720 (980MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 07/03/07, BIOS32 rev. 0 @  
0xffe90, SMBIOS rev. 2.3 @ 0xf0450 (63 entries)

bios0: vendor Dell Inc. version 1.4.1 date 07/03/2007
bios0: Dell Inc. PowerEdge SC440
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
acpi at bios0 function 0x0 not configured
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfed10/256 (14 entries)
pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801GH LPC rev  
0x00)

pcibios0: PCI bus #5 is the last bus
bios0: ROM list: 0xc/0x9000 0xc9000/0x2000! 0xcb000/0x1000
cpu0 at mainbus0
cpu0: Enhanced SpeedStep disabled by BIOS
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 Intel E7230 Host rev 0x00
ppb0 at pci0 dev 1 function 0 Intel E7230 PCIE rev 0x00: irq 11
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01: irq 11
pci2 at ppb1 bus 2
ppb2 at pci0 dev 28 function 4 Intel 82801G PCIE rev 0x01: irq 11
pci3 at ppb2 bus 3
em0 at pci3 dev 0 function 0 Intel PRO/1000 PT (82572EI) rev 0x06:  
irq 11, address 00:15:17:3d:38:11

ppb3 at pci0 dev 28 function 5 Intel 82801G PCIE rev 0x01: irq 10
pci4 at ppb3 bus 4
bge0 at pci4 dev 0 function 0 Broadcom BCM5754 rev 0x02,  
BCM5754/5787 A2 (0xb002): irq 10, address 00:1d:09:09:94:17

brgphy0 at bge0 phy 1: BCM5787 10/100/1000baseT PHY, rev. 0
uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: irq 9
uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: irq 5
uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: irq 3
uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x01: irq 10
ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x01: irq 9
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1
ppb4 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0xe1
pci5 at ppb4 bus 5
vga1 at pci5 dev 7 function 0 ATI ES1000 rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
drm at vga1 unsupported
ichpcib0 at pci0 dev 31 function 0 Intel 82801GB LPC rev 0x01: PM  
disabled
pciide0 at pci0 dev 31 function 1 Intel 82801GB IDE rev 0x01: DMA,  
channel 

Re: OpenBSD 4.4-release installation hangs on large disk (x86)

2008-11-29 Thread Nick Holland
Chris wrote:
 I'm trying to install OBSD 4.4-release on this desktop which has two
 hard disks of around 465 GB each. If I install on wd0 with only one
 partition (/) of 10GB, the installation goes smoothly. But if I try to
 allocate /tmp (20g), /home (100g), / (50g), /var (50g), /usr (50g),
 swap (3g), the installation hangs after the last file set is installed
 (xserv44.tgz): it just sits there and I cannot use my keyboard
 anymore. I have waited for about 2 hours for the installation to
 proceed to the next step but nothing. Here's my dmesg; Thanks for any
 help.

1) Having installed OpenBSD on a lot of 500G disks, I think I can
say with confidence the size of the disk is not your problem.

2) in an earlier message you indicated that there was some kind of
RAID on this system, I think it is safe to say that it is a BIOS-assisted
software RAID, which COULD be causing you problems if it is still
configured in the BIOS.  And even if it isn't causing this problem,
it WILL bite you in the future when the BIOS decides top copy something
from one drive to the other...


So, start by disabling the BIOS RAID do-hickey thing and unplug
the second drive.  I suspect you will have no problems then.


Once you convince yourself the size of the drive is not directly
an issue, I'd suggest starting over with a more sane partitioning
plan.  Just because you have a cheap 500G disk doesn't mean you
need to allocate all or most of it.  For one, the bigger the disk,
the longer it takes to fsck after you trip over the power cord.

Nick.