Sponsored Content
Operating Systems Solaris BAD magic number in disc label... Post 302380057 by amrut_k on Monday 14th of December 2009 05:04:19 AM
Old 12-14-2009
Thanks for ur time n reply...
it means my HDD is not detected by system..?
i have changed my HDD to for this reason already....
will check another HDD again,as u suggested..
thanks...

plz check if any other solution is available or not..?

Thanks & Regards
Amrut_K
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

bad magic number

Hi, when installing a piece of third part software I get the error "Bad magic number" at one point when it tries to use libraries from the bea tuxedo server. Am I correct that this means that the software is expecting 32bit while I'm on 64bit? Is there a way around it or can it only be solved... (5 Replies)
Discussion started by: rein
5 Replies

2. Solaris

Big UH-OH "Bad magic number in disk label"

I tried rebooting my Sun server just a few minutes ago and I got the following at boot: -- Sun Fire 280R (UltraSPARC-III+) , No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.5, 1024 MB memory installed, Serial #xxxxxxxxx Ethernet address... (6 Replies)
Discussion started by: deckard
6 Replies

3. Filesystems, Disks and Memory

Bad Magic Number

Dear All, i have a SCSI hard disk drive i'm installing on it solaris 5 and the workstation is sun sparc, i made an image of this H.D using Norton Ghost 6, so i took off the SCSI H.D from the sun workstation and put it on a Compaq server then i booted the server from the Norton Ghost floppy disk... (0 Replies)
Discussion started by: wesweshahaha
0 Replies

4. UNIX for Advanced & Expert Users

Bad magic number on /dev/md0

Hello All, (RHEL4) Few weeks ago I had posted a message in this forum about the problem I had when I replaced my two scsi disks and tried rebuild raid1 array. I somehow managed to up the system with working raid1 array. But the main problem persisted.. i.e when I reboot the system, mounting... (0 Replies)
Discussion started by: ravinandan
0 Replies

5. Solaris

Solaris 8.2 Bad magic number

I'll keep it fairly straight forward. I work with a Solaris server and magically today it decided to take a dump on me. At first it give a long list of files that couldn't be acessed before terminating the boot process and returning to the 'ok' prompt. Booting in single-user mode allowed me to run... (4 Replies)
Discussion started by: Aon
4 Replies

6. Solaris

cpio: Bad magic number/header.

Hi, i got the following error while unpacking the archive file. cpio -icvd < as_sun_x86_101202_disk2.cpio Disk2/stage/Components/oracle.webdb.wwdoc/10.1.2.0.1/1/DataFiles/wwdoc.jar Disk2/stage/Components/oracle.webdb.wwdoc/10.1.2.0.1/1/DataFiles... (2 Replies)
Discussion started by: malikshahid85
2 Replies

7. Solaris

corrupt label - wrong magic number

I have created 1 LUN. 1)LUN 00BB 200GB /dev/rdsk/c1t3d44 /dev/rdsk/c2t28d44 /dev/rdsk/c3t19d44 /dev/rdsk/c4t12d44 2) Already added the new entry into sd.conf and rebooted. 3) Already done these: powercf –q power config 4) power display dev=all I can see the new Symmetrix device.... (1 Reply)
Discussion started by: sirius20d
1 Replies

8. Solaris

Recover label, wrong magic number

Is there a way to recover label? I could install (sparc) Solaris again, but it would take a lot of time. (5 Replies)
Discussion started by: orange47
5 Replies

9. Solaris

Bad magic number error

So we have a new to us v240 server with no OS installed. It has an outdated version of OB and ALOM so before we install the OS we want to update both. We have a DVD with the latest OB patch burned on it. We do the boot cdrom command but receive the Bad Magic Number Error. Does an OS need to... (2 Replies)
Discussion started by: dunkpancakes
2 Replies

10. Solaris

Bad magic number in disk label.

This is first time post...found this forum when looking for possible solution to fix my sun pc. Just one day can't boot it already showing the following: Boot device: disk File args: Bad magic number in disk label Can't open disk label package Evaluating: boot Can't open boot device... (40 Replies)
Discussion started by: SHuKoSuGi
40 Replies
UMASS(4)						   BSD Kernel Interfaces Manual 						  UMASS(4)

NAME
umass -- USB Mass Storage Devices driver SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device scbus device usb device umass Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): umass_load="YES" DESCRIPTION
The umass driver provides support for Mass Storage devices that attach to the USB port. To use the umass driver, usb(4) and one of uhci(4) or ohci(4) must be configured in the kernel. Additionally, since umass uses the SCSI sub- system and sometimes acts as a SCSI device, it requires da(4) and scbus(4) to be included in the kernel. HARDWARE
The umass driver supports USB Mass Storage devices, including: o ADTEC Stick Drive AD-UST32M, 64M, 128M, 256M o Denno FireWire/USB2 Removable 2.5-inch HDD Case MIFU-25CB20 o FujiFilm Zip USB Drive ZDR100 USB A o GREEN HOUSE USB Flash Memory "PicoDrive" GH-UFD32M, 64M, 128M o Huawei Mobile (SD slot) o IBM 32MB USB Memory Key (P/N 22P5296) o IBM 256MB USB Drive (MSYSTEM DiskOnKey2) o IBM ThinkPad USB Portable CD-ROM Drive (P/N 33L5151) o I-O DATA USB CD/CD-R/CD-RW/DVD-R/DVD-RW/DVD-RAM/DVD-ROM Drive DVR-iUH2 (CDROM, DVD-RAM only) o I-O DATA USB x6 CD-RW Drive CDRW-i64/USB (CDROM only) o I-O DATA USB/IEEE1394 Portable HD Drive HDP-i30P/CI, HDP-i40P/CI o Iomega USB Zip 100/250 drive o Iomega Zip750 USB2.0 drive o Keian USB1.1/2.0 3.5-inch HDD Case KU350A o Kurouto Shikou USB 2.5-inch HDD Case GAWAP2.5PS-USB2.0 o LaCie P3 HardDrive USB 200GB o Logitec LDR-H443U2 DVD-RAM/-R/+R/-RW/+RW drive o Logitec Mobile USB Memory LMC-256UD o Logitec USB1.1/2.0 HDD Unit SHD-E60U2 o Logitec USB Double-Speed Floppy Drive LFD-31U2 o Logitec USB/IEEE1394 DVD-RAM/R/RW Unit LDR-N21FU2 (CDROM only) o MELCO USB Flash Disk "ClipDrive", RUF-C32M, -C64M, -C128M, -C256M, -C512M o MELCO USB Flash Disk "PetitDrive", RUF-32M, -64M, -128M, -256Mm o MELCO USB2.0 Flash Disk "PetitDrive2", RUF-256M/U2, -512M/U2 o MELCO USB2.0 MO Drive MO-CH640U2 o Matshita CF-VFDU03 floppy drive o Merlin SM300 MP3/WMA Player (256Mb) o Microtech International, Inc. USB-SCSI-HD 50 USB to SCSI cable o Motorola E398 Mobile Phone (TransFlash memory card) o NOVAC USB2.0 2.5/3.5-inch HDD Case NV-HD351U o PNY Attache Flash Drive o Panasonic ("Matshita FDD CF-VFDU03") o Panasonic KXL-CB20AN Portable DVD-ROM/CD-R/RW o Panasonic KXL-CB35AN (DVD-ROM & CD-R/RW) o Panasonic USB2.0 Portable CD-RW Drive KXL-RW40AN (CDROM only) o Panasonic floppy drive o Qware BeatZkey! Pro o RATOC Systems USB2.0 Removable HDD Case U2-MDK1, U2-MDK1B o SanDisk SDDR-31 (Compact Flash) o SanDisk SDDR-75 (only Compact Flash port works) o Sitecom CN-300 MultiFlash (MMC/SD, SmartMedia, CF, MemoryStick) o Sony Portable CD-R/RW Drive CRX10U (CDROM only) o TEAC Portable USB CD-ROM Unit CD-110PU/210PU o Time DPA20B MP3 Player (1Gb) o Trek Thumbdrive 8MB o VAIO floppy drive (includes Y-E Data Flashbuster-U) o Y-E Data floppy drive (720/1.44/2.88Mb) Among the supported digital cameras are: o Asahi Optical (PENTAX) Optio 230 & 330 EXAMPLES
device umass device scbus device da device pass Add the umass driver to the kernel. camcontrol rescan 0 Rescan a Zip drive that was added after boot. The command above assumes that the Zip drive is on the first SCSI bus in the system. camcontrol rescan 0:0:0 camcontrol rescan 0:0:1 camcontrol rescan 0:0:2 camcontrol rescan 0:0:3 Rescan all slots on a multi-slot flash reader, where the slots map to separate LUNs on a single SCSI ID. Typically only the first slot will be enabled at boot time. Again, this assumes that the flash reader is the first SCSI bus in the system. bsdlabel -w da0 zip100 newfs da0c mount -t ufs /dev/da0c /mnt Write a disklabel to the Zip drive (see vpo(4) for the disktab(5) entry), creates the file system and mounts the new file system on /mnt. newfs_msdos /dev/da0 Create a new FAT type file system. Care should be taken not to run newfs(8) on devices that already contain data, as this will result in the information being lost. Many consumer devices such as digital cameras automatically create MS-DOS based file systems when storing information such as images and videos. These file systems can be accessed by specifying the file system type as msdos when using mount(8). SEE ALSO
ehci(4), ohci(4), uhci(4), usb(4), vpo(4), disktab(5), bsdlabel(8), camcontrol(8) AUTHORS
The umass driver was written by MAEKAWA Masahide <bishop@rr.iij4u.or.jp> and Nick Hibma <n_hibma@FreeBSD.org>. This manual page was written by Nick Hibma <n_hibma@FreeBSD.org>. BSD
October 22, 2009 BSD
All times are GMT -4. The time now is 02:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy