newfs: cg 0: bad magic number
Hi *, I'm trying to build a new FS on an IDE disk. All newfs commands end with: # newfs /dev/rwd1a .. .. newfs: cg 0: bad magic number newfs: fsinit1 failed Here is the disk info: # disklabel wd1 # /dev/rwd1c: type: ESDI disk: ESDI/IDE disk label: Maxtor 6B250R0 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 30515 total sectors: 490234752 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a:481950 4.2BSD 2048 16384 16 c:4902347520 unused 0 0 (I tried several fs size (stard or end of the disk, same error) Any idea? Xavier -- Weird enough for government work.
Re: newfs: cg 0: bad magic number
Strange... fdisk wd1 reports: # fdisk wd1 Disk: wd1 geometry: 30515/255/63 [490234752 Sectors] Offset: 0 Signature: 0x180 Starting EndingLBA Info: #: id C H S - C H S [ start:size ] 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused When I create some partitions, write them to the disk, restart fdisk, I'm back to the same empty config. Is my disk physically dead? :( Xavier -- There's no place like ~ On Thu, 3 Jan 2008, Xavier Mertens wrote: Hi *, I'm trying to build a new FS on an IDE disk. All newfs commands end with: # newfs /dev/rwd1a .. .. newfs: cg 0: bad magic number newfs: fsinit1 failed Here is the disk info: # disklabel wd1 # /dev/rwd1c: type: ESDI disk: ESDI/IDE disk label: Maxtor 6B250R0 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 30515 total sectors: 490234752 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a:481950 4.2BSD 2048 16384 16 c:4902347520 unused 0 0 (I tried several fs size (stard or end of the disk, same error) Any idea? Xavier -- Weird enough for government work.
Re: newfs: cg 0: bad magic number
Indeed, this test was bad...
But the same occurs with an offset of 63 sectors :(
Same with fdisk:
fdisk: 1 edit 3
Starting EndingLBA Info:
#: id C H S - C H S [ start:size ]
3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
Partition id ('0' to disable) [0 - FF]: [0] (? for help) A6
Do you wish to edit in CHS mode? [n]
offset: [0] 63
size: [0] 488392002
fdisk:*1 q
Writing current MBR to disk.
bash-3.2# fdisk wd1
Disk: wd1 geometry: 30515/255/63 [490234752 Sectors]
Offset: 0 Signature: 0x100
Starting EndingLBA Info:
#: id C H S - C H S [ start:size ]
0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
Xavier
--
Secret hacker rule #11: hackers read manuals.
On Wed, 2 Jan 2008, Nick Holland wrote:
Good thing OpenBSD only runs on one platform and one type of computer,
eh?
Xavier Mertens wrote:
..
16 partitions:
#size offset fstype [fsize bsize cpg]
a:481950 4.2BSD 2048 16384 16
c:4902347520 unused 0 0
Assuming this is i386 (what people usually assume when they don't
bother to show dmesg or even mention platform), you need a one
cylinder offset on your 'a' partition (or more accurately, your
first partition. TYPICALLY, that's 63 sectors, but not always).
What you have here clobbers your MBR, which holds your (now hosed)
fdisk partitions.
see faq4.html.
Nick.
Re: newfs: cg 0: bad magic number
Ok, I fixed the disk partitions: # fdisk wd1 Disk: wd1 geometry: 30515/255/63 [490234752 Sectors] Offset: 0 Signature: 0x0 Starting EndingLBA Info: #: id C H S - C H S [ start:size ] 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: A6 0 1 1 - 30514 254 63 [ 63: 490223412 ] OpenBSD 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused # disklabel wd1 # Inside MBR partition 1: type A6 start 63 size 490223412 # /dev/rwd1c: type: ESDI disk: ESDI/IDE disk label: Maxtor 6B250R0 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 30515 total sectors: 490234752 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a:490223412 63 4.2BSD 2048 16384 16 c:4902347520 unused 0 0 But I still have the same error at the end of the newfs: newfs: cg 0: bad magic number newfs: fsinit1 failed :( Xavier -- Hint: A reload a day, keeps the TAC away . On Wed, 2 Jan 2008, Ted Unangst wrote: On 1/2/08, Xavier Mertens [EMAIL PROTECTED] wrote: 16 partitions: #size offset fstype [fsize bsize cpg] a:481950 4.2BSD 2048 16384 16 your partition is not properly offset from the beginning of the disk, where all the goodies like mbr need to live.
Re: newfs: cg 0: bad magic number
Is that normal to have a signature of 0x0 reported by fdisk? On my other disks, signature is 0xAA55. Thanks for your help! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Xavier Mertens Sent: jeudi 3 janvier 2008 2:28 To: misc@openbsd.org Subject: Re: newfs: cg 0: bad magic number Ok, I fixed the disk partitions: # fdisk wd1 Disk: wd1 geometry: 30515/255/63 [490234752 Sectors] Offset: 0 Signature: 0x0 Starting EndingLBA Info: #: id C H S - C H S [ start:size ] 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: A6 0 1 1 - 30514 254 63 [ 63: 490223412 ] OpenBSD 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused # disklabel wd1 # Inside MBR partition 1: type A6 start 63 size 490223412 # /dev/rwd1c: type: ESDI disk: ESDI/IDE disk label: Maxtor 6B250R0 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 30515 total sectors: 490234752 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a:490223412 63 4.2BSD 2048 16384 16 c:4902347520 unused 0 0 But I still have the same error at the end of the newfs: newfs: cg 0: bad magic number newfs: fsinit1 failed :( Xavier -- Hint: A reload a day, keeps the TAC away . On Wed, 2 Jan 2008, Ted Unangst wrote: On 1/2/08, Xavier Mertens [EMAIL PROTECTED] wrote: 16 partitions: #size offset fstype [fsize bsize cpg] a:481950 4.2BSD 2048 16384 16 your partition is not properly offset from the beginning of the disk, where all the goodies like mbr need to live.
OpenBSD on VMware
Hi *, I'm running a 4.1-GENERIC on a VMware server (the VMare host runs a Microsoft Windows OS). I've no access to the VMware server. At random time, the server is just powered off (that's the feedback I always received from the VMware server administrator). There is nothing in logs and as the server is off, the console is not available anymore. :( Does somebody already experienced such issue? Any tips to run OBSD as VMware guest? Regards, Xavier PS: I'm using pcn as network driver. Maybe vmnet could increase performance and/or stability?
Re: OpenBSD on VMware
It's a VMware server 1.0.3. I've no more info about the config. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of PowerBSD Sent: lundi 26 novembre 2007 8:17 To: misc@openbsd.org Subject: Re: OpenBSD on VMware On Mon, Nov 26, 2007 at 07:56:16AM +0100, Xavier Mertens wrote: Hi *, I'm running a 4.1-GENERIC on a VMware server (the VMare host runs a Microsoft Windows OS). I've no access to the VMware server. At random time, the server is just powered off (that's the feedback I always received from the VMware server administrator). There is nothing in logs and as the server is off, the console is not available anymore. :( Does somebody already experienced such issue? Any tips to run OBSD as VMware guest? Regards, Xavier PS: I'm using pcn as network driver. Maybe vmnet could increase performance and/or stability? I always runs openbsd on vmware , but the vware version is workstation 6.0.2.59824 . you may post your vmware server version.
Re: OpenBSD on VMware
Ok, the only fix that explains my issue is this one: This release fixes a problem that resulted from a conflict between Linux guest operating systems with kernel version 2.6.21 and RTC-related processes on the host. This problem caused the virtual machine to quit unexpectedly. Could you give me more details? As the VMware server is not under my control, I need to have good arguments to ask them to upgrade! :( /x -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of PowerBSD Sent: lundi 26 novembre 2007 8:33 To: misc@openbsd.org Subject: Re: OpenBSD on VMware On Mon, Nov 26, 2007 at 08:15:03AM +0100, Xavier Mertens wrote: It's a VMware server 1.0.3. I've no more info about the config. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of PowerBSD Sent: lundi 26 novembre 2007 8:17 To: misc@openbsd.org Subject: Re: OpenBSD on VMware On Mon, Nov 26, 2007 at 07:56:16AM +0100, Xavier Mertens wrote: Hi *, I'm running a 4.1-GENERIC on a VMware server (the VMare host runs a Microsoft Windows OS). I've no access to the VMware server. At random time, the server is just powered off (that's the feedback I always received from the VMware server administrator). There is nothing in logs and as the server is off, the console is not available anymore. :( Does somebody already experienced such issue? Any tips to run OBSD as VMware guest? Regards, Xavier PS: I'm using pcn as network driver. Maybe vmnet could increase performance and/or stability? I always runs openbsd on vmware , but the vware version is workstation 6.0.2.59824 . you may post your vmware server version. read this link : http://www.vmware.com/support/server/doc/releasenotes_server.html#resolved
systrace/stsh policies
Hi *, I'm busy with a systrace/stsh implementation but there is a lack of standard policies (IMHO). Any idea where I can find some ready-to-use policies? I must be missing some important ones, when the user logs in, he got immediately the following error: systrace: getcwd: Permission denied Xavier -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Problem with new IDE disk
Hi *, I just reinstalled a box (running -CURRENT). I added a third IDE drive: wd2 at pciide0 channel 1 drive 1: WDC WD2500JB-00REA0 wd2: 16-sector PIO, LBA48, 238475MB, 488397168 sectors wd2(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 5 dkcsum: wd2 matches BIOS drive 0x82 It will be fully dedicated to OpenBSD so, I issued the following commands: # fdisk -i wd2 # disklabel -E wd2 (created 'a' partition) # newfs wd2a == Errors! wd2a: id not found writing fsbn 488397104 (wd2 bn 8796581419375; cn 547561868 tn 158 sn 1), retrying wd2: transfer error, downgrading to Ultra-DMA mode 4 wd2(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 4 wd2a: id not found writing fsbn 488397104 (wd2 bn 8796581419375; cn 547561868 tn 158 sn 1), retrying wd2: transfer error, downgrading to Ultra-DMA mode 3 wd2(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 3 wd2a: id not found writing fsbn 488397104 (wd2 bn 8796581419375; cn 547561868 tn 158 sn 1), retrying I booted the box with a Knoppix CD and I was able to create an ext3 fs on the disk. The filesystem was successfully mounted under OpenBSD and I/O were correct. Any idea why newfs failed? Regards, Xavier -- The three Rs of Microsoft support: Retry, Reboot, Reinstall.
Re: Problem with new IDE disk
Argh! So stupid! I just started a rebuild of userland tools... I'll keep you informed. Tx Miod! Xavier -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie) On Thu, 23 Aug 2007, Miod Vallat wrote: # fdisk -i wd2 # disklabel -E wd2 (created 'a' partition) # newfs wd2a [...] wd2a: id not found writing fsbn 488397104 (wd2 bn 8796581419375; cn 547561868 tn 158 sn 1), retrying It looks like you are indeed running a -CURRENT (or fairly recent) kernel, but with an older userland. Are you sure your fdisk, disklabel and newfs binaries are on par with the kernel? Miod
Re: Problem with new IDE disk
Ok, problem solved, it was indeed a mismatch between kernel userland! Tx! Xavier -- The first time that Microsoft makes a product that doesn't suck will be when they start making vacuum cleaners! On Thu, 23 Aug 2007, Miod Vallat wrote: # fdisk -i wd2 # disklabel -E wd2 (created 'a' partition) # newfs wd2a [...] wd2a: id not found writing fsbn 488397104 (wd2 bn 8796581419375; cn 547561868 tn 158 sn 1), retrying It looks like you are indeed running a -CURRENT (or fairly recent) kernel, but with an older userland. Are you sure your fdisk, disklabel and newfs binaries are on par with the kernel? Miod
HTTP URL filtering?
Hi *, I've a problem with an Apache web server hit by f*cking spammers... I would like to filter some URLs (unused but still used by the bots) *BEFORE* they reach the httpd processes. What could be the best method? pf? something else? Thanks! Xavier
Thunderbird stability/usability?
hi *, A few days ago, my notebook disk died... Good opportunity to reinstall a fresh 3.9-GENERIC. My X environment is running fine (xfce4) but Thunderbird gives me some headaches... (mozilla-thunderbird-1.5.0.4.tgz) From time to time, when reading RSS feeds or HTML mails (Grrr), it just closes! (no crash, no core produced, no error). Another annoying behaviour: the GUI! Some windows are opened with a small size or without content!? (like password windows) Is that a problem related to my X environment? To Thunderbird? Regards, Xavier -- Secret hacker rule #11: hackers read manuals.
panic: semop - can't undo undos
Hi *, I got this panic today... I googled for this message and got a hit on the list archive: quote Otto Moerbeek wrote: On Thu, 8 Jun 2006, Michael Erdely wrote: panic: semop - can't undo undos your system is running out of semaphore undo data structures. Try increasing at least kern.seminfo.semmnu. Other semaphore related sysctl's might need an increase as well. Thanks, Otto. I'll give it a shot (increased semmnu to 40 for starters). /quote Anybody has more info about this problem? Increasing the kern.seminfo.semmnu solved the problem? Regards, Xavier -- Free shell account on www.rootshell.be!
CPU cache problem with 3.9 ?
Hi *, I found why my box freezes when booting 3.9 (GENERIC). I need to disable the CPU cache in the BIOS (PIII 1Ghz). But, of course, the box is slow... Anybody already had this issue? Xavier -- Free shell account on www.rootshell.be!
Help to debug Openbsd freezes...
Hi Gurus, I'm facing a strange and frustrating problem... I run a box with OpenBSD without problem for a while (2 years). It's still running 3.5 (ok, ok, don't shoot, it's an old one but upgrades are not easy). It's an i386 1U in a safe environment (colo) See attached dmesg below. For two weeks now, the box freezes randomly... No ping, no activity, capslock/keyboard don't work, no error on the console. The only solution is the magic-button :( I tested the disks: ok I replaced memory modules: ok (+memtest) I replaced two fans (for disk cooling) No new software has been installed not upgraded. If I check the symon logs, nothing special appends before the freeze Any advice? OpenBSD 3.5-current (GENERIC) #35: Thu Apr 15 19:35:46 MDT 2004 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III (GenuineIntel 686-class) 1 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,SER,MMX,FXSR,SSE real mem = 528068608 (515692K) avail mem = 481353728 (470072K) using 4278 buffers containing 26505216 bytes (25884K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(18) BIOS, date 05/15/01, BIOS32 rev. 0 @ 0xfb080 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown pcibios0 at bios0: rev. 2.1 @ 0xf/0xb500 pcibios0: PCI IRQ Routing Table rev. 1.0 @ 0xfd930/128 (6 entries) pcibios0: PCI Exclusive IRQs: 5 10 11 12 pcibios0: PCI Interrupt Router at 000:07:0 (VIA VT82C596A ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0xc000 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 VIA VT8601 PCI rev 0x05 ppb0 at pci0 dev 1 function 0 VIA VT82C601 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 Trident CyberBlade i1 rev 0x6a wsdisplay0 at vga1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pcib0 at pci0 dev 7 function 0 VIA VT82C686 ISA rev 0x40 pciide0 at pci0 dev 7 function 1 VIA VT82C571 IDE rev 0x06: ATA100, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: IC35L060AVV207-0 wd0: 16-sector PIO, LBA48, 58644MB, 120103200 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: QSI, CD-ROM SCR-242, CQ26 SCSI0 5/cdrom removable wd1 at pciide0 channel 1 drive 1: ST320414A wd1: 16-sector PIO, LBA, 19092MB, 39102336 sectors cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 wd1(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2 uhci0 at pci0 dev 7 function 2 VIA VT83C572 USB rev 0x16: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA UHCI root hub, class 9/0, 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 0x16: irq 11 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: VIA UHCI root hub, class 9/0, 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 0x40 auvia0 at pci0 dev 7 function 5 VIA VT82C686 AC97 Audio rev 0x50: irq 5 ac97: codec id 0x49434511 (ICEnsemble ICE1232) ac97: codec features headphone, 18 bit DAC, 18 bit ADC, KS Waves 3D audio0 at auvia0 dc0 at pci0 dev 9 function 0 Lite-On PNIC rev 0x20: irq 10, address 00:a0:cc:29:69:4c mtdphy0 at dc0 phy 1: MTD972 10/100 media interface, rev. 8 rl0 at pci0 dev 14 function 0 Realtek 8139 rev 0x10: irq 11 address 00:10:dc:04:83:a9 rlphy0 at rl0 phy 0: RTL internal phy 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 sysbeep0 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 biomask c840 netmask cc40 ttymask ccc2 pctr: 686-class user-level performance counters enabled mtrr: Pentium Pro MTRR support dkcsum: wd0 matched BIOS disk 80 dkcsum: wd1 matched BIOS disk 81 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 WARNING: / was not properly unmounted Xavier -- There are three kinds of death in this world. There's heart death, there's brain death, and there's being off the network.
RAID label problem?
Hi, I'm busy to set up a box with 2 x 80GB disks in RAID1. I'm following the procedures found online but, once the RAID is initialized, I got the follow error while trying to partition it: Write new label?: [y] disklabel: ioctl DIOCWDINFO: No space left on device disklabel: unable to write label The RAID is up, consistant: # raidctl -s raid0 raid0 Components: /dev/wd0d: optimal /dev/wd1d: optimal No spares. Parity status: clean Reconstruction is 100% complete. Parity Re-write is 100% complete. Copyback is 100% complete. disklabel report the following: # disklabel -E raid0 disklabel: Can't get bios geometry: Device not configured Initial label editor (enter '?' for help at any prompt) p device: /dev/rraid0c type: RAID disk: raid label: fictitious bytes/sector: 512 sectors/track: 128 tracks/cylinder: 8 sectors/cylinder: 1024 cylinders: 156417 total sectors: 160171392 free sectors: 160171392 rpm: 3600 16 partitions: # sizeoffset fstype [fsize bsize cpg] a: 4358414031416925149 unused 0 0 # Cyl 1383715*-1809342* c: 160171392 0 unused 0 0 # Cyl 0 -156417* I create my partition, exit with q Xavier -- SELECT * FROM users WHERE clue 0; 0 rows returned
Re: RAID label problem?
Well, I already tried to create only a small partition: # disklabel -E raid0 disklabel: Can't get bios geometry: Device not configured Initial label editor (enter '?' for help at any prompt) p device: /dev/rraid0c type: RAID disk: raid label: fictitious bytes/sector: 512 sectors/track: 128 tracks/cylinder: 8 sectors/cylinder: 1024 cylinders: 156417 total sectors: 160171392 free sectors: 160171392 rpm: 3600 16 partitions: # sizeoffset fstype [fsize bsize cpg] a: 4358414031416925149 unused 0 0 # Cyl 1383715*-1809342* c: 160171392 0 unused 0 0 # Cyl 0 -156417* d a a a offset: [0] size: [160171392] 200m FS type: [4.2BSD] p device: /dev/rraid0c type: RAID disk: raid label: fictitious bytes/sector: 512 sectors/track: 128 tracks/cylinder: 8 sectors/cylinder: 1024 cylinders: 156417 total sectors: 160171392 free sectors: 159761792 rpm: 3600 16 partitions: # sizeoffset fstype [fsize bsize cpg] a:409600 0 4.2BSD 2048 16384 16 # Cyl 0 - 399 c: 160171392 0 unused 0 0 # Cyl 0 -156417* q Write new label?: [y] y disklabel: ioctl DIOCWDINFO: No space left on device disklabel: unable to write label # Xavier -- Dear customer, we located the problem... It's between the keyboard and the chair! On Wed, 22 Mar 2006, Greg Oster wrote: Xavier Mertens writes: Hi, I'm busy to set up a box with 2 x 80GB disks in RAID1. I'm following the procedures found online but, once the RAID is initialized, I got the follow error while trying to partition it: Write new label?: [y] disklabel: ioctl DIOCWDINFO: No space left on device disklabel: unable to write label The RAID is up, consistant: # raidctl -s raid0 raid0 Components: /dev/wd0d: optimal /dev/wd1d: optimal No spares. Parity status: clean Reconstruction is 100% complete. Parity Re-write is 100% complete. Copyback is 100% complete. disklabel report the following: # disklabel -E raid0 disklabel: Can't get bios geometry: Device not configured Initial label editor (enter '?' for help at any prompt) p device: /dev/rraid0c type: RAID disk: raid label: fictitious bytes/sector: 512 sectors/track: 128 tracks/cylinder: 8 sectors/cylinder: 1024 cylinders: 156417 total sectors: 160171392 free sectors: 160171392 rpm: 3600 16 partitions: # sizeoffset fstype [fsize bsize cpg] a: 4358414031416925149 unused 0 0 # Cyl 1383715*-180 9342* c: 160171392 0 unused 0 0 # Cyl 0 -15641 7* 435841403 + 1416925149 = 1852766552 which is greater than 160171392 by 1692595160. If you fix the offset of 'a', I suspect things will be happier. Later... Greg Oster
Re: RAID label problem?
Thanks Otto! This fixed the problem... Xavier -- There are only 10 types of people in the world: Those who understand binary and those who don't. On Wed, 22 Mar 2006, Otto Moerbeek wrote: On Wed, 22 Mar 2006, Xavier Mertens wrote: 16 partitions: # sizeoffset fstype [fsize bsize cpg] a: 4358414031416925149 unused 0 0 # Cyl 1383715*-1809342* c: 160171392 0 unused 0 0 # Cyl 0 -156417* I create my partition, exit with q Xavier -- SELECT * FROM users WHERE clue 0; 0 rows returned You better run fdisk -i raid0 first. You are seeing the remains of an old disklabel, probably. -Otto
