DIsk labels on ST2510

Hello, all.
Is it possible to redefine disk labels on ST2510 to something looks like this c2t6d0?
Now I have:
4. c2t600A0B80003ACB430000030348B661EAd0 <SUN-LCSM100_I-0670-1.08TB>
/scsi_vhci/ssd@g600a0b80003acb430000030348b661ea
5. c2t600A0B80003AD200000002A648B66245d0 <SUN-LCSM100_I-0670-1.08TB>
Beforehand thanks.

No this isn't possible.
You are using MPxIO for the multipathing and it automatically defines the devices as you shown in your example.
Regards

Similar Messages

Boot image does not exist and cannot read disk label errors.

Hi - I'm having a problem with installing Solaris 9 4/04 on a Netra T1. The Netra already has Solaris 7. I need to get this set up as a jumpstart server but it can't find the boot image. I'm using a brand new bonafide installation disk - not a copy. The system won't let me install/upgrade to Solaris 9 either. I get an error stating that disk label can't be read. I've tried swapping out the CDROM but I still get the same errors. Does anyone know what or why this may be happening? (Oh - and another strange thing - like I said the CDs are the original but there doesn't appear to be a cdrom/cdrom0/s0 directory. The directory I see is cdrom/cdrom0/sol_9_404_sparc/Solaris_9/Tools)
ERROR: Install boot image /cdrom/sol_9_404_sparc/Solaris_9/Tools/Boot does not exist
Check that boot image exists, or use [-t] to
specify a valid boot image elsewhere.
and
Excuting last command: boot cdrom [- nowin]
Boot device: /pci@1f,0/pc1@1/ide/cdrom@2:f file and args: [- nowin]
Can't read disk label.
Can't open disk label package
Evaulating: boot cdrom [- nowin]@1/ide@e/cdrom@2:f File and args: [- nowin]
Can't open boot device
I appreciate any help at all - is there anyone out there who can tell me what I may be doing wrong?
Thanks

Hi check that you are booting of the right cd. Make sure it is soalris 9 software 1/2 if that fails then it may well be that your cd is buggered. most likely it is buggered it it cant find the boot image.

Is it possible to add tape name/reel name/disk label/etc on more than one clip at a time?

Just coming to grips with some potential media management nightmares and want to find out whether I'm just missing something in the literature. Using Adobe Premiere Pro CC is there any way to modify tape name/reel name/disk label/card number? In both Final Cut Pro and Avid this is pretty straight forward and you can do this on multiple clips, or one at a time. However, I've not seen an easy way of doing this in Premiere.
To be honest, I haven't seen any way of identifying roll/card name within Premiere. It may not be part of everyone's workflow, but it is a rather crucial step for ours, and we're not able to do this at the moment which is pretty frustrating.
Any suggestions would be greatly appreciated. I suppose if we've got to do them one at a time it'll be a nice, quiet afternoon hitting copy and paste for someone!
Thanks in advance.
Amy

so strange premiere cant read/import other metadata, after they tout they ready for the big time... you can enter multiple values for some metadata fields, such as tape name. if you highlight multiple clips in the project bin and have metadata panel open, you can then type in your comments/data in the metadata panel, and it will write it to all the highlighted clips. you can also right click the columns in the project bin panel to choose which metadata fields you want, create new metadata fields, and save the setup for other projects...

Sun Ultra 25 - Bad magic number in disk label

I have a Sun Ultra 25 SPARC that is booting fine to it's 80GB SATA drive. Solaris 10, OpenBoot 4.22.19.
Here's what I did:
I installed a 2TB Western Digital SATA drive into the HDD1 slot.
I formatted the disk in the HDD1 slot via the format command, labeled the disk, and divided it into partitions.
I then used newfs to build the ufs on all partitions.
I mirrored the disk in HDD0 to the disk in HDD1 using ufsdump for all partitions. The data is accessible and looks ok.
After this was done I did an installboot to /dev/rdsk/c1t1d0s0 (the / partition of the HDD1 slot).
I then did a fsck on every partition to verify that they are okay.
I then took the hard drive in HDD1 and put it in the HDD0 slot, now wanting to boot off that disk.
At the reboot:
Bad magic number in disk label
Can't open disk label package
If I do a probe-scsi:
MPT Version 1.05, Firmware Version 1.08.03.00
Target 0
Unit 0 Disk ATA WDC WD20EADS-00R0A01 3907029168 Bocks, 2000 GB SATA device PhyNum 0
As far as I can tell disk0 is the correct devalias which is:
/pci@1e,600000/pci@0/pci@9/pci@0/scsi@1/disk@0,0
I just don't understand how the fsck is okay, but the boot give bad magic number in disk label?
The 80GB drive in HDD slot 0 works fine with the boot disk0 command, all I'm doing is swapping a larger disk with the same data for the smaller disk.

if it is like any other Sun product, it needs to go through the format command and get a volname.... it is just a label, but it needs to be done.
haroldkarl

Can't read disk label

Dear Sun experts,
I am trying to install Solaris 9 on a Sun Ultra 10 Sparc workstation. This system formerly had Solaris 8 on it, but we decided to do a reinstallation to configure things the way we wanted them.Before doing that we encountered a few problems
1.The system failed to recognize the Dell Ultra Sharp Monitor, when the signal cable was plugged into the port behind the computer. To solve this we researched and were told to remove the Video card attached to the mother board, and this we did.The system now recognized the dell monitor and booted in Solaris 8.
2.We ran sys-unconfig to reconfigure the system to change the hostname on a reboot.We powered off the computer.Afterward we would go through the sys-unconfig program in an indefinite loop.So I powered off the computer each time i got stuck.
3.Lastly I tried to do a STOP A to try to go to the 'ok' prompt in order to do a clean installation of Solaris 8 Installation CD, by running
ok boot cdrom [ENTER]
Here's what I am getting:
Boot device: /pci@1f, 0/pci@1,1/ide@3/cdrom@2,0:f File and args:
Can't read disk label.
Can't open disk label package
Can't open boot device
ok
[end]
I want to do a clean installation of the Solaris 9 CD on the sparc ultra 10 computer.Please can anyone help me out? I looked at the solaris 9 installation guide, and it asked that I follow this procedure. Please respond if you can help.
Also of note is that I got this system from a user who had installed Solaris 8 sparc on it earlier.
Thanks a million!
Omon

Hi!
After a day fighting with same problem and found no good solution on the internet , I was able to do a workaround in order to be able to boot my sun bade 1500 that was giving the "can't open disk label" message.
I found no source of the problem but someone with more knowledge could guess. (maybe a default bad alias definition of cdrom ��?)
Well, first of all I plugued a normal IDE CDrom as primary slave, leaving IDE HD as primary master. And inserted solaris 8 installation CD (as it was my only solaris bootable CD, but I guess that I oculd boot any other CD).
After that, I went to the openboot prompt (ok>) and did next:
ok devalias cdrom - this will show you current path to internal CD. Use this to determine what new alias should look like.
ok setenv auto-boot? false
ok reset-all
ok probe-scsi-all - find the path to the new cdrom - write it down & write target # as well
ok show-disks - find the exact path you just wrote down and type that letter
ok nvalias cdrom2 [Ctrl] + [y] which will paste that path. Finish with @sd1,0:f AS IT's PRIMARY SLAVE
ok reset-all
ok boot cdrom2
I found this part in http://www.experts-exchange.com/Operating_Systems/Solaris/Q_ 20757891.html
except teh @sd1,0:f, I found that with my good luck!
After that I was able to boot with CD. the installation failed, but at least I was able to mount / filesystem and modify my /etc/passwd ... my target!
HTH
Cheers!

Sol_10 x86 5/08 disk label corruption (yes i have searched...)

I am truly sorry if the following is going to be a "oh no not this again" issue.
I am having an issue with 3 of my disks having "primary label corrupt: using backup" issues. Here is what I have tried and what has happened thusfar:
first I tried format, which core dumped
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
       0. c0d0 <drive type unknown>
          /pci@0,0/pci-ide@11/ide@0/cmdk@0,0
       1. c0d1 <drive type unknown>
          /pci@0,0/pci-ide@11/ide@0/cmdk@1,0
       2. c1d0 <drive type unknown>
          /pci@0,0/pci-ide@11/ide@1/cmdk@0,0
       3. c1d1 <DEFAULT cyl 30398 alt 2 hd 255 sec 63>
          /pci@0,0/pci-ide@11/ide@1/cmdk@1,0
       4. c3d0 <DEFAULT cyl 38910 alt 2 hd 255 sec 63>
          /pci@0,0/pci-ide@14,1/ide@1/cmdk@0,0
Specify disk (enter its number): 0
Segmentation Fault - core dumpedok, thats wierd (and it does it with the other "drive type unknown" disks as well"). So I looked around and found a patch for format on x86 with a revision just a bit newer than what I had (137022-01 came with the install, I tried 137022-02's format command), to no avail (same response).
I then tried fmthard to try and read the label, which responded with "disk must be labeled first"
so I thought, ok, I will just use one of the working labels as a start (4 of my 5 disks are identical, so I figured I could fix the 3 bad ones using an existing disk label)
so I used fmthard again to write a disklabel that I had copied from the one good disk:
{code}
# fmthard -i -n "" /dev/rdsk/c1d1s2 > /tmp/partmap
# fmthard -s /tmp/partmap -n "" /dev/rdsk/c0d0s2
fmthard: Partition 8 overlaps partition 2. Overlap is allowed
only on partition on the full disk partition).
fmthard: Partition 9 overlaps partition 2. Overlap is allowed
only on partition on the full disk partition).
expected one reserved partition, but found 0
{code}
which I guess is another way to spell failure, as I still can't read a disklabel from the drive.
prtvtoc also reports "invalid VTOC" on the drives in question.
I have also tried booting a linux live environment, and partitioning these drives with one big solaris (code 'bf') partition on each. this had no effect on the issue.
I would like to point out that this very system was running solaris 10 x86 5/08 with the exact same harddrives 1 week ago. I had to re-install after some momentary laps of reason made me try out linux on the machine. this shouldn't have done much, as these drives have at one point been used in solaris, freebsd, and linux during their lives, and they haven't had much to do anyway, so I am confident in their current condition.
My big question is: why have multiple versions of format failed me? and is there any other way to give a disk a brand new disk label? there is nothing on the drives, so I don't care what happens to the data.
thank you all in advance

thank you both for your responses.
you aren't going to believe this, but format now behaves! it seems as though after creating a zfs pool using the disks that crashed format, the disks now show up just fine under format, in fact format says:
Searching for disks...done
AVAILABLE DISK SELECTIONS:
       0. c0d0 <SAMSUNG-S09QJ1OA10134-0001-232.89GB>
          /pci@0,0/pci-ide@11/ide@0/cmdk@0,0
       1. c0d1 <WDC WD25- WD-WCANKE28342-0001-232.89GB>
          /pci@0,0/pci-ide@11/ide@0/cmdk@1,0
       2. c1d0 <WDC WD25- WD-WCANKE22707-0001-232.89GB>
          /pci@0,0/pci-ide@11/ide@1/cmdk@0,0
       3. c1d1 <SAMSUNG-S09QJ1LL50379-0001-232.89GB>
          /pci@0,0/pci-ide@11/ide@1/cmdk@1,0
       4. c3d0 <DEFAULT cyl 38910 alt 2 hd 255 sec 63>
          /pci@0,0/pci-ide@14,1/ide@1/cmdk@0,0
Specify disk (enter its number): 0
selecting c0d0
NO Alt slice
No defect list found
[disk formatted, no defect list found]
/dev/dsk/c0d0s0 is part of active ZFS pool pool. Please see zpool(1M).I am running 64-bit on an amd phenom 9550 based machine.
I am going to read through the zfs documents (ALL of them, not just the quick-starts) and see what it says about disk labels.
here is pstack's output on the core file of `format'
# pstack ./core
core './core' of 1013: format
----------------- lwp# 1 / thread# 1 --------------------
080626e1 c_disk   (8047560, 8047454, feffb818, 4, 806740e, 0) + 369
08060777 main     (1, 8047498, 80474a0) + 2e3
080547c6 ???????? (1, 80475c8, 0, 80475cf, 8047603, 8047618)
----------------- lwp# 2 / thread# 2 --------------------
feeb5053 _door_return (0, 0, 0, 0) + 23
fec30d3d door_create_func (0) + 29
feeb3a81 _thr_setup (feab0200) + 4e
feeb3d70 _lwp_start (feab0200, 0, 0, febbeff8, feeb3d70, feab0200)
----------------- lwp# 3 / thread# 3 --------------------
feeb3dcb __lwp_park (80c5c08, 80c5c18, 0) + b
feeae60e cond_wait_queue (80c5c08, 80c5c18, 0, 0) + 3b
feeaeb07 _cond_wait (80c5c08, 80c5c18) + 66
feeaeb49 cond_wait (80c5c08, 80c5c18) + 21
fed82bc8 subscriber_event_handler (8091e00) + 3f
feeb3a81 _thr_setup (feab0a00) + 4e
feeb3d70 _lwp_start (feab0a00, 0, 0, feaaeff8, feeb3d70, feab0a00)

Bad Magic Number in Disk Label & DiskSuite

Envrionment:
E450
Solaris 8
DiskSuite 4.2.1
16 disks
Because of a power failure, after reboot one of the disks has bad magic number in its disk label. The slice was in a mirror. DiskSuite has hot spares and one of them took over the failed slice. I am trying to figure out how to get it back to where it was.
I think I should use 'format' to recover the disk label from the backup label. However, once the label is recovered, how do I make it stop using the hotspare and have the failed slice join back to the mirror?
Sorry if this is basic question, I am relatively new to Sun/Solaris and I just took over the E450.
Thanks,

Envrionment:
E450
Solaris 8
DiskSuite 4.2.1
16 disks
Because of a power failure, after reboot one of the
disks has bad magic number in its disk label. The
slice was in a mirror. DiskSuite has hot spares and
one of them took over the failed slice. I am trying to
figure out how to get it back to where it was.
I think I should use 'format' to recover the disk
label from the backup label. However, once the label
is recovered, how do I make it stop using the hotspare
and have the failed slice join back to the mirror?
Sorry if this is basic question, I am relatively new
to Sun/Solaris and I just took over the E450.
Thanks,Since the host spare took over then you're free to repair/replace the bad drive. In this case you could check the drive using format and partition to view the partitions. If the label is bad then I would suspect the drive is still good and a simple format>label and save command would repair the label. Then once this is done if all goes well then the system should rebuild the drive and the hot spare will not longer be used. The system should regonize the drive as a replacement and rebuild it then stop using the hot spare.
Michael

Bad number in disk label?

I am attempting to install Sol.8 on a sparc 10. when I attempt to boot from the cdrom I receive this error:" Bad magic number in disk label
Can't open disk label package"
I can identify the cdrom with the probe-scsi command. I relize that this is being caused because the disk has not yet been formated. Any thoughts on how to format this new disk without accessing the cdrom?Any thoughts would be appreciated!

Looks like your cdrom dive or cd media is defective. Probe scsi will detect the cdrom hardware but can't verify its reading ability .Media can be checked by using it on another system and trying to boot with cd . For cdrom try using another drive or try cd lens cleaning.
Hemant
http://www.adminschoice.com

Bad magic no in disk label

dear all,
i am facing a problem with the above said matter.i have sun fire v480 m/c with solaris 9 loaded.now the problem i am facing is,while booting the system it shows BAD MAGIC NO IN DISK LABEL.CANT OPEN BOOT DISK.
i have tried with following.
booting the system in single user mode with the boot cd and run FSCK.
but it didnt work.
can anybody can help me out.

Standard question posted many times on this forum.
Boot to the prompt.
Type `format`
When presented with menu, choose `label disk`
Follow simple instructions and choose `save` ....
Reboot your machine and the drive should be recognized.
Good luck, John.

T6340 cannot boot disk - Bad magic number in disk label

Hi,
I have a shiny new T6340 that I am just setting up.
When I get through the CMM to the SP and onto the EEPROM,
I then try to start the boot process:
{0} ok boot disk1
Sun Blade T6340 Server Module, No Keyboard
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.30.4, 130848 MB memory available, Serial #76313344.
Ethernet address 0:14:4f:8c:73:0, Host ID: 848c7300.
Boot device: /pci@500/pci@0/pci@9/@0/disk@1 File and args:
Bad magic number in disk label
Can't open disk label package
ERROR: boot-read fail
Evaluating:
Can't open boot device
{0} ok show-disks
a) /pci@500/pci@0/pci@9/LSILogic,sas@0/disk
b) /pci@500/pci@0/pci@2/pci@0/usb@0,2/storage@5/disk
c) /pci@500/pci@0/pci@2/pci@0/usb@0,2/storage@1/disk
q) NO SELECTION
Enter Selection, q to quit: q
{0} ok boot /pci@500/pci@0/pci@9/LSILogic,sas@0/disk
Boot device: /pci@500/pci@0/pci@9/LSILogic,sas@0/disk File and args:
Bad magic number in disk label
Can't open disk label package
ERROR: boot-read fail
Can't open boot device
{0} ok This is a brand new B6000 system and has not been booted before.
Please tell me what I need to do to enable the disks, so I can do the next bit!
rachel

@rachel,
In your original post you showed a screen capture of what you tried.
First you typed "boot disk1". ( Why disk1? Why not disk0?)
When that didn't seem to work, you displayed the disks recognized by the system at OpenBoot.
The first of those disks was a device path of
/pci@500/pci@0/pci@9/LSILogic,sas@0/disk{code}
and so you attempted to boot from that but omitted whatever slice might be the boot slice of a factory preinstalled OS. For example...
{code:java}
boot /pci@500/pci@0/pci@9/LSILogic,sas@0/disk@0,0{code}
(just guessing at what could be that bootable slice).
What happens if you simply type "*boot*" when you are at OBP?

Disk Label requirement

Hi,
Any one explain, why disk labeling required . If there is no disk label it will create problem, please clarify.
Regards,
Siva

I'm not in the expert class, I'm simply another Solaris administrator but I can give you a simple answer. The disk label is required because it provides some very basic low level information needed by the system for disk access. If the disk is divided into partitions, the disk label would give an indication as to the location and size of each partition. If you wanted to mount a filesystem stored in the fifth partition on the disk, the system can use the data recorded in the disk label to find that partition. Of course, things have a way of getting complicated. There are different sorts of disk labels so you can have situations where you have the wrong kind label on a disk for a particular purpose. That's where understanding the requirements can get tricky.

Installer 2011DS1: hand crafted disk labels for compatibility checks?

I have a problem with the installer of Labview 2011 DS1in combination with Vision. I want to create an installer for an application that uses vision and therefore selected the additional installers "NI Vision Common Resources 2010 SP1" and "NI Vision Run-Time Engine 2010 SP1". The assistant then asks for the disk "NI Developer Suite 2011 DS1 - DVD 2". When I insert that disk the assistant complains
"The disk you have provided is a different version of the requested disk.
Disk Requested: NI Developer Suite 2011 DS1 - DVD 2
Disk Provided: NI Developer Suite 2011 DS1 DVD 2
It seems, a litte missing hyphen in the disk name prevents me from deploying my application. You could argue to simply choose another DVD containing the run time engine. This leads to an overwhelming list of disk alternatives one has to manually click through in order to find another variant of the installer. The assistant knows what installer is missing and obviously knows whether the selected disks contain this installer but it is unable to filter the list to show applicable alternatives only.
After a lot of clicks, I found another disk containing the vision runtime. It is "NI Vision Developer Module 2010 SP 1" and when I insert a DVD that is labelled exacly the same, the assistant complains:
"The disk you have provided is a valid installer, but it does not match the disk requested.
Disk Requested: NI Vision Developer Module 2010 SP 1
Disk Provided: VDM2010SP1DVD
There is an alternative Disk that seems to have the same label as my DVD and so I selected "VDM2010SP1DVD", click "Yes" and of course get the error message I have attached. After that message, nothing else happens. At least no installer for my application is created.
Is there any way to create an installer with Labview 2011 SP1? Could you please refrain from using obviously hand crafted disk labels for compatibility checks?
With best regards
C. Manteuffel
Attachments:
installer_error.gif ‏7 KB

I had something similar happen recently, see:
http://forums.ni.com/t5/LabVIEW/LV2010-SP1-Installer-Build-Issue-Cannot-find-the-file-it-need-on/m-p...
I copied the VDM DVD to my hard drive and it came up on the list of alternative choices. Selected that folder and it finally completed the installer.
-AK2DM
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

Can' t read disk label, install issues

can' t read disk label, install issues
i am trying to install solaris 8 on a sparc5 (256mb, 4.2gb,110mhz). i initially installed using the installation disk and it seemed successful as i was able to load the rest of the cds. something went wrong though b/c the system is stuck in a rebooting loop after it finished the last cd. so i went searching and found that i could only have a root partition of no bigger than 1gb. since i used the installation disk, i was not given an option to specify slice sizes. so now, i am trying to redo the install starting from the first disk (1 of 2) and skipping the installation disk. when i do a "boot cdrom" with the 1 of 2 disk, i get the cant read disk label or something about short entry and it will not boot. i am using actual Solaris 8 cds and not downloads. what can i do to get it to boot up from the first disk, or fix the partitioning on the disk?

I am using the offical Solaris 8 Installation 2/02 for SPARC Platform Edition for Sun Computer Systems February 2002, Revision A
Output from the probe-ide command follows:
device 0 (Primary Master)
ATA Model: ST3160023A
device 1 (Primary Slave)
Removable ATAPI Model: LTN4865
device 2 (Secondary Master)
ATA Model: ST340016A
device 3 (Secondary Slave)
not present
device 0 is the new hard disk that I just installed
device 1 is the CDR drive
device 2 is the original hard disk. I can boot this but now get some magic disk errors or something like that
device 3 is not present
I have all devices set to cable select according to the manual.
Thanks for your help...
Tom

Can't read disk label: Booting Blade from CDROM

Folks !
I am trying to boot Sun Blade 100 from its internal IDE CD-ROM drive
using the Solaris 8 boot/installation CD (01/01). When I give the command
"boot cdrom" from ok fromt in OpenBoot, disk seems to spin for a moment
(green light comes on) but it eventually fails complaining:
can't read disk label
can'open disk label package
failed to open boot device.
I have tried following (all to no avail)
"boot /pci@1f,0/ide@d/cdrom@1,0:f" since devalias shows that cdrom is aliased to above. I also tried cdrom@0,0:f, but same result.
tried boot/installation CD from Solaris 9
did set-defaults reset-all
checked probe-ide and show disks output to make sure CDROM is recognized - it is primary slave.
swapped another IDE CD-ROM drived pulled from a PC. It was recognized but still not bootable.
Makes me wonder if PROM/NVRAM is corrupted. Hard disk
drive is trashed as such (another Blade 100 problem, since it was crashing
often, I had to force powerdown using the switch eventually leading
to corruption of basic files like /usr/lib/libnsl.so.1, so I can't force fsck)
I have to boot from CD to recover the machine and hopefully
repair the disk drive or swap it out and upgrade to Solaris 9.
any help would be appreciated.
thanks very much.
-Sanjay Kumar

as per the message it appears either you have a bad CD drive or CD media . If you have another machine try to boot this CD and verify it is working there. If the CD is ok you will have to swap the cd drive for testing
Hemant
http://www.adminschoice.com
Folks !
I am trying to boot Sun Blade 100 from its internal
IDE CD-ROM drive
using the Solaris 8 boot/installation CD (01/01). When
I give the command
"boot cdrom" from ok fromt in OpenBoot, disk seems to
spin for a moment
(green light comes on) but it eventually fails
complaining:
can't read disk label
can'open disk label package
failed to open boot device.
I have tried following (all to no avail)
"boot /pci@1f,0/ide@d/cdrom@1,0:f" since devalias
shows that cdrom is aliased to above. I also tried
cdrom@0,0:f, but same result.
tried boot/installation CD from Solaris 9
did set-defaults reset-all
checked probe-ide and show disks output to make sure
CDROM is recognized - it is primary slave.
swapped another IDE CD-ROM drived pulled from a PC. It
was recognized but still not bootable.
Makes me wonder if PROM/NVRAM is corrupted. Hard disk
drive is trashed as such (another Blade 100 problem,
since it was crashing
often, I had to force powerdown using the switch
eventually leading
to corruption of basic files like
/usr/lib/libnsl.so.1, so I can't force fsck)
I have to boot from CD to recover the machine and
hopefully
repair the disk drive or swap it out and upgrade to
Solaris 9.
any help would be appreciated.
thanks very much.
-Sanjay Kumar

Can't open disk label

Hello world !!:
I'm installing a Tape in my Sparc 5. The system works whit Solaris 2.4.
When I boot the system without the tape it starts normally. But, the problem is when I put the tape... and I have this message:
Can't read disk label
Can't open disk label package
Can't open boot device
In the prompt I did:
ok probe-scsi-all
Target 3 Disk SEAGATE
Target 4 Removable only Tape ARCHIVE // my TAPE
Target 6 Removable Read only device TOSHIBA XM- // my CDROM
ok boot -r
Can't read disk label
Can't open disk label package
Can't open boot device
I check with the commnad 'devalias' and all the paths are ok. I probe when 2 different tapes and I format the disk using the command format booting the system without the tape . But I've the same error when the tape is connected.
Someone can help me? Thanks a million
[email protected]
HPP

Hello worl !:
I'm installing a Tape in my Sparc 5. The system works whit Solaris 2.4.
When I boot the system without the tape it starts normally. But, the problem is when I put the tape... and I have this message:
Can't read disk label
Can't open disk label package
Can't open boot device
In the prompt I did:
ok probe-scsi-all
Target 3 Disk SEAGATE
Target 4 Removable only Tape ARCHIVE // my TAPE
Target 6 Removable Read only device TOSHIBA XM- // my CDROM
ok boot -r
Can't read disk label
Can't open disk label package
Can't open boot device
I check with the commnad 'devalias' and all the paths are ok. I probe when 2 different tapes and I format the disk using the command format booting the system without the tape . But I've the same error when the tape is connected.
Someone can help me?
[email protected]
HPP.

DIsk labels on ST2510

Similar Messages

Maybe you are looking for