disklabel error
Good day all, I am trying to install 7.0 RC1 on an old Dell laptop. However it fails to create the swap partition. The message I keep getting is: Unable to find device node for /dev/ad0s1b in /dev!. The creation of filesystem will be aborted. Is there a way around it? Thanks in advance, Michael Michael Sherman http://msherman77.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: disklabel error in 4.11 release
At 03:21 PM 4/10/2007, fbsd bsd wrote: Hey *, having a bit of a problem with disklabel. A bit of background. I'm building a lab with Olive boxes in it (http://juniper.cluepon.net/index.php/Olive), which are basically i386 machines running JunOS. Please note that this whole procedure is entirely unsupported by Juniper and I would never *ever* recommend anyone run production traffic on an Olive box. At any rate, it requires a base install of FBSD 4.11, which you then do a pkg_add of their software over. The problem I'm having is that the package add fails every time. I personally have no experience with disklabel so it took me a bit to track down, but it seems like the raw device is not allowing anything to edit the first sectors. Keep in mind that an Olive install effectively turns your BSD box into a Juniper box, so the boot procedure will be different, which is why I'm leaning toward this. Also, this is the output of disklabel querying the kernel, then the device. olive1# disklabel ad4 # /dev/ad4: type: unknown disk: amnesiac label: fictitious flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 9726 sectors/unit: 15625 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 156250unused0 0# (Cyl.0 - 9726*) olive1# olive1# olive1# olive1# olive1# olive1# olive1# disklabel -r ad4 disklabel: bad pack magic number (label is damaged, or pack is unlabeled) olive1# Attempts to use disklabel -e to edit the device label end in: :q disklabel: Operation not supported by device re-edit the label? [y]: n olive1# Finally, here is the failure of the pkg_add: olive1# pkg_add jinstall-7.2R4.2-domestic-signed.tgz Verified SHA1 checksum of jinstall-7.2R4.2-domestic.tgz Adding jinstall... sysctl: unknown oid 'hw.re.model' disklabel: bad pack magic number (label is damaged, or pack is unlabeled) WARNING: This package will load JUNOS 7.2R4.2 software. WARNING: It will save JUNOS configuration files, and SSH keys WARNING: (if configured), but erase all other files and information WARNING: stored on this machine. It will attempt to preserve dumps WARNING: and log files, but this can not be guaranteed. This is the WARNING: pre-installation stage and all the software is loaded when WARNING: you reboot the system. Saving the config files ... Installing the bootstrap installer ... disklabel: bad pack magic number (label is damaged, or pack is unlabeled) WARNING: Failed while trying to install bootstrap loaders Deleting bootstrap installer ... disklabel: bad pack magic number (label is damaged, or pack is unlabeled) WARNING: This installation attempt will be aborted. WARNING: If you wish to force the installation despite these warnings WARNING: you may use the 'force' option on the command line. pkg_add: install script returned error status pkg_add: install script returned error status olive1# If anyone has any tips I'd appreciate it. sysinstall will label the disks as part of the install. Is the hardware preventing the boot area from being written to? It would appear that this is the case. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: disklabel error in 4.11 release
On Tue, Apr 10, 2007 at 01:21:18PM -0700, fbsd bsd wrote: Hey *, having a bit of a problem with disklabel. A bit of background. I'm building a lab with Olive boxes in it (http://juniper.cluepon.net/index.php/Olive), which are basically i386 machines running JunOS. Please note that this whole procedure is entirely unsupported by Juniper and I would never *ever* recommend anyone run production traffic on an Olive box. At any rate, it requires a base install of FBSD 4.11, which you then do a pkg_add of their software over. The problem I'm having is that the package add fails every time. I personally have no experience with disklabel so it took me a bit to track down, but it seems like the raw device is not allowing anything to edit the first sectors. Keep in mind that an Olive install effectively turns your BSD box into a Juniper box, so the boot procedure will be different, which is why I'm leaning toward this. Also, this is the output of disklabel querying the kernel, then the device. olive1# disklabel ad4 # /dev/ad4: type: unknown disk: amnesiac label: fictitious flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 9726 sectors/unit: 15625 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 156250unused0 0# (Cyl.0 - 9726*) olive1# olive1# olive1# olive1# olive1# olive1# olive1# disklabel -r ad4 disklabel: bad pack magic number (label is damaged, or pack is unlabeled) olive1# Attempts to use disklabel -e to edit the device label end in: :q disklabel: Operation not supported by device re-edit the label? [y]: n olive1# I don't know ab out the pkg_add below but that seems to be a later problem anyway. First comes disklabel issues. Three things to consider: Do you really have a drive 'ad4'? that would be the 5th ide type drive on the machine. If not, then you need to straighten out your drive designators. If you do have an ad4 (see dmesg to check), then you are attempting what they call a 'dangerously dedicated' drive by putting on a label without creating slices and putting the label in there. Maybe that is what is expected if this system you are trying to install mucks with the boot sector. But, it could also indicate you are not quite doing what you want. Be sure about what you are doing. What drive/slice/partition are you booted to? If it is to ad4 then the system probably will not allow you (or pkg_add) to write to that disk slice table or partition table - which, by the way, must be done as root. Finally, here is the failure of the pkg_add: olive1# pkg_add jinstall-7.2R4.2-domestic-signed.tgz Verified SHA1 checksum of jinstall-7.2R4.2-domestic.tgz Adding jinstall... I don't see anywhere that you are saying where to install this stuff so I assume it is on the drive that you are running from. In that case, is it trying to write to a drive slice table or boot block that you are running from?As above, that isn't allowed. Anyway, as is probably obvious, I am not familiar with this piece of software you are trying to install so I don't know just what to expect from it. One more thing to ask: Is it really necessary to try to install it in such an old version of FreeBSD? Will it not work in FreeBSD 6.2? That would be better if it can be done. jerry sysctl: unknown oid 'hw.re.model' disklabel: bad pack magic number (label is damaged, or pack is unlabeled) WARNING: This package will load JUNOS 7.2R4.2 software. WARNING: It will save JUNOS configuration files, and SSH keys WARNING: (if configured), but erase all other files and information WARNING: stored on this machine. It will attempt to preserve dumps WARNING: and log files, but this can not be guaranteed. This is the WARNING: pre-installation stage and all the software is loaded when WARNING: you reboot the system. Saving the config files ... Installing the bootstrap installer ... disklabel: bad pack magic number (label is damaged, or pack is unlabeled) WARNING: Failed while trying to install bootstrap loaders Deleting bootstrap installer ... disklabel: bad pack magic number (label is damaged, or pack is unlabeled) WARNING: This installation attempt will be aborted. WARNING: If you wish to force the installation despite these warnings WARNING: you may use the 'force' option on the command line. pkg_add: install script returned error status pkg_add: install script returned error status olive1# If anyone has any tips I'd appreciate it. - Be a PS3 game guru. Get your game face on with the latest PS3 news and previews at Yahoo! Games.
4.5 to 4.8, disks not mounting now -- w/ disklabel error output
Sorry, I should have included this output as well: fs3# disklabel -r ad4 disklabel: bad pack magic number (label is damaged, or pack is unlabeled) --Bill McMilleon quoting previous posting below: - I have a Pentium 233 that was running 4.5-RELEASE whose boot drive went belly up last week. Fortunately, I have a atapci1: Promise TX2 ATA133 controller which provides access to my primary data drives, so merely replacing the failed boot drive that lived on the onboard ide controller would not result in a loss of critical data. Unfortunately, it appears that the fresh install of 4.8-RELEASE on a new, replacement boot drive is unable to mount the old drives on the Promise controller. Dmesg output still conveys that the controller and drive names (ad4, ad5, ad7) are found, but disklabel reports disklabel: bad pack magic number (label is damaged, or pack is unlabeled) and attempts to mount fail. Please see below. I am inexperienced at migrations like this, and fear the loss of this large amount of critical data. See details below. Any help is appreciated. Thx. --Bill McMilleon Selected dmesg output: atapci0: Intel PIIX3 ATA controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: Intel 82371SB (PIIX3) USB controller at 7.2 irq 10 atapci1: Promise TX2 ATA133 controller port 0x7400-0x740f,0x7000-0x7003,0x6c00 -0x6c07,0x6800-0x6803,0x6400-0x6407 mem 0xe002-0xe0023fff irq 9 at device 13 .0 on pci0 ata2: at 0x6400 on atapci1 ata3: at 0x6c00 on atapci1 . . . ad0: 8809MB QUANTUM FIREBALLP KA9.1 [17898/16/63] at ata0-master WDMA2 ad4: 117800MB IC35L120AVVA07-0 [239340/16/63] at ata2-master UDMA100 ad5: 171705MB WDC WD1800BB-00DAA0 [348861/16/63] at ata2-slave UDMA100 ad7: 156334MB Maxtor 4G160J8 [317632/16/63] at ata3-slave UDMA133 acd0: DVD-ROM AOpen Inc. DVD-ROM DVD-1640 PRO 0122 at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a WARNING: R/W mount of /i120g denied. Filesystem is not clean - run fsck Fstab (failing mounts commented out): /dev/ad0s1b noneswapsw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1f /tmpufs rw 2 2 /dev/ad0s1g /usrufs rw 2 2 /dev/ad0s1e /varufs rw 2 2 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 #/dev/ad4s1e/disks/stashufs rw 2 2 #/dev/ad5s1e/disks/main ufs rw 2 2 #/dev/ad7s1e/disks/mediaufs rw 2 2 proc/proc procfs rw 0 0 Typical fdisk output (ad5 and ad7 are similar): fs3# fdisk -s ad4 /dev/ad4: 15017 cyl 255 hd 63 sec PartStartSize Type Flags 1: 63 241248042 0xa5 0x80 Typical disklabel output (again, ad5 and ad7 similar): fs3# disklabel ad4 # /dev/ad4: type: unknown disk: amnesiac label: fictitious flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 15017 sectors/unit: 241254720 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 2412547200unused0 0# (Cyl.0 - 15017*) _ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fdisk/disklabel - Error: unable to write data to disk ad0
On Sat, May 31, 2003 at 07:05:56PM +0200 or thereabouts, Herbert seemed to write: Hei! On Thursday May 29th I installed FreeBSD 5.1 Beta2. The next day I've update to CURRENT from May 30th. I have a 60 GB ATA harddisk and during installation I created only 1 20 GB slice for FreeBSD. Today I wanted to use the other 40 GB of my hard disk and create two more slices each 20 GB. Well, fdisk reports that the disk geometry is wrong and sets it to 7476/255/63, the same disk geometry the BIOS reports. When I try to save the changes in fdisk, I get the following error messages: Error: Unable to write data to disk ad0 Disk partition write returned an error status! It's GEOM preventing you from shooting yourself in the foot. Feature, not bug :-) Hmm, I tried both in multiuser and singleuser mode. Finally I booted with the floppies I had used to setup FreeBSD 5.1B2. Fdisk also reports that the disk geometry is wrong and sets it to 7476/255/63. But creating the slices and saving the changes did work: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) [snip] The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BS [snip] The data for partition 3 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) [snip] The data for partition 4 is: UNUSED Now I have booted FreeBSD from hard disk and try to create partitions within the new slices. But again I get: Error: unable to write data to disk ad0 Now I am booting with the install floppies again. I guess this is working fine. Any ideas what I am doing wrong? Nothing - you should boot from install floppy to partition any drive which is even partially being used, even if you don't change the used parts. (I had this problem too due to a swapspace on the drive.) HTH, -- Josh Regards, Herbert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
