Ultra 60 "Seeing" Incorrect Disk Size

System: Ultra 60 - (2x 360MHz, 256 RAM)
The system has (2) 18GB drives, a Seagate Barracuda and a Toshiba (which turns out in fact to be a rebranded Barracuda). After launching the Solaris 10 installer, I noticed it only sees 2 9GB drives. I am completely new to SPARC architecture. My initial though was to upgrade the BIOS (PROM I guess) and that the drives are probably supportable since both are in the factory options list in the System Handbook section of the site. After successfully applying the patch for OBP and POST, I launched the Sol10 installer again and got the same result. The drives are hooked to the onboard controller and integrated backplane via SCA. They are most definately 18GB drives, both. Also on the internal SCSI is the factory CD drive. When I acquired the system, I thought I performed some steps to clear the NVRAM; would there have been some way for the previous owner to have capped the drive recognition or set up some kind of odd RAID with the internal controller, or perhaps something I still need to do to force recognition? Also, the system has another SCSI controller, some strange thing with an Ethernet connecter combined on it. Nothing is currently hooked to it, I'm using onboard everything. I wanted to get some advice before I run out and acquire an internal SCSI cable to try it on the add-in controller. Thanks!

So, after some extensive playing and advice-exploring, I still have the same results. The problem is simplistic: the LBA-geometry drive is full size, and the other is seen in CHS, and thus seen incorrectly. I believe the way to correct this is to fill in the "type" routine in format with a CHS value that yields a large disk, OR use some other utility from within an OS to rewrite the disk label to LBA or perform the CHS geometry modification. Does anyone know of any way to make a disk seen by "format" as CHS switch over to LBA? (normally performed in the BIOS of a PC) or a generic CHS value used for large CHS drives? (like 65536/255/<drive-specific sector number>) I tried the auto and SUN18G types (matches the part numbers of the drives in the System Handbook, these are genuine Sun parts as well and have SUN18G in their firmware model #), and doing this on an LBA drive leaves me with an LBA drive, and it doesn't change on CHS either. Within the course of a night I can have either Solaris 10 or Debian on the "good" disk so I can have any utility necessary, and still would really like to resolve this. I can also bring these into work and slap em into a Proliant, and use the SCSI on that to low-level these disks as well, if that will help and will solve the issue.
Also of interest, do these drives have some geometry they report to the OS built into the drive's firmware? Might that be where the LBA/CHS info is coming from, or is it just a soft disklabel that someone wrote with whatever antiquated version of Solaris was previously on this? Thanks again for your continued help. ST-318203LC is the problematic drive.

Similar Messages

"raidctl -l c0t0d0" in T1000 shows incorrect disk size

We are using hardware raid1, set up with raidctl command on our T1000. When I issue "raidctl -l c0t0d0" in our T1000 it shows incorrect disk size of 689.9M, instead of 136G. This seems to have started with 12/1/09 Recommended Patch Cluster for Solaris 10. Is anyone else seeing this and/or know of a fix?

Hello
We've been told to install patch 144017-01 although we've yet to perform this to see if it fixes the problem.
After installing mpt patch 141743-02 or later drive capacity is incorrectly reported
SunOS 5.10: mpt.so.1 patch
Status: RELEASED
Patch Id: 144017-01
READ THE TERMS OF THE AGREEMENT ("AGREEMENT") IN THE LEGAL_LICENSE.TXT
FILE CAREFULLY BEFORE USING THIS SOFTWARE. BY USING THE SOFTWARE, YOU
AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE
TERMS, PROMPTLY DESTROY THE UNUSED SOFTWARE.
For further information on patching best practices and resources, please
see the Big Admin Patching Center, http://www.sun.com/bigadmin/patches/
Summary: SunOS 5.10: mpt.so.1 patch
Date: Mar/17/2010
Installation Requirements:
NA
Solaris Release: 10
Sun OS Release: 5.10
Unbundled Product:
Unbundled Release:
Xref: This patch available for x86 as patch 144018
Topic:
SunOS 5.10: mpt.so.1 patch
Relevant Architecture: sparc
BugId's fixed with this patch:
6881276
Changes incorporated in this version:
Patches accumulated and obsoleted by this patch:
Patches which conflict with this patch:
Required Patches:
127127-11 137137-09 139555-08 141444-09 (or greater)
Obsoleted by:
Files Included in this Patch:
/usr/lib/raidcfg/mpt.so.1
/usr/lib/raidcfg/sparcv9/mpt.so.1
Problem Description:
6881276 after installing mpt patch 141743-02 or later drive capacity is incorrectly reported
Revision History:
Patch Installation Instructions:
Please refer to the man pages for instructions on using 'patchadd'
and 'patchrm' commands provided with Solaris.
The following example installs a patch to a standalone machine:
example# patchadd /var/spool/patch/123456-07
The following example removes a patch from a standalone system:
example# patchrm 123456-07
For additional examples please see the appropriate man pages. Any
other special or non-generic installation instructions should be
described below as special instructions.
Special Install Instructions:
None.
README -- Last modified date: Wednesday, March 17, 2010

MacBook in target disk mode shows incorrect disk size

My 80 GB hard drive in MacBook has gone bad (the filesystem is in inconsistent state). I connected it to an iMac in Target Disk Mode. It shows up (unmounted) but the capacity reported by Disk Utility is 20 GB. Does someone know why is that? Is it due to the corrupt filesystem?
I am afraid that given this situation, if I buy and run DiskWarrior, that too might not be able to see the full disk and fail to repair it. Note that if I boot my MacBook using the Apple CD, the Disk Utility shows the correct disk size.
Thanks.

If you have a disk that is in really, really bad shape to the point that Disk Utility looks at you like a 5 year old that just spilled a glass of apple juice on the kitchen floor, it's time to bring in the big guns.
DiskWarrior.
I love it, I love it. If someone has something bad to say about it, they are lying. If there is a chance that you can get everything back to normal without spending the huge dough to send your drive out to be dismantled in a clean room, DiskWarrior is that chance.
It's worth every single penny.
Let me know if you have other queries.

WMV and Disk Size issues

So I am a pretty avid Encore user and I have come into some issues lately and could use some help.
Background-
I filmed a 14 hour conference on SD 16:9 mini dv
I captured 14 hours with Premiere as .AVI - I edited the segments and exported as .AVI
I used Media Encoder to convert the files to NTSC Progressive Widescreen High Quality (.m2v) - Reduced the file size drastically
I then used Media Encoder to convert the .m2v files to .wmv files - Reducing the conference size to 5.65 GB in total.
I then imported the .wmv into Encore - my issues begin
At first, Encore CS4 imported the .wmv files without a problem however the disk size (of 5.65 GB) registered in Encore as around 13 gigs??? Why is that? The .wmv files only consume 5.65 gb on my harddrive. Where is this file size issues coming from?
So then Encore CS4 gets upset that I have exceeded the 8.5 DL Disk size and crashes...
I reopen the program and try to import my .wmv files again (forgot to save like an idiot). 3 of 8 .wmv files import and then Encore starts giving me decoder errors saying I cannot import the rest of the .wmv files...
Can anyone help me with this issue? Im quite confused by all of this. Things seemed to work fine (sorta) at first and now Encore is pissed.
I want to get this 14 hour conference on 1 DL DVD and I thought it would be as simple as getting the files reduced to a size sutable for a 8.5 gb disk. Why is my way of thinking incorrect?
Thanks for any help,
Sam

ssavery wrote:
Thanks everyone for your help.
Im still not giving up.... It's become an obsession at this point. My uncle does this with kids movies for his children. He'll download and compress entire seasons of children shows and put them all on one dvd which he then plays in a dvd player for them to watch. Im currently trying to get ahold of him....
Thanks for the help
Sam
i've done this as well for shows that are never to be seen again for the light of day from the 80s and such... i use VSO Software's "ConvertXtoDVD v4" i ONLY use this for archival purposes of xvid or wmv or stuff that encore would throw fits over. the menus are all mainly default stock stuff. but for these projects i'm not concerned about menus or specific navigation, i just need to get the job done. i can squeeze around 15 hrs of 720x480 on one DL (it compresses the ever living dayligths out of the video... but for most of the source footage... it really doesnt matter at that point, its mostly all VHS archives i use for this program anyway) if you just absolutely HAVE to have a 1 disker, you could check that app out, burn it an see how it looks.
edited to add: that to really squeeze crap in, you can also use a DVDFab program (any ersion should do... Older ones are cheaper) make a disc image with ConvertX, if yiu have alot f footage it may push it beyond the normal boundary of a dvd-dl and fail the burn. So then you can just import the disc image into DVDFab, and choose it to burn to a DVD-DL, and it may compress it by about 3-7% more to fit it. I would NEVER use this method EVER for a client... But if you are just hell-bent on doing 1 disk. Tries these 2 apps out. It may work out if you can live with the compression.
if you do try this, I recommend trying this workflow. Open premiere with your first gem captured AVI. set up your chapters how you want them or whatever, then save each chapter or lecture or segment or whatever as it's own AVI. the. Import all those separately into ConvertX and set it up to play one after the other when each segment ends. [i can't confirm this 100%, because i usually drop in already compressed files... but if for some reason it don't wanna work out... then i would suggest dropping in the mts files instead] (if say you want a new "movie" for each lecture instead, and have chapters per movie that can be done too... But it's more work, but I can expound later if need be) To save time on encoding, set up the menu to be the "minimalist" menu. It's strictly text. Then just create sn ISO. if you donthe full thing, I can almost guarantee you'll have to use DVDFab to burn to disc, because it'll probably be about 5-8% overburn.

Is there a max SATA disk size in OSX 10.4.11 and G4/1.25?

Hello,
I am trying to set up a G4/1.25 (2 gig in memory) as a fileserver with a SATA card and 2 x 3 TB seagate disks. This is the setup:
http://lowendmac.com/ppc/mdd-power-mac-g4-1.25-ghz.html
http://firmtek.com/seritek/seritek-1v4/
http://eshop.macsales.com/item/Seagate/ST3000DM001/
The system is OSX 10.4.11. I am unable to initialize the disks in disk utility. The process starts but then halts and says that it can not continue.
My question is if there is a max disk size in OSX 10.4.11?
Any help greatly appriceated.
Best regards,
Ingolfur Bruun

Hello again,
I tried to work my way around armed with your input and succeeded
By using a FireWire dock I was able to see the disks in 10.4.11. What I did was to partition the disks with ONE partition in Disk Utility and then format with GUID partitioning scheme instead of the Apple Partition Mapping scheme which I had done before. And as I am using a ATA disk as a startup disk it dosen't matter if the 3 TB disks are not bootable. They will only be used for data, not as system disks.
You saved my day! Thanks again.
Best regards,
Ingolfur

Maximum disk size?

That's the maximum disk size or volume size supported? Thanks for any insights.

The maximum volume size, and file size, in Mac OS X 10.4 or later, is close to 8 EB (exabyte, or 10**18 bytes). The actual number is 2**63 - 2**31.
See Mac OS X: Mac OS Extended format (HFS Plus) volume and file limits

Time Machine backup disk size - total capacity of disk or just files used?

Hi folks,
After upgrading to Leopard, I'm trying to set up my Time Machine. My main HD is 175 Gig and all the OS and other files take up 37 Gig of that. The drive I want to use for Time Machine (a spare internal hard drive) is a 75 Gig drive with 74 Gig of space available. Time machine says this drive is too small to use.
According to the Time Machine documentation, Time Machine takes the _total size of the files_ to be backed up and multiplies that by 1.2. So in my case, since the total files on my 175 Gig drive take up 37 Gig, then I would need only 42 Gig for my Time Machine back up. So, in theory, my 75 Gig spare drive should work just fine.
The problem is that Time Machine is taking the total size of the entire HD and using that to calculate the size of the back up drive, which would be 210 Gig. Does anyone know why this problem is occurring? It seems like Time Machine is not calculating the needed back up disk size properly and is incorrectly including the unused disk space on my main HD.

Not sure exactly, but your drive really is too small. Yes, 37 gb plus workspace would do for your initial Full Backup, but subsequent incrementals could fill it up pretty fast. That would depend, of course, on how you use your Mac -- how often you add or update files of what sizes.
If you change your habits and, say, download a multi-gb video, then work on editing it for a few hours, you could eat up the remaining space very, very quickly.
Just to be sure, how are you determining space used? Via right-click (or control-click) and Get Info on your HD icon?
Also, do you have any other HDs connected? If so, exclude it/them, as TM will include them by default.
Three possible workarounds:
First, get a bigger drive. HDs have gotten ridiculously cheap -- 500 gb (or even some 1 tb) for not much over $100.
Second, use CarbonCopyCloner, SuperDuper, or a similar product instead of TM. CCC is donationware, SuperDuper about $30, I think. Either can make a full bootable "clone", and CCC has an option to either archive previous versions of changed files or delete them. CCC can be set to run automatically hourly, daily, etc. (I suspect SD can, too, but I don't know it's details). An advantage is, of course, if your HD fails you can boot and run from the "clone" until you get it replaced, then reverse the process and clone the external to the internal.
Note that these will take considerably longer, as unlike TM, they don't use the OSX internals to figure out what's been added or changed, but must look at every file and folder. In my case, even smaller than yours, TM's hourly backup rarely runs over 30 seconds; CCC's at least 15 minutes (so I have it run automatically at 3 am). And, if you don't keep previous versions, of course, you lose the ability to recover something that you deleted or changed in error, or got corrupted before the last backup.
Third (and NOT recommended), continue with TM but limit it to your home folder. This means if you lose your HD, you can't restore your whole system from the last TM backup. You'd have to reload from your Leopard disk, the apply all OS updates, and reload any 3rd party settings, then restore from TM. As a friend of mine used to say, "un-good"!

About OCR and Vote Disk size

Hallo,
I have a simple question about OCR and Vote Disk in a 10g/11g RAC setup:
official documentation speaks about sizing OCR and Vote Disk about 280 MB, but do they mean each OCR and Vote disk LUN ?
In other words, for 2 OCR and 3 Vote disk I need 280*5 MB ( in multiple o single LUN)
Is it so?
thx in advance

ottocolori wrote:
Hallo,
I have a simple question about OCR and Vote Disk in a 10g/11g RAC setup:
official documentation speaks about sizing OCR and Vote Disk about 280 MB, but do they mean each OCR and Vote disk LUN ?
In other words, for 2 OCR and 3 Vote disk I need 280*5 MB ( in multiple o single LUN)
Is it so?
thx in advanceYes. Also see Re: Reduce size of OCR file

Silly question regarding sol 8 containers and disk sizes

I've got what is probably just about the silliest question, but I can't seem to find an answer whilst searching around for the past couple of hours. Say I have 2 boxen, one is a sol 8 server and the other is a brand new install of sol 10/8. They have the exact same hardware, including disk size. If I want to turn the first box into a solaris 8 container running under the second, how do I reconcile the fact that the disk sizes are the same? The sol 8 box is only using, say, 25-30GB of the 72GB on the disk. Do I have to resize the slice into something smaller to enable it fit into a container on the second server? It would seem that is the case, but I didn't know if there was some magic I was not aware of. I've not done a ufsdump or flash archive before so I don't know if the 'empty' space on the disc will be disregarded, possibly allowing me to squeeze it onto my sol 10 server and allow me to resize it smaller in zfs. This topic isn't touched in all the tutorials I've read, so I assume it's either a completely retarded/braindead concern, or everyone always migrates these boxen onto servers with much more in the way of resources.
Sorry if I offended anyone with my ignorance ; P

No. Solaris8/9 containers make use the "branded zones" technology. But it's still the same thing and there's no "disk image", at least not like you might think of for VMware or Xen.
Now if you want to call a ufsdump or flash archive an "image", then that's fine. But you can see in either case, the free space or minor changes is size are irrelevant. You're just copying files. It's a system image, not a "disk image".
                  Installer Options :
                        Option          Description
                        -a filepath     Location of archive from which to copy system image.
                                        Full flash archive and cpio, gzip compressed cpio,
                                        bzip compressed cpio, and level 0 ufsdump are
                                        supported. Refer to the gzip man page available in the
                                        SUNWsfman package.--
Darren

Disk size requirement

Hello,
I'm planning the installation of an SDS. I don't find any reference to the disk size requirements in the documentation. Is the any recommendation ?
We will be managing Solaris Sparc 8,9, 10 as well as Soalris X64 and Linux RHES 3 and 4. Around 100 servers for the whole farm.
Could someone point me to some recommendation ?
Best regards

For installing an SDS, here is the recommendation:
Disk Space Requirements:
Installation: 512 MB minimum free in the file system that serves /usr/local
Software Components: 500 MB minimum
SWAP: 500 MB minimum
For more information, see:
http://docs.sun.com/app/docs/coll/1561.1

Max. disk size in A1000?

Hi,
Does anybody know what the max. disk size is that works in a A1000 array? We have so far used 76GB disks in an 8 slot A1000.
Thanks

Hello Erwin,
SCSI is less limited than IDE. The next bigger size should work.
The Seagate ST3146707LC (146.8GB - 10000 RPM Ultra-320) and Fujitsu MAT3147NC (146.8GB - 10000 RPM Ultra-320) are listed as compatible.
http://sunsolve.sun.com/handbook_pub/Systems/A1000/component s.html#Disks
Michael

Does Labview RT 8.5 impose a limit on FAT32 partition / hard disk size?

We will be using a PXI RT system (spec below) to collect, analyse and store a
large amount of data (~30 to 40GB per experiment).
We don't want to keep the Windows host PXI attached
and so the RT PXI must be able to store all the data from an
experiment.
It would be desirable to keep data from all
experiments on the H/D, so a capacity of ~300GB would be useful.
Q: Is there a limit on the hard disk size imposed by the Labview RT 8.5 Operating System and if so what is
it?
An older
post (~2005) suggests that the partitioning tool limited FAT32 partitions to 32GB.
Thus the question I'm asking that if I created a large FAT32 partition with
a third party tool could I install and run Labview RT
8.5?
Q: Is there any other way of connecting a
large capacity H/D to the RT System? For example using H/D partitions, slave H/D. Other
ideas?
Thanks,
Michael
NI-1000B with
NI-8176 embedded controller
PIII
1.266MHz
128MB RAM
Labview RT
8.5
Solved!
Go to Solution.

> The size limitation has nothing to do with
the LabVIEW RT OS. FAT32 limits you to 32GB. This cannot be changed since it's a
limitation of the file system format.
Thanks for
reply.
I have, however, gained the impression from a
number of web sites that there isn't a 32GB partition limit on FAT32 -- see [**]
below -- but the limit is with the
partitioning tool. It looks like the
partitioning tool that comes with RT has a 32GB limit (Is that correct?). Hence
my question if you were able to create a large FAT32 partition could you install
and run RT?
Regards,
Michael
[**] The following was copied from http://en.wikipedia.org/wiki/File_Allocation_Table#FAT32
Windows 2000 and Windows XP can read and write to
FAT32 file systems of any size, but the format program included in Windows 2000
and higher can only create FAT32 file systems of 32 GiB or less. ... This
limitation can be bypassed by using third-party formatting
utilities.

Building a dvd with custom disk size (disk, ISO, or dvd folder)

My goal at the end of all this is to get a DVD format of video at 6mbps with menu's to be burned to a blu-ray 25GB disk.
Using Encore CS6 on a Windows 7 (4.7Gzh 8-core, 16gb ram @2400mhz)
1st attempt: I used a bluray disk and tried to burn a dvd format and it ejected my disk and said please insert a black dvd. (used custom disk of 25GB showing extra space available)
2nd attempt: I thought perhaps I would build it to an ISO (also tried dvd folder) to burn later. it responded with an error message saying, "disk capacity is too small - building navigation failed"
I dont care how I can get this to work but I would like to get all the video and menu's onto a single disk. Encore limits the "custom disk size" to 99GB so I assume it should work for 25GB (23.2GB).
The reason I dont want to make a bluray format is because it requires high bitrate and the video is so old it would be a waist of space. I dont need 720p of video from 1935. (unless I can make a bluray format at a 6mbps)
Thank you for any help you can provide
bullfrogberry

You can do this in Encore.
I am assuming you are only picking presets, and not customizing one. You pick prests in the Transcode Settings dialog. Do you see the "Edit Quality Presets" button? Pick it, customize one by setting the bitrates to get the results you want, then SAVE IT as your own. Then pick that in the transcode setting. (In the transcode setting image, you can see my custom example "Stan Custom 4Mb CBR".) And yes, you can select all your video assets and apply this custom preset to all of them at once. I would do one short one to see if you are getting in the ball park. I would do 2 samples: one in MPEG2-Bluray and one in H.264-Blu-ray. (I'd follow Richard's recommendation to you and use H.264.)

Unable to see Member disk in ASM

Hi all
I am having standalone(NON-RAC) box with Linux AS3 (Kernel Ver. 2.4.21.4) and oracle 10G installed on it. It is having one database as ORCL. Now i wants to configure ASM on it. For that I did the following activities.
mkdir -p /u03
mkdir -p /u03/asmdisks
dd if=/dev/zero of=/u03/asmdisks/disk0 bs=1024k number=100
dd if=/dev/zero of=/u03/asmdisks/disk1 bs=1024k number=100
dd if=/dev/zero of=/u03/asmdisks/disk2 bs=1024k number=100
dd if=/dev/zero of=/u03/asmdisks/disk3 bs=1024k number=100
chown -R oracle:oinstall /u03
chmod -R 777 /u03
Then i chose to create the database through DBCA. Where i gave database Sid as ASM and selected AUTOMATIC STORAGE MANAGEMENT for the storage. In the parameter of asm instance i set the parameter asm_diskstring as */u03/asmdisks/*'
ASM Instance gets started with this as when i do "ps -aux | grep +asm" then it shows the ASM processes.
Now when i create the diskgroup as DGROUP1 with normal redundancy, I am not able to see member disks which i have defined in ASM instance parameter "asm_diskstring".
Is there any need to install ASM libraries on OS or any special service should be started on the OS?
Kindly Help as i am struckup in this past 5 days.
Regards
Bally

Two issues come to mind. Invallid discovery string - which means that ASM fails to see the raw disks. Or incorrectly configured raw disks.
My guess is the latter. Those "devices" that you configured as ASM devices do not sound valid. They have to be dinkum raw devices - they cannot be binary files on a cooked file system. Unless I'm mistaken? (I cannot recall seeing any cooked files as ASM devices option when I did a couple of ASM installs)
Okay, not close to my Linux boxes to check so the following is frrom memory. The last ASM install I did on Redhat was to create an actual raw device use an unformatted partition (e.g. /dev/sdb1) using the raw device Linux command. A file called /etc/sysconfig/rawdevices was created. At boot time the raw devices are mounted in /dev/raw something or another. These devices are then chmod'ed so that the oracle o/s user can access them.
The ASM discovery string is then set to /dev/raw whatever to pick up these raw devices.

Unable to see Member disk in ASM through DBCA

Hi
I am having standalone(NON-RAC) box with Linux AS3(Kernel Ver. 2.4.21.4) and oracle 10G installed on it. It is having one database as ORCL. Now i wants to configure ASM on it. For that I did the following activities.
mkdir -p /u03
mkdir -p /u03/asmdisks
dd if=/dev/zero of=/u03/asmdisks/disk0 bs=1024k number=100
dd if=/dev/zero of=/u03/asmdisks/disk1 bs=1024k number=100
dd if=/dev/zero of=/u03/asmdisks/disk2 bs=1024k number=100
dd if=/dev/zero of=/u03/asmdisks/disk3 bs=1024k number=100
chown -R oracle:oinstall /u03
chmod -R 777 /u03
Then i chose to create the database through DBCA. Where i gave database Sid as ASM and selected AUTOMATIC STORAGE MANAGEMENT for the storage. In the parameter of asm instance i set the parameter asm_diskstring as */u03/asmdisks/*'
ASM Instance gets started with this as when i do "ps -aux | grep +asm" then it shows the ASM processes.
Now when i create the diskgroup as DGROUP1 with normal redundancy, I am not able to see member disks which i have defined in ASM instance parameter "asm_diskstring".
Is there any need to install ASM libraries on OS or any special service should be started on the OS?
Kindly Help as i am struckup in this past 5 days.
Regards
Bally

Two issues come to mind. Invallid discovery string - which means that ASM fails to see the raw disks. Or incorrectly configured raw disks.
My guess is the latter. Those "devices" that you configured as ASM devices do not sound valid. They have to be dinkum raw devices - they cannot be binary files on a cooked file system. Unless I'm mistaken? (I cannot recall seeing any cooked files as ASM devices option when I did a couple of ASM installs)
Okay, not close to my Linux boxes to check so the following is frrom memory. The last ASM install I did on Redhat was to create an actual raw device use an unformatted partition (e.g. /dev/sdb1) using the raw device Linux command. A file called /etc/sysconfig/rawdevices was created. At boot time the raw devices are mounted in /dev/raw something or another. These devices are then chmod'ed so that the oracle o/s user can access them.
The ASM discovery string is then set to /dev/raw whatever to pick up these raw devices.

Ultra 60 "Seeing" Incorrect Disk Size

Similar Messages

Maybe you are looking for