Re: Problem with disk size
Please dont kill me :) I'm really not experienced with this kind of stuff. Maby this helps: $ sudo disklabel wd0 # Inside MBR partition 3: type A6 start 63 size 16514001 # /dev/rwd0c: type: ESDI disk: ESDI/IDE disk label: Maxtor 6L250R0 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 16383 total sectors: 490234752 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # sizeoffset fstype [fsize bsize cpg] c: 490234752 0 unused 0 0 # Cyl 0 -486343 d: 49023468863 4.2BSD 2048 16384 16 # Cyl 0*-486343* $ sudo fdisk wd0 fdisk: sysctl(machdep.bios.diskinfo): Device not configured Disk: wd0 geometry: 16383/16/63 [490234752 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: idC H S -C H S [ start: size ] 0: 000 0 0 -0 0 0 [ 0: 0 ] unused 1: 000 0 0 -0 0 0 [ 0: 0 ] unused 2: 000 0 0 -0 0 0 [ 0: 0 ] unused *3: A60 1 1 - 16382 15 63 [ 63:16514001 ] OpenBSD $ Jon Sjvstedt wrote: Hello all! I have an OpenBSD-box with two 250G drives inside (and some SCSI). Trying to use one of the drives as a whole gave this from disklabel $ sudo disklabel -p g wd0 [snip] don't snip. 16 partitions: # sizeoffset fstype [fsize bsize cpg] c:233.8G 0.0G unused 0 0 # Cyl 0-486343 d:233.8G 0.0G 4.2BSD 2048 16384 16 # Cyl 0*-486343* but df -h says: /dev/wd0d 7.8G7.4G4.2M 100% and I cant create any new files on the drive. What could be the problem here? Any hints appreciated. dmesg attached. thanks for the dmesg. You tried darned hard to obscure this (I really don't care how many G your disk is, I care about which sectors you are using), but it does appear that you opted to not properly partition your disk. The fact that you didn't show the output of fdisk causes me to believe you knew it, though you may not have recognized the significance. ;) Your OpenBSD subpartition appears to start at sector zero. Bad idea. This means, whether by design or by accident, you don't have an fdisk partition table (aka, MBR) on the disk. Also a bad idea. On some platforms, i386 is one of them, you must use fdisk partitions, and your disklabel partitions must start at a one track offset (in your case, probably 63 sectors). When you don't follow the rules, ugly things happen. It isn't the size of the disk, it's the way it's laid out that is giving you problems. See faq14.html... I did, but i probably didnt understand it :P Nick. Jon Sjvstedt _O_
Re: Problem with disk size
Jon Sjvstedt wrote: Please dont kill me :) I'm really not experienced with this kind of stuff. Looks like you maybe cloned an 8GB disk to the 250GB disk and are now running out of space on the cloned file system. fdisk wd0 should give you the MS-DOS partitioning (what BIOS sees) 16383/16/63 16383 cylinders, 16 heads 63 sectors per track = 8.45GB disklable wd0 will give you the layout of where partitions find themselves. Note, the file system that is there, can have been set up to 1) use more space than is available -- generally with wierd results 2) use less space than is available --- works but is way too small Reasons for including complete info (and the creation sequence) (If you know what to include, that's more than enough to solve it yourself) You're probably ahead to just use the normal defaults The people who set them up tend to know what they're doing. Depending on anyone else awake, you should get better info.
Problem with disk size
Hello all! I have an OpenBSD-box with two 250G drives inside (and some SCSI). Trying to use one of the drives as a whole gave this from disklabel $ sudo disklabel -p g wd0 [snip] 16 partitions: # sizeoffset fstype [fsize bsize cpg] c:233.8G 0.0G unused 0 0 # Cyl 0 -486343 d:233.8G 0.0G 4.2BSD 2048 16384 16 # Cyl 0*-486343* but df -h says: /dev/wd0d 7.8G7.4G4.2M 100% and I cant create any new files on the drive. What could be the problem here? Any hints appreciated. dmesg attached. Jon Sjvstedt _O_ OpenBSD 3.9 (GENERIC) #617: Thu Mar 2 02:26:48 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III (GenuineIntel 686-class) 665 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real mem = 536387584 (523816K) avail mem = 482426880 (471120K) using 4278 buffers containing 26923008 bytes (26292K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 05/31/00, BIOS32 rev. 0 @ 0xfdae0 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 30102 dobusy 0 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf7710/176 (9 entries) pcibios0: PCI Interrupt Router at 000:07:0 (VIA VT82C686 ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0x1 0xd/0x8000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 VIA VT82C691 PCI rev 0xc4 ppb0 at pci0 dev 1 function 0 VIA VT82C598 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 NVIDIA Riva TNT2 rev 0x15 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pcib0 at pci0 dev 7 function 0 VIA VT82C686 ISA rev 0x1b uhci0 at pci0 dev 7 function 2 VIA VT83C572 USB rev 0x0e: irq 12 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 7 function 3 VIA VT83C572 USB rev 0x0e: irq 12 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered viaenv0 at pci0 dev 7 function 4 VIA VT82C686 SMBus rev 0x20 ahc0 at pci0 dev 9 function 0 Adaptec AHA-2940U rev 0x00: irq 10 scsibus0 at ahc0: 16 targets sd0 at scsibus0 targ 0 lun 0: SEAGATE, ST39102LW, 0004 SCSI2 0/direct fixed sd0: 8683MB, 6962 cyl, 12 head, 212 sec, 512 bytes/sec, 17783240 sec total sd1 at scsibus0 targ 1 lun 0: SEAGATE, ST39102LW, 0004 SCSI2 0/direct fixed sd1: 8683MB, 6962 cyl, 12 head, 212 sec, 512 bytes/sec, 17783240 sec total sd2 at scsibus0 targ 2 lun 0: IBM, DNES-309170, SAH0 SCSI3 0/direct fixed sd2: 8748MB, 11474 cyl, 5 head, 312 sec, 512 bytes/sec, 17916240 sec total cd0 at scsibus0 targ 3 lun 0: SONY, CD-RW CRX140S, 1.0e SCSI4 5/cdrom removable pciide0 at pci0 dev 10 function 0 CMD Technology PCI0680 rev 0x02 pciide0: bus-master DMA support present pciide0: channel 0 configured to native-PCI mode pciide0: using irq 9 for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: Maxtor 6L250R0 wd0: 16-sector PIO, LBA48, 239372MB, 490234752 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 pciide0: channel 1 configured to native-PCI mode wd1 at pciide0 channel 1 drive 0: Maxtor 6L250R0 wd1: 16-sector PIO, LBA48, 239372MB, 490234752 sectors wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 5 dc0 at pci0 dev 11 function 0 Davicom DM9102 rev 0x31: irq 12, address 00:80:ad:72:3b:17 amphy0 at dc0 phy 1: DM9102 10/100 PHY, rev. 0 emu0 at pci0 dev 12 function 0 Creative Labs SoundBlaster Live rev 0x05: irq 11 ac97: codec id 0x54524123 (TriTech Microelectronics TR28602) audio0 at emu0 Creative Labs PCI Gameport Joystick rev 0x05 at pci0 dev 12 function 1 not configured isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec isapnp0 at isa0 port 0x279: read port 0x203 Maxi Sound 64 Series, ESS8600, , at isapnp0 port 0x800/8 not configured Maxi Sound 64 Series, ESS8601, , at isapnp0 port 0x220/16,0x388/4,0x300/2 irq 5 drq 1,0 not configured Maxi Sound 64 Series, ESS8602, , at isapnp0 port 0x201/1 not configured Maxi Sound 64 Series, ESS8603, , at isapnp0 port 0x330/6 irq 5 not configured biomask f765 netmask f765 ttymask f7e7 pctr: 686-class user-level performance counters enabled
Re: Problem with disk size
Jon Sjvstedt wrote: Hello all! I have an OpenBSD-box with two 250G drives inside (and some SCSI). Trying to use one of the drives as a whole gave this from disklabel $ sudo disklabel -p g wd0 [snip] don't snip. 16 partitions: # sizeoffset fstype [fsize bsize cpg] c:233.8G 0.0G unused 0 0 # Cyl 0-486343 d:233.8G 0.0G 4.2BSD 2048 16384 16 # Cyl 0*-486343* but df -h says: /dev/wd0d 7.8G7.4G4.2M 100% and I cant create any new files on the drive. What could be the problem here? Any hints appreciated. dmesg attached. thanks for the dmesg. You tried darned hard to obscure this (I really don't care how many G your disk is, I care about which sectors you are using), but it does appear that you opted to not properly partition your disk. The fact that you didn't show the output of fdisk causes me to believe you knew it, though you may not have recognized the significance. ;) Your OpenBSD subpartition appears to start at sector zero. Bad idea. This means, whether by design or by accident, you don't have an fdisk partition table (aka, MBR) on the disk. Also a bad idea. On some platforms, i386 is one of them, you must use fdisk partitions, and your disklabel partitions must start at a one track offset (in your case, probably 63 sectors). When you don't follow the rules, ugly things happen. It isn't the size of the disk, it's the way it's laid out that is giving you problems. See faq14.html... Nick.
