8.02 Defects List?

Is there a list anywhere of currently known WebHelp 8.02 bugs?
I'm having numerous issues after upgrading from 7 to 8.02. One is a known issue - Related Topics control triggered by script does not work without manual patch.
Others I am experiencing:
Template clobbered when converted to master page (weird path alterations).
Related topics control simply not publishing at all.
CSS changes.
Flickering cursor (supposedly fixed by 8.02).
Project files list constantly refreshing (randomly?). It's like the project never opens and "settles in." The project is on my drive.
Sadly it is going to take some time to sort all of this out. This is the first upgrade in my long Robo history that has resulted in so much breakage.

http://www.grainge.org/pages/authoring/rh8/using_rh8.htm lists some but it is not exhaustive and does not cover what you are reporting!
Related Topics control - Maybe someone else can come in on this or you can search these forums. Follow your search by +robohelp to limit the results. There is a script on my site that converts Related Topics to a See Also list, if that helps.
Template  clobbered when converted to master page (weird path alterations) - I don't think that has been an issue.
Related  topics control simply not publishing at all. - see above
CSS  changes. - If you are talking about lists, there are many threads on that. See also the RoboHelp Tour on my site and look under Lists there.
Flickering cursor (supposedly fixed by  8.02). - Fixed by 801 not 802 and I haven't seen reports since then.
Project files list constantly refreshing  (randomly?). It's like the project never opens and "settles in." The  project is on my drive. That was something that was a warning that a project was about to go belly up before the 802 patch was released. See Opening Projects on my site. With a backup in place, try deleting the CPD file and reopening the project.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Similar Messages

  • Defect #368646: Defect manipulating Distribution Lists

    As stated in the Admin API Object Defect, there is a probleme using
    Distribution List with members beloging to another domain than the one
    you are connected to.
    This problem occurs ALWAYS for me and not only in certain cases.
    Does anyone knows if Novell is aware of this problem, and will take any
    action to support the method .users.Item ??
    I don t see any other solution to manipulate distribution list correctly?
    Thanks
    For Information : Admin object
    Defect #368646: In some circumstances, when the Admin API is used to
    get a user in a secondary domain and report the name of that domain, in
    the following way -
    Set usr = objAdminSystem.Users.Item("bbaggins", "books", "secdom")
    UserDomainName = usr.Domain.Name
    the Admin API will report the name of the primary domain instead. In
    addition, your Admin API application now thinks that any user in
    the secondary domain now belongs to the primary domain. Defect
    reported
    to GroupWise Development.

    Thanks for the answer but it s not possible as the GroupWise system is
    spanning over many eDir trees.
    I have used the UserIterator to access the User object I need, despite it
    is far longer than the Users.Item method, it works
    But as soon as I iterate in the User Collection, I found what is shown as
    duplicate users (may be unreadable object and the API is returning the
    previous user red) and after 3700 users .. my program hangs the
    gwcmb1.dll.
    Do you know if the API has some defects not reported in the defect list ?
    Does Novell support this API ? I had a look for SOAP but there is nothing
    to manage the GW objects, does Novell have a Admin SOAP ? or is planning
    to have one ?
    Thanks for the answer. We have around 5000 GW users, 5 eDir, 12 domains
    and around 20 POs .. and we are facing big issues to have a robust and
    open solution.
    We are still using the API Gateway (on a 5.1 NetWare server in a VWWare
    session as no hardware supports now NW 5.1) and our goal was to migrate
    our DLs management from API Gateway to Admin Object API.
    > One other way would be to have your DL's all linked to NDS Groups and
    do a
    > regular sync. But that might not be what you want
    > <[email protected]> wrote in message
    > news:[email protected]...
    > > As stated in the Admin API Object Defect, there is a probleme using
    > > Distribution List with members beloging to another domain than the one
    > > you are connected to.
    > >
    > > This problem occurs ALWAYS for me and not only in certain cases.
    > >
    > > Does anyone knows if Novell is aware of this problem, and will take
    any
    > > action to support the method .users.Item ??
    > >
    > > I don t see any other solution to manipulate distribution list
    correctly?
    > >
    > > Thanks
    > >
    > > For Information : Admin object
    > >
    > > Defect #368646: In some circumstances, when the Admin API is used to
    > > get a user in a secondary domain and report the name of that
    domain, in
    > > the following way -
    > >
    > > Set usr = objAdminSystem.Users.Item("bbaggins", "books", "secdom")
    > > UserDomainName = usr.Domain.Name
    > >
    > > the Admin API will report the name of the primary domain instead.
    In
    > > addition, your Admin API application now thinks that any user in
    > > the secondary domain now belongs to the primary domain. Defect
    > > reported
    > > to GroupWise Development.
    > >
    >
    >

  • How can I create my own tag name while creating a partition table.

    I have X4500 running Solaris 10. I have formatted a disk and created partition table as given below.
    Specify disk (enter its number): 0
    selecting c0t0d0
    [disk formatted]
    /dev/dsk/c0t0d0s0 is part of active ZFS pool zpool1. Please see zpool(1M).
    FORMAT MENU:
    disk - select a disk
    type - select (define) a disk type
    partition - select (define) a partition table
    current - describe the current disk
    format - format and analyze the disk
    fdisk - run the fdisk program
    repair - repair a defective sector
    label - write label to the disk
    analyze - surface analysis
    defect - defect list management
    backup - search for backup labels
    verify - read and display labels
    inquiry - show vendor, product and revision
    volname - set 8-character volume name
    !<cmd> - execute <cmd>, then return
    quit
    format> partition
    PARTITION MENU:
    0 - change `0' partition
    1 - change `1' partition
    2 - change `2' partition
    3 - change `3' partition
    4 - change `4' partition
    5 - change `5' partition
    6 - change `6' partition
    select - select a predefined table
    modify - modify a predefined partition table
    name - name the current table
    print - display the current table
    label - write partition map and label to the disk
    !<cmd> - execute <cmd>, then return
    quit
    partition> print
    Current partition table (original):
    Total disk sectors available: 1953508749 + 16384 (reserved sectors)
    Part Tag Flag First Sector Size Last Sector
    0 usr wm 34 4.00GB 8388641
    1 usr wm 8388642 2.00GB 12582945
    2 usr wm 12582946 200.00GB 432013345
    3 usr wm 432013346 175.00GB 799014945
    4 usr wm 1166180386 375.43GB 1953508748
    5 usr wm 799014946 175.00GB 1166016545
    6 usr wm 1166016546 80.00MB 1166180385
    8 reserved wm 1953508749 8.00MB 1953525132
    partition>
    I am unable to specify my own tag name. How can I change the tag name to one of my interest.
    I need to create 3 partitions as told below
    partitions:
    /earth
    /mars
    /work
    /earth and /work should be roughly equal in size, /mars should be twice the size of the others, if that is possible. If not 3 partitions of equal size will do.
    Please, help me .
    Thank you.

    Exactly 1TB? Slightly under/slightly over?
    Traditional Solaris disk labels are in VTOC format, but this format cannot describe disks larger than 1TB. So EFI labels must be used on disks larger than 1TB. Setup is slightly different.
    Are these physical disks or LUNs from a SAN array? If they are array LUNS, it is often the case that they don't have a Sun label of any type. So...
    #1 Apply a Solaris label
    If the LUNS don't have a label (when selected in 'format', it gives a warning that no label is present and offers to apply a label immediately). When run non-interactively, format assumes "yes" for any questions. So all you'd have to do is select every disk to have it apply labels to any unlabled disk. Run 'format' once and find the highest number (maybe it's 50 for you). Create a text file that looks like this:
    disk 1
    disk 2
    disk 3
    disk 50Then feed that to format like this:
    # format -f /tmp/disklist or whatever you've named the file.
    #2 Apply the partition layout to all disks you want.
    You asked if you should do the same procedure, but I don't see that you've actually done anything above other than print out the existing layout. Take one of your 48 drives and partition it the way you want manually (set the slices to the sizes that you want). Then you can copy the layout of that disk to others. You only want to do this between disks/LUNs of the same size. As an example, if you've explicitly partitioned c1t0d0 and you want to apply this to c1t1d0, do this:
    # prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2Repeat for all of your other disks.
    Darren

  • Non root user can delete root files, bug?

    We're having an odd permissions based problem on Solaris 10 u5 x86_64, (new install, fully patched as of 2 days ago) It means that non root users can delete root owned files, which is something I've never seen before, and I've been doing this for almost 10 years.
    We're installing into an 80Gb container on VMware ESX server 3.0.1. The OS takes 20Gb (2 processors, 4Gb memory, 8Gb swap) most of the remaining 60Gb is being used as both file systems and raw devices under disksuite as soft partitions. It's one of the file systems, /apps (where we plan to install sybase) that is giving us "issues"
    Essentially:
    # more /etc/vfstab |grep apps
    /dev/md/dsk/d0 /dev/md/rdsk/d0 /apps ufs 2 yes -
    # newfs -v /dev/md/rdsk/d0
    /dev/md/rdsk/d0: Unable to find Media type. Proceeding with system determined parameters.
    newfs: /dev/md/rdsk/d0 last mounted as /apps
    newfs: construct a new file system /dev/md/rdsk/d0: (y/n)? y
    mkfs -F ufs /dev/md/rdsk/d0 20971520 -1 -1 8192 1024 264 1 546 8192 t 0 -1 8 7 n
    /dev/md/rdsk/d0: Unable to find Media type. Proceeding with system determined parameters.
    Warning: 4096 sector(s) in last cylinder unallocated
    /dev/md/rdsk/d0: 20971520 sectors in 3414 cylinders of 48 tracks, 128 sectors
    10240.0MB in 214 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
    super-block backups (for fsck -F ufs -o b=#) at:
    32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
    20055584, 20154016, 20252448, 20350880, 20449312, 20547744, 20646176,
    20744608, 20843040, 20941472
    # mount /apps
    # ls -al /apps
    total 20
    drwxr-xr-x 3 root root 512 Sep 10 12:31 .
    drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
    drwx------ 2 root root 8192 Sep 10 12:31 lost+found
    # su - sybase
    Sun Microsystems Inc. SunOS 5.10 Generic January 2005
    sol10% cd /apps
    sol10% rm *
    rm: lost+found is a directory
    sol10% rm -rf *
    rm: cannot read directory lost+found: Permission denied
    sol10% ls -al
    total 20
    drwxr-xr-x 3 root root 512 Sep 10 12:31 .
    drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
    drwx------ 2 root root 8192 Sep 10 12:31 lost+found
    sol10% exit
    sol10% logout
    # chgrp sybase /apps
    # chmod g+w /apps
    # ls -ald /apps
    drwxrwxr-x 3 root sybase 512 Sep 10 12:31 /apps
    # ls -al /apps
    total 20
    drwxrwxr-x 3 root sybase 512 Sep 10 12:31 .
    drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
    drwx------ 2 root root 8192 Sep 10 12:31 lost+found
    # su - sybase
    Sun Microsystems Inc. SunOS 5.10 Generic January 2005
    sol10% cd /apps
    sol10% rm -rf *
    sol10% ls -al
    total 4
    drwxrwxr-x 2 root sybase 512 Sep 10 12:34 .
    drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
    sol10% id
    uid=***(sybase) gid=***(sybase)
    sol10% exit
    sol10% logout
    # pwd
    # ls -ald /apps
    drwxrwxr-x 2 root sybase 512 Sep 10 12:34 /apps
    # ls -al /apps
    total 4
    drwxrwxr-x 2 root sybase 512 Sep 10 12:34 .
    drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
    It's a new "bare metal" (in as much as there is no metal) install. I created the sybase user from scratch by hand editing passwd, group and shadow, buy copying and pasting the data out of the NIS maps. All I've done besides the install & patch is setup networking manually, and created the metadb's and the soft partitions and the mount points & newfs'ed & mounted three of them . I then changed ownership of /apps to be sybase:sybase, and handed it to the database team for the sybase install. they came back and said "should we be able to do this?" as they habitually run rm rf * knowing they can't delete root owned files, only now they can... This is true even if I just chgrp the directory and give them group write permissions. They can still delete anything owned by root, even if it doesn't have group permissions just like the lost+found directory. No other "real" machine we have, x86 or SPARC does this, but we've never installed u5 before either.
    As you can imagine losing the lost+found directory is a bit of a problem, however what's really worrying me is if they can do that, what happens when they run sybase as the sybase user? If it borks can they trash the OS and write/overwrite random files?
    It's a VM, so in as much that's not a problem, but the reason it's a VM is somebody wants to send a VM to a client as a demo, and at present it's highly unstable IMO.
    Does anyone have any idea where to start? My thoughts are that it may be a VMware issue, (though the hardware and the guest OS is supported) it could be a bug, because I've never seen that weird newfs error before, and then I found this:
    http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6622243
    Or it could be me, and the fact that I'm hand configuring it, and u5 now requires I do it "properly" with useradd, etc. I'd like to test, but the guy wants it built, and wants it now, so I patched it up, and gave it back to the database team and told them to be careful.
    I'd be interested in you opinions regardless.
    The full spec of the "machine" is below, sol10 is not it's name for obvious reasons, and I've hashed out the ID & GIUD for similar reasons.
    # uname -a
    SunOS sol10 5.10 Generic_127128-11 i86pc i386 i86pc
    # prtdiag
    System Configuration: VMware, Inc. VMware Virtual Platform
    BIOS Configuration: Phoenix Technologies LTD 6.00 09/06/2007
    ==== Processor Sockets ====================================
    Version Location Tag
    Pentium(R) Pro CPU socket #0
    Pentium(R) Pro CPU socket #1
    ==== Memory Device Sockets ================================
    Type Status Set Device Locator Bank Locator
    DRAM in use 0 RAM slot #0 RAM slot #0
    DRAM in use 0 RAM slot #1 RAM slot #1
    DRAM in use 0 RAM slot #2 RAM slot #2
    DRAM in use 0 RAM slot #3 RAM slot #3
    ==== On-Board Devices =====================================
    VMware SVGA II
    ES1371
    ==== Upgradeable Slots ====================================
    ID Status Type Description
    0 unknown ISA ISA Slot J8
    0 unknown ISA ISA Slot J9
    0 unknown ISA ISA Slot J10
    1 in use PCI PCI Slot J11
    2 in use PCI PCI Slot J12
    3 in use PCI PCI Slot J13
    4 available PCI PCI Slot J14
    # dmesg
    Wednesday, 10 September 2008 15:33:35 BST
    Sep 10 10:17:44 sol10 busra: [ID 490441 kern.info] NOTICE: ndi_ra_free: bad free, dip ffffffff803807a8, resource type memory
    Sep 10 10:17:44 sol10 busra: [ID 883242 kern.info] NOTICE: ndi_ra_free: freeing base 0xe0000, len 0x4000 overlaps with existing resource base 0x0, len 0xf4000000
    Sep 10 10:17:44 sol10 rootnex: [ID 349649 kern.info] pci0 at root: space 0 offset 0
    Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] pci0 is /pci@0,0
    Sep 10 10:17:44 sol10 scsi: [ID 365881 kern.info] /pci@0,0/pci1000,30@10 (mpt0):
    Sep 10 10:17:44 sol10 Rev. 1 LSI, Inc. 1030 found.
    Sep 10 10:17:44 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: pci1000,30 (mpt) instance 0 vector 0x11 ioapic 0x2 intin 0x11 is bound to cpu 0
    Sep 10 10:17:44 sol10 scsi: [ID 365881 kern.info] /pci@0,0/pci1000,30@10 (mpt0):
    Sep 10 10:17:44 sol10 mpt0 Firmware version v0.0.0.0 (?)
    Sep 10 10:17:44 sol10 scsi: [ID 365881 kern.info] /pci@0,0/pci1000,30@10 (mpt0):
    Sep 10 10:17:44 sol10 mpt0: IOC Operational.
    Sep 10 10:17:44 sol10 pci: [ID 370704 kern.info] PCI-device: pci1000,30@10, mpt0
    Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] mpt0 is /pci@0,0/pci1000,30@10
    Sep 10 10:17:44 sol10 scsi: [ID 193665 kern.info] sd0 at mpt0: target 0 lun 0
    Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] sd0 is /pci@0,0/pci1000,30@10/sd@0,0
    Sep 10 10:17:44 sol10 genunix: [ID 408114 kern.info] /pci@0,0/pci1000,30@10/sd@0,0 (sd0) online
    Sep 10 10:17:44 sol10 unix: [ID 190185 kern.info] SMBIOS v2.31 loaded (1695 bytes)
    Sep 10 10:17:44 sol10 genunix: [ID 408114 kern.info] /cpus (cpunex0) online
    Sep 10 10:17:44 sol10 pseudo: [ID 129642 kern.info] pseudo-device: dld0
    Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] dld0 is /pseudo/dld@0
    Sep 10 10:17:44 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: i8042 (i8042) instance 0 vector 0x1 ioapic 0x2 intin 0x1 is bound to cpu 1
    Sep 10 10:17:44 sol10 pcplusmp: [ID 398438 kern.info] pcplusmp: i8042 (i8042) instance #0 vector 0xc ioapic 0x2 intin 0xc is bound to cpu 1
    Sep 10 10:17:44 sol10 i8042: [ID 526150 kern.info] 8042 device: keyboard@0, kb8042 # 0
    Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] kb80420 is /isa/i8042@1,60/keyboard@0
    Sep 10 10:17:44 sol10 i8042: [ID 526150 kern.info] 8042 device: mouse@1, mouse8042 # 0
    Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] mouse80420 is /isa/i8042@1,60/mouse@1
    Sep 10 10:17:44 sol10 unix: [ID 950921 kern.info] cpu0: x86 (GenuineIntel family 6 model 15 step 8 clock 2000 MHz)
    Sep 10 10:17:44 sol10 unix: [ID 950921 kern.info] cpu0: Intel(r) Xeon(r) CPU E5335 @ 2.00GHz
    Sep 10 10:17:47 sol10 unix: [ID 950921 kern.info] cpu1: x86 (GenuineIntel family 6 model 15 step 8 clock 2000 MHz)
    Sep 10 10:17:47 sol10 unix: [ID 950921 kern.info] cpu1: Intel(r) Xeon(r) CPU E5335 @ 2.00GHz
    Sep 10 10:17:47 sol10 unix: [ID 557827 kern.info] cpu1 initialization complete - online
    Sep 10 10:17:47 sol10 rootnex: [ID 349649 kern.info] iscsi0 at root
    Sep 10 10:17:47 sol10 genunix: [ID 936769 kern.info] iscsi0 is /iscsi
    Sep 10 10:17:52 sol10 genunix: [ID 454863 kern.info] dump on /dev/dsk/c1t0d0s1 size 8197 MB
    Sep 10 10:17:53 sol10 pci: [ID 370704 kern.info] PCI-device: pci8086,7191@1, pci_pci0
    Sep 10 10:17:53 sol10 genunix: [ID 936769 kern.info] pci_pci0 is /pci@0,0/pci8086,7191@1
    Sep 10 10:17:54 sol10 mac: [ID 469746 kern.info] NOTICE: e1000g0 registered
    Sep 10 10:17:54 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: pci8086,100f (e1000g) instance 0 vector 0x12 ioapic 0x2 intin 0x12 is bound to cpu 0
    Sep 10 10:17:54 sol10 e1000g: [ID 766679 kern.info] Intel(R) PRO/1000 Network Connection, Driver Ver. 5.1.11
    Sep 10 10:17:54 sol10 pseudo: [ID 129642 kern.info] pseudo-device: zfs0
    Sep 10 10:17:54 sol10 genunix: [ID 936769 kern.info] zfs0 is /pseudo/zfs@0
    Sep 10 10:17:55 sol10 pseudo: [ID 129642 kern.info] pseudo-device: pm0
    Sep 10 10:17:55 sol10 genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
    Sep 10 10:17:55 sol10 pseudo: [ID 129642 kern.info] pseudo-device: power0
    Sep 10 10:17:55 sol10 genunix: [ID 936769 kern.info] power0 is /pseudo/power@0
    Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
    Sep 10 10:17:56 sol10 rootnex: [ID 349649 kern.info] xsvc0 at root
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] xsvc0 is /xsvc
    Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: pseudo1
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] pseudo1 is /pseudo/zconsnex@1
    Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: lp (ecpp) instance 0 vector 0x7 ioapic 0x2 intin 0x7 is bound to cpu 1
    Sep 10 10:17:56 sol10 isa: [ID 202937 kern.info] ISA-device: ecpp0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] ecpp0 is /isa/lp@1,378
    Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: asy (asy) instance 0 vector 0x4 ioapic 0x2 intin 0x4 is bound to cpu 0
    Sep 10 10:17:56 sol10 isa: [ID 202937 kern.info] ISA-device: asy0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] asy0 is /isa/asy@1,3f8
    Sep 10 10:17:56 sol10 pcplusmp: [ID 398438 kern.info] pcplusmp: asy (asy) instance #1 vector 0x3 ioapic 0x2 intin 0x3 is bound to cpu 0
    Sep 10 10:17:56 sol10 isa: [ID 202937 kern.info] ISA-device: asy1
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] asy1 is /isa/asy@1,2f8
    Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: ide (ata) instance 0 vector 0xe ioapic 0x2 intin 0xe is bound to cpu 1
    Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: ide (ata) instance 0 vector 0xe ioapic 0x2 intin 0xe is bound to cpu 0
    Sep 10 10:17:56 sol10 genunix: [ID 640982 kern.info] ATAPI device at targ 0, lun 0 lastlun 0x0
    Sep 10 10:17:56 sol10 genunix: [ID 846691 kern.info] model VMware Virtual IDE CDROM Drive
    Sep 10 10:17:56 sol10 genunix: [ID 479077 kern.info] ATA/ATAPI-4 supported, majver 0x1e minver 0x17
    Sep 10 10:17:56 sol10 pci: [ID 370704 kern.info] PCI-device: ide@0, ata0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] ata0 is /pci@0,0/pci-ide@7,1/ide@0
    Sep 10 10:17:56 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:17:56 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:17:56 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:17:56 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:17:56 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:17:56 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:17:56 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:17:56 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:17:56 sol10 scsi: [ID 193665 kern.info] sd1 at ata0: target 0 lun 0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] sd1 is /pci@0,0/pci-ide@7,1/ide@0/sd@0,0
    Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: fdc (fdc) instance 0 vector 0x6 ioapic 0x2 intin 0x6 is bound to cpu 1
    Sep 10 10:17:56 sol10 isa: [ID 202937 kern.info] ISA-device: fdc0
    Sep 10 10:17:56 sol10 fdc: [ID 114370 kern.info] fd0 at fdc0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] fd0 is /isa/fdc@1,3f0/fd@0,0
    Sep 10 10:17:56 sol10 genunix: [ID 314293 kern.info] device pciclass,030000@f(display#0) keeps up device sd@0,0(sd#1), but the latter is not power managed
    Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: nvidia255
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] nvidia255 is /pseudo/nvidia@255
    Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk@1024
    Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lockstat0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat@0
    Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: llc10
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0
    Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lofi0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0
    Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: dtrace0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] dtrace0 is /pseudo/dtrace@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: profile0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] profile0 is /pseudo/profile@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: systrace0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fbt0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: sdt0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fasttrap0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fasttrap0 is /pseudo/fasttrap@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fcp0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lx_systrace0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] lx_systrace0 is /pseudo/lx_systrace@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: ucode0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] ucode0 is /pseudo/ucode@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: winlock0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: vol0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] vol0 is /pseudo/vol@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: rsm0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] rsm0 is /pseudo/rsm@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: pool0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] pool0 is /pseudo/pool@0
    Sep 10 10:17:57 sol10 ipf: [ID 774698 kern.info] IP Filter: v4.1.9, running.
    Sep 10 10:18:05 sol10 nfs4cbd[395]: [ID 867284 daemon.notice] nfsv4 cannot determine local hostname binding for transport tcp - delegations will not be available on this transport
    Sep 10 10:18:10 sol10 sendmail[598]: [ID 702911 mail.crit] My unqualified host name (localhost) unknown; sleeping for retry
    Sep 10 10:18:10 sol10 sendmail[600]: [ID 702911 mail.crit] My unqualified host name (localhost) unknown; sleeping for retry
    Sep 10 10:18:17 sol10 mac: [ID 736570 kern.info] NOTICE: e1000g0 unregistered
    Sep 10 10:19:10 sol10 sendmail[598]: [ID 702911 mail.alert] unable to qualify my own domain name (localhost) -- using short name
    Sep 10 10:19:10 sol10 sendmail[600]: [ID 702911 mail.alert] unable to qualify my own domain name (localhost) -- using short name
    Sep 10 10:20:10 sol10 pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
    Sep 10 10:20:10 sol10 genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
    Sep 10 10:24:54 sol10 mac: [ID 469746 kern.info] NOTICE: e1000g0 registered
    Sep 10 10:24:54 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: pci8086,100f (e1000g) instance 0 vector 0x12 ioapic 0x2 intin 0x12 is bound to cpu 0
    Sep 10 10:24:54 sol10 e1000g: [ID 766679 kern.info] Intel(R) PRO/1000 Network Connection, Driver Ver. 5.1.11
    Sep 10 10:24:59 sol10 e1000g: [ID 801725 kern.info] NOTICE: pci8086,100f - e1000g[0] : Adapter 1000Mbps full duplex copper link is up.
    Sep 10 10:28:21 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
    Sep 10 10:35:17 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:35:17 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:35:17 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:35:17 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:35:17 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:35:17 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:35:17 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:35:17 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:35:17 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: lp (ecpp) instance 0 vector 0x7 ioapic 0x2 intin 0x7 is bound to cpu 1
    Sep 10 10:35:17 sol10 isa: [ID 202937 kern.info] ISA-device: ecpp0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] ecpp0 is /isa/lp@1,378
    Sep 10 10:35:17 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: asy (asy) instance 0 vector 0x4 ioapic 0x2 intin 0x4 is bound to cpu 0
    Sep 10 10:35:17 sol10 isa: [ID 202937 kern.info] ISA-device: asy0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] asy0 is /isa/asy@1,3f8
    Sep 10 10:35:17 sol10 pcplusmp: [ID 398438 kern.info] pcplusmp: asy (asy) instance #1 vector 0x3 ioapic 0x2 intin 0x3 is bound to cpu 0
    Sep 10 10:35:17 sol10 isa: [ID 202937 kern.info] ISA-device: asy1
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] asy1 is /isa/asy@1,2f8
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: nvidia255
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] nvidia255 is /pseudo/nvidia@255
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk@1024
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lockstat0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: llc10
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lofi0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: profile0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] profile0 is /pseudo/profile@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: systrace0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fbt0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: sdt0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fcp0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lx_systrace0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] lx_systrace0 is /pseudo/lx_systrace@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: ucode0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] ucode0 is /pseudo/ucode@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: winlock0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: pm0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: rsm0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] rsm0 is /pseudo/rsm@0
    Sep 10 10:55:50 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:55:50 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:55:50 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:55:50 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:55:50 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:55:50 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:55:50 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:55:50 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 11:28:55 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
    Sep 10 12:28:56 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
    Sep 10 13:29:01 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
    Sep 10 14:29:10 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
    Sep 10 15:29:38 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
    # prtconf
    System Configuration: Sun Microsystems i86pc
    Memory size: 4132 Megabytes
    System Peripherals (Software Nodes):
    i86pc
    scsi_vhci, instance #0
    isa, instance #0
    i8042, instance #0
    keyboard, instance #0
    mouse, instance #0
    lp, instance #0
    asy, instance #0
    asy, instance #1
    fdc, instance #0
    fd, instance #0
    pci, instance #0
    pci15ad,1976 (driver not attached)
    pci8086,7191, instance #0
    pci15ad,1976 (driver not attached)
    pci-ide, instance #0
    ide, instance #0
    sd, instance #1
    ide (driver not attached)
    pci15ad,1976 (driver not attached)
    display, instance #0
    pci1000,30, instance #0
    sd, instance #0
    pci15ad,750, instance #0
    iscsi, instance #0
    pseudo, instance #0
    options, instance #0
    agpgart, instance #0
    xsvc, instance #0
    objmgr, instance #0
    acpi (driver not attached)
    used-resources (driver not attached)
    cpus, instance #0
    cpu (driver not attached)
    cpu (driver not attached)
    # format
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
    0. c1t0d0 <DEFAULT cyl 10440 alt 2 hd 255 sec 63>
    /pci@0,0/pci1000,30@10/sd@0,0
    Specify disk (enter its number): 0
    selecting c1t0d0
    [disk formatted]
    Warning: Current Disk has mounted partitions.
    /dev/dsk/c1t0d0s0 is currently mounted on /. Please see umount(1M).
    /dev/dsk/c1t0d0s1 is currently used by swap. Please see swap(1M).
    /dev/dsk/c1t0d0s3 is currently mounted on /usr. Please see umount(1M).
    /dev/dsk/c1t0d0s4 is currently mounted on /var. Please see umount(1M).
    /dev/dsk/c1t0d0s5 is currently mounted on /opt. Please see umount(1M).
    /dev/dsk/c1t0d0s6 is part of SVM volume sp:d8. Please see metaclear(1M).
    /dev/dsk/c1t0d0s7 contains an SVM mdb. Please see metadb(1M).
    FORMAT MENU:
    disk - select a disk
    type - select (define) a disk type
    partition - select (define) a partition table
    current - describe the current disk
    format - format and analyze the disk
    fdisk - run the fdisk program
    repair - repair a defective sector
    label - write label to the disk
    analyze - surface analysis
    defect - defect list management
    backup - search for backup labels
    verify - read and display labels
    save - save new disk/partition definitions
    inquiry - show vendor, product and revision
    volname - set 8-character volume name
    !<cmd> - execute <cmd>, then return
    quit
    format> p
    PARTITION MENU:
    0 - change `0' partition
    1 - change `1' partition
    2 - change `2' partition
    3 - change `3' partition
    4 - change `4' partition
    5 - change `5' partition
    6 - change `6' partition
    7 - change `7' partition
    select - select a predefined table
    modify - modify a predefined partition table
    name - name the current table
    print - display the current table
    label - write partition map and label to the disk
    !<cmd> - execute <cmd>, then return
    quit
    partition> p
    Current partition table (original):
    Total disk cylinders available: 10440 + 2 (reserved cylinders)
    Part Tag Flag Cylinders Size Blocks
    0 root wm 1 - 131 1.00GB (131/0/0) 2104515
    1 swap wu 132 - 1176 8.01GB (1045/0/0) 16787925
    2 backup wm 0 - 10439 79.97GB (10440/0/0) 167718600
    3 usr wm 1177 - 1829 5.00GB (653/0/0) 10490445
    4 var wm 1830 - 2091 2.01GB (262/0/0) 4209030
    5 unassigned wm 2092 - 2614 4.01GB (523/0/0) 8401995
    6 unassigned wm 2617 - 10439 59.93GB (7823/0/0) 125676495
    7 unassigned wm 2615 - 2616 15.69MB (2/0/0) 32130
    8 boot wu 0 - 0 7.84MB (1/0/0) 16065
    9 unassigned wm 0 0 (0/0/0) 0
    partition> quit
    FORMAT MENU:
    disk - select a disk
    type - select (define) a disk type
    partition - select (define) a partition table
    current - describe the current disk
    format - format and analyze the disk
    fdisk - run the fdisk program
    repair - repair a defective sector
    label - write label to the disk
    analyze - surface analysis
    defect - defect list management
    backup - search for backup labels
    verify - read and display labels
    save - save new disk/partition definitions
    inquiry - show vendor, product and revision
    volname - set 8-character volume name
    !<cmd> - execute <cmd>, then return
    quit
    format> q
    # metastat -p
    d8 -p c1t0d0s6 -o 109973513 -b 61440
    d7 -p c1t0d0s6 -o 109461512 -b 512000
    d6 -p c1t0d0s6 -o 109051911 -b 409600
    d5 -p c1t0d0s6 -o 88080390 -b 20971520
    d4 -p c1t0d0s6 -o 67108869 -b 20971520
    d3 -p c1t0d0s6 -o 46137348 -b 20971520
    d2 -p c1t0d0s6 -o 41943043 -b 4194304
    d1 -p c1t0d0s6 -o 20971522 -b 20971520
    d0 -p c1t0d0s6 -o 1 -b 20971520

    An easy way to think of it is this -- everything in Unix is a file. Including directories; they are just a file which contains a list of the files in that directory, and pointers to them.
    If the 'sybase' user has write permission on the directory, they have permission to edit that "list", and can add or remove files to the list. It doesn't matter who the files on the list belong to, because the files are not what is being modified. Only the list of files is being modified. (Of course, in Unix, if you erase the file's listing from all of the lists it's on, the file itself goes away for housekeeping purposes.)
    One thing that would have stopped the 'sybase' user from removing the lost+found directory is if that directory itself had files in it -- without write permission to the lost+found directory, that user could not have removed those files, and since one cannot remove a non-empty directory, that operation would have failed. Since lost+found was empty in this case, it could be removed simply by having permission to write to the /apps directory.
    This behavior does change if you set the sticky bit on the directory -- in that case, files may only be removed by the owner of the file or directory, or if the user has write permission to the file. This would have prevented the sybase user from removing the lost+found directory. (Note, this also applies to the 'rename' function call.) This would probably be the best way to handle your situation, since you apparently do want the sybase user to be able to add files to /apps, but do not want them to be able to remove lost+found.
    Edited by: MadBishop on Sep 12, 2008 7:46 AM

  • How to correctly allocate size while creating FileSystem

    I am finding difficulty in creating and allocating correct size to File Systems on solarix x86 box. Please see below contents I followed on screen and in the end It shows that /app file system is created of size 135GB , I wanted it to be 30gb as mentioned during 'format' command in 'Enter Partitiion size' :
    root@unknown # df -k
    Filesystem kbytes used avail capacity Mounted on
    /dev/dsk/c0t0d0s0 15496821 7472292 7869561 49% /
    /devices 0 0 0 0% /devices
    ctfs 0 0 0 0% /system/contract
    proc 0 0 0 0% /proc
    mnttab 0 0 0 0% /etc/mnttab
    swap 17574616 808 17573808 1% /etc/svc/volatile
    objfs 0 0 0 0% /system/object
    /usr/lib/libc/libc_hwcap2.so.1
    15496821 7472292 7869561 49% /lib/libc.so.1
    fd 0 0 0 0% /dev/fd
    swap 17573844 36 17573808 1% /tmp
    swap 17573840 32 17573808 1% /var/run
    root@unknown # format
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
    0. c0t0d0 <DEFAULT cyl 17832 alt 2 hd 255 sec 63>
    /pci@0,0/pci1022,7450@2/pci1000,3060@3/sd@0,0
    1. c0t2d0 <DEFAULT cyl 17846 alt 2 hd 255 sec 63>
    /pci@0,0/pci1022,7450@2/pci1000,3060@3/sd@2,0
    2. c0t3d0 <DEFAULT cyl 17845 alt 2 hd 255 sec 63>
    /pci@0,0/pci1022,7450@2/pci1000,3060@3/sd@3,0
    Specify disk (enter its number): 0
    selecting c0t0d0
    [disk formatted]
    Warning: Current Disk has mounted partitions.
    /dev/dsk/c0t0d0s0 is currently mounted on /. Please see umount(1M).
    /dev/dsk/c0t0d0s1 is currently used by swap. Please see swap(1M).
    FORMAT MENU:
    disk - select a disk
    type - select (define) a disk type
    partition - select (define) a partition table
    current - describe the current disk
    format - format and analyze the disk
    fdisk - run the fdisk program
    repair - repair a defective sector
    label - write label to the disk
    analyze - surface analysis
    defect - defect list management
    backup - search for backup labels
    verify - read and display labels
    save - save new disk/partition definitions
    inquiry - show vendor, product and revision
    volname - set 8-character volume name
    !<cmd> - execute <cmd>, then return
    quit
    format> p
    PARTITION MENU:
    0 - change `0' partition
    1 - change `1' partition
    2 - change `2' partition
    3 - change `3' partition
    4 - change `4' partition
    5 - change `5' partition
    6 - change `6' partition
    7 - change `7' partition
    select - select a predefined table
    modify - modify a predefined partition table
    name - name the current table
    print - display the current table
    label - write partition map and label to the disk
    !<cmd> - execute <cmd>, then return
    quit
    partition> p
    Current partition table (original):
    Total disk cylinders available: 17832 + 2 (reserved cylinders)
    Part Tag Flag Cylinders Size Blocks
    0 root wm 524 - 2482 15.01GB (1959/0/0) 31471335
    1 swap wu 1 - 523 4.01GB (523/0/0) 8401995
    2 backup wm 0 - 17831 136.60GB (17832/0/0) 286471080
    3 unassigned wm 2483 - 4441 15.01GB (1959/0/0) 31471335
    4 unassigned wm 0 0 (0/0/0) 0
    5 unassigned wm 0 0 (0/0/0) 0
    6 unassigned wm 0 0 (0/0/0) 0
    7 unassigned wm 0 0 (0/0/0) 0
    8 boot wu 0 - 0 7.84MB (1/0/0) 16065
    9 unassigned wm 0 0 (0/0/0) 0
    partition> 3
    Part Tag Flag Cylinders Size Blocks
    3 unassigned wm 2483 - 4441 15.01GB (1959/0/0) 31471335
    Enter partition id tag[unassigned]: usr
    Enter partition permission flags[wm]:
    Enter new starting cyl[2483]: 2483
    Enter partition size[31471335b, 1959c, 4441e, 15366.86mb, 15.01gb]: 30gb
    partition> p
    Current partition table (unnamed):
    Total disk cylinders available: 17832 + 2 (reserved cylinders)
    Part Tag Flag Cylinders Size Blocks
    0 root wm 524 - 2482 15.01GB (1959/0/0) 31471335
    1 swap wu 1 - 523 4.01GB (523/0/0) 8401995
    2 backup wm 0 - 17831 136.60GB (17832/0/0) 286471080
    3 usr wm 2483 - 6399 30.01GB (3917/0/0) 62926605
    4 unassigned wm 0 0 (0/0/0) 0
    5 unassigned wm 0 0 (0/0/0) 0
    6 unassigned wm 0 0 (0/0/0) 0
    7 unassigned wm 0 0 (0/0/0) 0
    8 boot wu 0 - 0 7.84MB (1/0/0) 16065
    9 unassigned wm 0 0 (0/0/0) 0
    partition> label
    Ready to label disk, continue? y
    partition>q
    root@unknown # newfs /dev/rdsk/c0t0d0s2
    newfs: construct a new file system /dev/rdsk/c0t0d0s2: (y/n)? y
    Warning: 5208 sector(s) in last cylinder unallocated
    /dev/rdsk/c0t0d0s2: 286471080 sectors in 46627 cylinders of 48 tracks, 128 sectors
    139878.5MB in 2915 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
    super-block backups (for fsck -F ufs -o b=#) at:
    32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
    Initializing cylinder groups:
    super-block backups for last 10 cylinder groups at:
    285576352, 285674784, 285773216, 285871648, 285970080, 286068512, 286166944,
    286265376, 286363808, 286462240
    root@unknown # mount /dev/dsk/c0t0d0s2 /app
    root@unknown # df -k /app
    Filesystem kbytes used avail capacity Mounted on
    /dev/dsk/c0t0d0s2 141066718 65553 139590498 1% /app
    root@unknown #
    Please advice, what is wrong I am doing above?

    panchpan wrote:
    THANKS a lot - The size allocation is resolved now :-) Please see few questions, perhaps I missed to have this basic knowledege
    1) How to create more than 7 partitions?
    2) Slice 9 seems to be unassigned. But I am not able to allocate 9 - It says '9' is not expected as shown below:
    Part Tag Flag Cylinders Size Blocks
    0 root wm 524 - 2482 15.01GB (1959/0/0) 31471335
    1 swap wu 1 - 523 4.01GB (523/0/0) 8401995
    2 backup wm 0 - 17831 136.60GB (17832/0/0) 286471080
    3 usr wm 2484 - 6400 30.01GB (3917/0/0) 62926605
    4 usr wm 2485 - 3790 10.00GB (1306/0/0) 20980890
    5 usr wm 2486 - 5096 20.00GB (2611/0/0) 41945715
    6 usr wm 2487 - 5097 20.00GB (2611/0/0) 41945715
    7 usr wm 2488 - 5098 20.00GB (2611/0/0) 41945715
    8 boot wu 0 - 0 7.84MB (1/0/0) 16065
    9 unassigned wm 0 0 (0/0/0) 0
    partition> 9
    `9' is not expected.
    3) How to give different names in 'Tag'?
    4) How to know actually, How much size can be distributed among user defined partitions?
    5) On solaris, How do we actually verify IF mirroring is in place?1) You create a really big slice and use soft partitioning. Otherwise 7 hard partitions are all you can assign.
    2) That's an alternate system partition. You can't touch it and there's only 2 cylinders in it anyway.
    3) There are only certain values that are legal. You generally don't adjust them.
    4) Slice 2 is the entire usable space. That tells you how much you can distribute among the 7 (0,1,3,4,5,6,7) partitions/slices available to you. In your case; that's about 137 GB.
    5) It isn't by default. You have to take positive actions with either Logical Volume Manager (aka Solstice Disk Suite for us old school guys) or some other form of volume manager. LVM is free with the OS and does a great job of mirroring the OS. I personally wouldn't use it for managing a form of disks; but it's perfect for the OS mirroring.
    Edited by: John.Kotches on Nov 12, 2007 12:46 PM

  • Format disks in a non-global zone

    Hi
    Can i format a disk inside a non global zone which has been assigned (add device) to this non-global zone.
    thanks

    In order to allow managing his/her disk to the zone "administrator".
    This is what i�ve got when i try to format the disk in the non-global zone:
    AVAILABLE DISK SELECTIONS:
    0. c4t600A0B8000179A5000002EFD42AFC76Fd0 <SUN-CSM100_R_FC-0610 cyl 20478 alt 2 hd 64 sec 64> sx2_v2
    ssd22 at scsi_vhci0 slave 0
    1. c4t600A0B8000179A5000002F0A4355CEE9d0 <SUN-CSM100_R_FC-0610 cyl 20478 alt 2 hd 64 sec 64>
    ssd24 at scsi_vhci0 slave 0
    Specify disk (enter its number): 1
    selecting c4t600A0B8000179A5000002F0A4355CEE9d0
    [disk unformatted]
    FORMAT MENU:
    disk - select a disk
    type - select (define) a disk type
    partition - select (define) a partition table
    current - describe the current disk
    format - format and analyze the disk
    repair - repair a defective sector
    label - write label to the disk
    analyze - surface analysis
    defect - defect list management
    backup - search for backup labels
    verify - read and display labels
    save - save new disk/partition definitions
    inquiry - show vendor, product and revision
    volname - set 8-character volume name
    !<cmd> - execute <cmd>, then return
    quit
    format> format
    Ready to format. Formatting cannot be interrupted.
    Continue? yes
    Beginning format. The current time is Thu Nov 10 12:59:50 2005
    Inquiry failed
    failed
    Warning: Unable to get capacity. Cannot check geometry
    Warning: error reading backup label.
    Warning: error reading backup label.
    Warning: error reading backup label.
    Warning: error reading backup label.
    Warning: error reading backup label.

  • Using a 160GB Disk with Solaris 8

    Hello all:
    I am using an Ultra5 system with OBP 3.25.3, Solaris 8 [10/01]. I have a 160GB Seagate ST3160812A disk drive that I am trying to use as a second drive (primary slave).
    I have installed the drive on the primary channel as a slave and performed boot -r. The /dev and /devices directories correctly setup device links (c0t1d0) for the drive.
    Assuming all was good I tried to create a new file system on slice 0 with "newfs /dev/rdsk/c0t1d0s0". This responded with
    /dev/rdsk/c0t1d0s0: I/O error
    I then used the "format" command to see what was going on. I can see the drive in the 'format' command:
    #format
    AVAILABLE DISK SELECTIONS
    0. c0t0d0 <ST320420A cyl 39533 alt 2 hd 16 sec 63>...
    1. c0t1d0 <ST3160812A cyl 255 alt 2 hd 16 sec 255>...
    Specify disk (enter...) : 1
    selecting c0t1d0
    (disk formatted, no defect list found)
    format> quit
    As can be seen the 160GB drive has parameters that are all wrong for this size disk. The #format->verify command output for slice 2 (backup) shows the following:
    ascii name = <ST3160812A cyl 255 alt 2 hd 16 sec 255>
    pcyl = 257
    ncyl = 255
    acyl = 2
    nhead = 16
    nsect = 255
    Part Tag Flag Cylinders Size Blocks
    0 unassigned wm 0 0 (0/0/0) 0
    1 :: :: ::
    2 backup wu 0 - 254 508.01MB (255/0/0) 1040400
    3 unassigned wm 0 0 (0/0/0) 0
    7 unassigned wm 0 0 (0/0/0) 0
    I recalled that at boot-up the system showed a 'wrong magic number' message on the new drive. I tried to re-label the drive (format->label). The 'magic number' message went away on the next reboot but the 'format->verify' still showed the same thing.
    I have tried several approaches to fix this:
    1. I have read several posts and on-line texts that indicate the 137GB limit associated with LBA addressing for the Ultra5 IDE controllers. I have also read the post "How can I use my 160G Disk?"
    (http://forum.java.sun.com/thread.jspa?forumID=829&threadID=5065871)
    which provided great information and described using the "format" command to configure the disk with 65535 cylinders.
    When I use the "format->type" command I get the following:
    #format
    format> type
    AVAILABLE DRIVE TYPES:
    0. ST320420A
    1. ST3160812A
    2. other
    According to the "How can I use..." post, I select [2] other and set parameters. When I get to the first parameter to set the cylinders to 65535 I get the following:
    Enter number of data cylinders: 65535
    '65535' is out of range
    a. Using the #format->type {other} function to change the # of cylinders is not accepted by the OS. In fact any value over 32000 cylinders is rejected by the command.
    b. Just in case I also tried using the [1] disk type. I get the message:
    "disk formatted, no defect list found"
    So the suggestion in this post did not work in my case.
    2. Next I tried referring to the post "Sun Ultra 5 Hard Drive"
    (http://forum.java.sun.com/thread.jspa?forumID=860&threadID=5068466)
    which suggested using the dd command to 'nuke' the disk label and re-label with format. So using the command:
    dd if=/dev/zero of=/dev/rdsk/c0t1d0s2 bs1b count =16
    the command is processed properly but when I perform "format->verify"
    the label is unchanged even after I re-execute the "format->label" command. Rebooting the system did not change it either.
    3. I also attempted to use the 'format->part->modify' command to change the partition. When the command gets to the 'Free Hog Partition[6]" prompt I get a 'warning: no space available from Free Hog partition" message.
    4. I also tried using the 'format->part' command to directly modify the specific '2' partition from the partition menu.
    format>part
    partition> 2
    Part Tag Flag Cylinders Size Blocks
    2 backup wu 0 - 254 508.01MB (255/0/0) 1040400
    Enter partition id tag[backup]; <return>
    Enter partition permission flags [wu]: <return>
    Enter new starting cylinder cyl[0]: <return>
    Enter partition size [1040400b, 255c, 508.01mb, 0.50gb]: 100g
    '100.00gb is out of range'
    ^D
    For some reason even this command limits the partition size.
    5. My last ditch attempt was to use fdisk -S <geom_file> to set the label geometry with the following parameters in the file:
    pcyl: 65535
    ncyl: 65535
    acyl: 2
    bcyl: 0
    nheads: 16
    nsectors: 255
    secsize: 512
    When I run this command the command core dumps.
    I'm somewhat lost as to what is preventing me from even using the suggestions others have found useful.
    Has anyone successfully used a 160GB Seagate (ST3160812A or other 160GB model) drive with the following?
    (as defined by #showrev and #prtconf)
    system: Ultra5
    OS: Solaris 8 [10.01 assumed based on kernel date]
    Kernel: SunOS 5.8 Generic 108528-13 December 2001
    OBP 3.25.3 2000/06/29 14:12
    kernel architecture: sun4u
    My hardware guy has tried numerous times to get a 120GB drive (which some posts indicated should work without any problems) but they are very hard to find. If I can get the 160GB drive to work (even with 137GB) I'll be happy.
    Thanks for any information.
    elbowz

    Your version of the OBP as well as the Solaris kernel are not the most up-to-date. If the system is stable without the new disk I would upgrade the OBP to the last version (3.31). It may also be worthwhile to patch the kernel with the recommended cluster patches (if you have enough disk space).

  • 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)

  • Format utility in Solaris 10

    During the preparation of my SCSA exam I found the folowing:
    Place each format utility by the right function
    Updates the disks VTOC ---- Partition
    Reads and displays labels ---- Disk
    Allows you to select a new disk ---- Label
    Saves disk and slice information to a file ---- Save
    Alters size slices ---- Fomat
    Formats and analyzes the disk ---- Verify
    My answers are:
    Updates the disks VTOC --> Label
    Reads and displays labels --> Verify
    Allows you to select a new disk --> Disk
    Saves disk and slice information to a file --> Save
    Alters size slices --> Partition
    Formats and analyzes the disk --> Format
    But the answers in the course are:
    Updates the disks VTOC --> Save
    Reads and displays labels --> Label
    Allows you to select a new disk --> Verify
    Saves disk and slice information to a file --> Format
    Alters size slices --> Partition
    Formats and analyzes the disk --> Disk
    So can someone tell me what the real answers are because I don't know it anymore. ;-)

    I would say your answers are correct:
    FORMAT MENU:
    disk - select a disk
    type - select (define) a disk type
    partition - select (define) a partition table
    current - describe the current disk
    format - format and analyze the disk
    fdisk - run the fdisk program
    repair - repair a defective sector
    label - write label to the disk
    analyze - surface analysis
    defect - defect list management
    backup - search for backup labels
    verify - read and display labels
    save - save new disk/partition definitions
    inquiry - show vendor, product and revision
    volname - set 8-character volume name
    !<cmd> - execute <cmd>, then return
    quit
    format>
    Your instructor agrees with the answers in the course???

  • Importing from iphoto, always get "import failed".

    I am trying to move my pictures from iphoto to elements.
    I "import from files and folders" and choose import from iphoto.
    I have 87,0000 pictures.
    It fails saying "import failed".
    I check the disk, and the files are there but no pictures in the catalog.
    I try to remove the files that it says are damaged.  I have done that.  I still get "import failed" with no report of why.
    I see many other posts with this same issue, and no good solution.
    I tried to create a new catalog, no difference.
    Help!
    Mac OS X
    Elements 12.0
    I have had Elements for the mac for 3 months now and still can't use it!

    I did the "from iPhoto" and got the problem listed above.  I want the whole library transferred.
    I am looking for a solution to the elements defect listed above.  If I import the library, and it has a problem with a single photo, it should not import that photo, but do the rest.  It is not doing that, it is failing and not importing anything.
    This is especially frustrating since it take hours to import the library, then when it is 95% done, it fails and imports nothing.

  • Hash # in url

    APEX version 3.1.2.00.02
    I have a interactive report with a few columns of which one is a link. The link is created from page items and column values. The URL for the link might look like
    f?p=&APP_ID.:8:&SESSION.::&DEBUG.:RP:P8_NAME,P8_SHOW:#NAME#,&P7_SHOW.
    The problem is that I don't explicitly deal with hashmarks. Once a while a get a name such as bill#gates which in the example above results in P8_SHOW not being set and P8_NAME being set to bill only. And yes the link has "Display Text As" set to "Display as Text (escape special characters)".
    Cheers Niklas

    Niklas,
    Thanks for pointing that out. The hashmark is deliberately preserved in links so that a hashmark used as a fragment delimiter can be part of the URL. When the hashmark appears within an item value, however, this doesn't have the desired effect. This puts the hashmark in the same category as a colon -- one that cannot be part of an item value in a URL. (This limitation applies only to links that use apex_util.prepare_url, as most links do. However, you could use PL/SQL to dynamically emit a link that passed an escaped hashmark in an item value.)
    I'll put this on a defect list for future improvements.
    Scott

  • Unity 4.2(1.0) delayed messages

    We have customer who are having issues of delayed delivery of voicemails.. sometimes days...
    The problem is that Unity holds some voicemails for days before releasing them. Some users saying that after return from holiday, they clear down all voicemails and then the following day they get some from a few days ago.
    I have restarted the server and MTA service but this issue seems to return after few days.
    Any idea what could be the issue or is there a bug in this version?
    Help would be much appreciated.
    Thanks

    this is the text for the Cisco Unity 4.2(1) Engineering Special 173 (I also reported the broken link that you saw earlier):
    Release Notes for 4.2(1) Engineering Special 173
    System Requirements
    Overview
    Engineering Special Installation Instructions
    Post Installation Steps
    New Options and Features
    Uninstall Instructions
    Resolved Defects
    System Requirements
    This Engineering Special (patch) requires Cisco Unity 4.2(1) and needs to be installed on both Primary and Secondary Cisco Unity failover servers in the case of a failover configuration.
    Overview
    A complete list of defects addressed by this Engineering Special can be found in the section titled Resolved Defects. This Engineering Special is a roll-up of the following Engineering Specials and service patches:
    ES172, ES171, ES170, ES169, ES168, ES167, ES166, ES165, ES164, ES163, ES162, ES161, ES160, ES159, ES158, ES157, ES155, ES153, ES152, ES150, ES149, ES148, ES147, ES146, ES145, ES144, ES143, ES142, ES140, ES139, ES137, ES135, ES134, ES133, ES132, ES131, ES130, ES129, ES127, ES126, ES125, ES123, ES122, ES121, ES120, ES119, ES118, ES117, ES116, ES115, ES114, ES113, ES112, ES111, ES110, ES109, ES108, ES107, ES106, ES105, ES104, ES103, ES102, ES101, ES100, ES99, ES98, ES97, ES96, ES95, ES94, ES93, ES92, ES91, ES89, ES88, ES87, ES86, ES85, ES84, ES83, ES82, ES81, ES80, ES79, ES78, ES77, ES76, ES75, ES73, ES72, ES71, ES70, ES69, ES68, ES67, ES66, ES64, ES63, ES62, ES61, ES59, ES58, ES57, ES56, ES55, ES54, ES53, ES52, ES51, ES50, ES49, ES48, ES47, ES46, ES44, ES43, ES42, ES41, ES40, ES39, ES38, ES37, ES36, ES35, ES34, ES33, ES32, ES31, ES30, ES28, ES27, ES26, ES25, ES24, ES23, ES22, ES20, ES19, ES18, ES17, ES16, ES15, ES14, ES13, ES12, ES11, ES10, ES9, ES8, ES6, ES5, ES4, ES3, ES2, ES1
    Engineering Special Installation Instructions
    Logon to the Cisco Unity server console either directly (physical console) or via VNC (do not use Terminal Services / Remote Desktop)
    Double click the executable install file CU4.2(1)_ES173.exe
    Step through the installation wizard clicking 'Next' as appropriate
    Once the installation has completed select the option to reboot the Cisco Unity server
    Post Installation Steps
    1) This patch must be installed after applying this Engineering Special, available here for download: Other non-Cisco Unity Patch 70.
    This patch installs new prompts to provide a warning when the Reply-All recipient list either contains a PDL or is above a threshold.
    2) These steps must be applied after applying this Engineering Special:
    a. Stop Tomcat service.
    b. Delete only the files in
    \CommServer\cscoserv\Tomcat\work\Standalone\localhost\ciscopca directory.
    c. Restart Tomcat service.
    3) Customers using the Blackberry feature with Cisco Unity must apply this patch on the Blackberry server after applying this Engineering Special, available here for download: Other non-Cisco Unity Patch 76.
    4) Customers with systems based in Australia shall be affected by the Daylight Saving Time changes introduced by the Australian Gov't across several of their territories. The changes cause systems to report incorrect time stamps and to resolve them patches from Microsoft and Sun Microsystems must be applied after applying this engineering special:
    Sun Microsystems patch:
    a. Download the TZUpdater 1.2.2 or later from here: TZ Updater to the Cisco Unity system.
    b. Stop the Tomcat service.
    c. Unzip the contents to the same folder, file extracted tzupdater.jar
    d. Open a CMD window and change directories to where tzupdater.jar is located
    e. Enter "%JAVA_HOME%\jre\bin\java -jar tzupdater.jar -u -v -bc" and press enter. The output should be similar to this:
    - java.home: E:\CommServer\cscoserv\Java2SDK\jre
    - java.vendor: Sun Microsystems Inc.
    - java.version: 1.4.2_13
    - JRE time zone data version: tzdata2006g
    - Embedded time zone data version: tzdata2007h
    - Extracting files... done.
    - Making changes for JDK 1.1 compatibility... done.
    - Renaming directories... done.
    - Validating the new time zone data... done.
    - Time zone data update is complete.
    Windows Patch
    Apply the relevant Windows patch (Windows 2003 SP1/SP2 or Windows 2000 SP4) to the following machines:
    a. Each Cisco Unity Server
    b. Each Cisco Unity Bridge
    c. All servers hosting Microsoft Exchange or Lotus Domino housing a mailbox of a Cisco Unity subscriber
    d. The Cisco Unity partner mail server
    e. Each Exchange server with the Internet Voice Connector installed
    f. Each domain controller in an Active Directory (AD) domain with a Cisco Unity server
    g. Each global catalog server within the AD forest where Cisco Unity is present
    The Windows 2003 SP1/SP2 patch may be obtained directly from Microsoft under Knowledge Base article 955839. The Windows 2000 SP4 patch, KB article 942763, is only available to customers with a Microsoft Extended Hotfix Service Agreement for Windows 2000.
    Defect: CSCsm32946, CSCtc11035
    4) Customer sites where Cisco Unity integrated with multiple PIMG devices is failing to start after Microsoft hotfix MS08-037 - KB 953230 was applied must do the following after applying this Engineering Special:
    a) Open and close the Manage Integrations (UTIM) utility.
    b) Reboot the Cisco Unity server for the changes to take affect.
    Defect: CSCsv54175
    New Options and Features
    The following sections detail how to enable new options and features that are supported by this ES. Prior to following these steps, you must first install the ES as per the above Engineering Special Installation Instructions section
    1) Customers wishing to change the number of Microsoft Exchange mailstores Cisco Unity supports, shall need to modify the registry key found here:
    [\HKLM\Software\Active Voice\AvWm\1.00]
    Registry Key Name: Max Stores
    Registry Key Type: DWORD
    Registry Key Default Value: 250
    Other Settings:
    After changing the number of mailstores to support, stop Cisco Unity and the CuMdbStoreMonitor service and then re-start Cisco Unity.
    Defect: CSCsu03848
    2) Customer's wishing to enable the enhanced Cross-server login functionality shall need to upgrade to the latest version of the Advanced Setting Tools.
    Launch the Advanced Setting Tool and look for Networking - Allow Transfer Override on Cross-server Transfer Handoff and follow the instructions in the description for a full understanding on how this works feature can be enabled/disabled.
    Defect: CSCsd69934
    3) Customer's wishing to enable the enhanced functionality for transfers to alternate contact numbers shall need to upgrade to the latest version of the Advanced Setting Tools.
    Launch the Advanced Setting Tool and look for Conversation - ACN Follows Current Transfer Rule and follow the instructions in the description for a full understanding on how this works feature can be enabled/disabled.
    Defect: CSCsi02306
    4) Customers wishing to enable the functionality to prevent accidentally reply-all to PDLs shall need to upgrade to the latest version of the Advanced Setting Tools.
    Launch the Advanced Setting Tool and look for Conversation - Reply-to-All Warning and follow the instructions in the description for a full understanding on how this works feature can be enabled/disabled.
    Defect: CSCsi01131
    5) Customer's experiencing issues with cross-server transfers to VPIM, Bridge or AMIS subscribers under the conditions listed below should consider enabling this functionality:
    - Cisco Unity A and Cisco Unity B are two servers in the same directory and dialing domain.
    - Cisco Unity A has a VPIM (or Bridge or AMIS) Delivery Location configured for remote location X.
    - Cisco Unity A has a VPIM (or Bridge or AMIS) Subscriber (SubExt) associated with the Delivery Location.
    - Cisco Unity B, on the SA Dialing Domain page, "Cross-server transfer: Pass control to the called subscriber's Cisco Unity server" is enabled.
    In these conditions, if a caller calls Cisco Unity B and enters the id of SubExt, Cisco Unity B will prompt "One moment please", then immediately "You cannot be transferred now" and the caller will be returned to the previous conversation state.
    Upgrade to the latest version of the Advanced Setting Tools.
    Launch the Advanced Setting Tool and look for Networking - Cross-server Transfer Behavior for External Subscribers and follow the instructions in the description for a full understanding on how this works feature can be enabled/disabled.
    Defect: CSCsh56194
    6) Customers wishing to set the pre-pended and post-pended digits to any extension that a caller may dial while listening to the greeting for a Call Handler or Subscriber shall need to upgrade to the latest version of the Bulk Edit Utility.
    Launch the Bulk Edit Utility and perform topic search in the Help file for instructions on how to set the pre-pend and post-pend digits for Callhandlers and Subscribers.
    Defect: CSCse16249
    Uninstall Instructions
    On the Cisco Unity server console browse to the X:\CommServer\EngineeringSpecialBackup\ folder
    Search for the folder called CU4.2(1)_ES173
    Double click the Restore.bat file and follow the instructions
    Once the un-install completes reboot the Cisco Unity server
    Resolved Defects
    All defects listed below are included in this ES
    Fixes introduced in CU4.2(1)_ES173
    CSCsf27378
    CSCsf27378 - Media Master fails to load with "not found" errors in PCA
    CSCtc24189
    CSCtc24189 - HTTP TRAP - CPCA TRaP record does not work
    CSCsv30015
    CSCsv30015 - Unity failing to connect to SQL causing Unity to stop working as expected
    CSCsx94938
    CSCsx94938 - Recording New Greetings causes a file lock condition
    CSCta71728
    CSCta71728 - Issue with ActiveX controls shipped with Unity PCA
    CSCsz17586
    CSCsz17586 - Unity Inbox timestamp incorrect for some time zones
    CSCtc11035
    CSCtc11035 - DST change for Western Australia
    Fixes introduced in CU4.2(1)_ES172
    CSCsz19418
    CSCsz19418 - modify exclusion pattern so . (period) is allowed
    CSCsi74619
    CSCsi74619 - Conv - Empty-body TTS message can cause AV
    CSCsy10773
    CSCsy10773 - Intermittent License Corruption on double-byte Unity systems
    Fixes introduced in CU4.2(1)_ES171
    CSCsq76448
    CSCsq76448 - primary active but ports unregistered after reboot when sec. offline
    CSCsx67429
    CSCsx67429 - modify exclusion pattern so _ (underscore) is allowed with Exchange
    CSCsx95506
    CSCsx95506 - Remove feedback link from CPCA and SA
    Fixes introduced in CU4.2(1)_ES170
    CSCsx20874
    CSCsx20874 - Double-free in Event Log class can cause heap corruption, crash
    Fixes introduced in CU4.2(1)_ES169
    CSCsx20874
    CSCsx20874 - Double-free in Event Log class can cause heap corruption, crash
    Fixes introduced in CU4.2(1)_ES168
    Fixes introduced in CU4.2(1)_ES167
    CSCsv54175
    CSCsv54175 - Unity has IP Port conflicts with DNS after MS08-037 installed.
    CSCsw73149
    CSCsw73149 - Unity not starting Unexpected result in CAvLic::QueryS. Unspecified error
    Fixes introduced in CU4.2(1)_ES166
    CSCsv37908
    CSCsv37908 - If Interview Handler Question Skipped, Unity States Message Has No Audio
    CSCsv10048
    CSCsv10048 - DOM: Unity does not keep BusinessTelephoneNumber in sync
    CSCsv93549
    CSCsv93549 - Failover: FCW can fail if run after certain ESs applied
    Fixes introduced in CU4.2(1)_ES165
    CSCsm80598
    CSCsm80598 - TdsProxy fails due to corrupted Performance Counter Registry
    CSCso96540
    CSCso96540 - Unity should write eventlog warning when MAPI stalls
    CSCsd89417
    CSCsd89417 - SA does not create a MWI device correctly in SQL
    CSCsw19755
    CSCsw19755 - Port MWI improvements, fixes, diags to 4.2 from 5.0 and 7.0
    CSCsj35854
    CSCsj35854 - AvWm - Request to port MAPI function diags
    CSCsl48610
    CSCsl48610 - Unity sends port 0 in SDP information
    CSCsw25257
    CSCsw25257 - Unity AD sync - offer setting to disable sync'ing Scope DL's
    Fixes introduced in CU4.2(1)_ES164
    CSCsh04473
    CSCsh04473 - SA: Administrative Access report is empty
    Fixes introduced in CU4.2(1)_ES163
    CSCsv24693
    CSCsv24693 - Missing stored procedures after running scripts in UnitydbEx
    Fixes introduced in CU4.2(1)_ES162
    CSCsr86345
    CSCsr86345 - SA>Primary Location page is vulnerable to Cross Site Scripting
    Fixes introduced in CU4.2(1)_ES161
    CSCsr86971
    CSCsr86971 - Anonymous Auth Logon page counts against the session count
    CSCsr86943
    CSCsr86943 - Authentication bypass w/ anonymous auth
    Fixes introduced in CU4.2(1)_ES160
    CSCsr91797
    CSCsr91797 - AvLic diagnostics don't show Unity location being processed
    Fixes introduced in CU4.2(1)_ES159
    CSCsq80836
    CSCsq80836 - AvDSAD: Syncing of ScopeDls causes performance problems.
    Fixes introduced in CU4.2(1)_ES158
    CSCsm46139
    CSCsm46139 - CUOM voicemail test fails to deliver msg to inbox
    CSCso28123
    CSCso28123 - Unity repeats option to record message
    Fixes introduced in CU4.2(1)_ES157
    CSCse87865
    CSCse87865 - Change greeting to CUBI subscriber will change all others to default
    Fixes introduced in CU4.2(1)_ES155
    CSCso69772
    CSCso69772 - When sending message, if hang up after continuing, is not delivered
    Fixes introduced in CU4.2(1)_ES153
    CSCsm27607
    CSCsm27607 - JPN: Message Locator cannot search messages
    CSCsm09325
    CSCsm09325 - Unnecessary Drafts folder in unexpected language is created in Outlook
    CSCsd26042
    CSCsd26042 - Realspeak engine buffer overflow results in email TTS failure
    Fixes introduced in CU4.2(1)_ES152
    CSCsm90314
    CSCsm90314 - Dom: message notification re-sent on MWI Resync
    Fixes introduced in CU4.2(1)_ES150
    CSCsm97318
    CSCsm97318 - ReportDb_log.ldf or TempLog.ldf fill disk, may cause failsafe
    Fixes introduced in CU4.2(1)_ES149
    CSCsm82003
    CSCsm82003 - Streamsweeper logic deletes DB reference when it shouldn't
    Fixes introduced in CU4.2(1)_ES148
    CSCsi22389
    CSCsi22389 - Virtual Bytes / Fragmentation in AvCsMgr
    Fixes introduced in CU4.2(1)_ES147
    CSCsm17318
    CSCsm17318 - Unity can't set Continue adding names after each addressee from Web SA
    Fixes introduced in CU4.2(1)_ES146
    CSCsm32946
    CSCsm32946 - DST Australia Unity: Update for Unity
    Fixes introduced in CU4.2(1)_ES145
    CSCsg90913
    CSCsg90913 - Inconsistent subject line on subscriber to subscriber message
    CSCsk56884
    CSCsk56884 - Subscriber sign in should respect system first & inter digit dtmf delays
    Fixes introduced in CU4.2(1)_ES144
    CSCsm10385
    CSCsm10385 - MWI Refresh/resync turns MWI Off for New Urgent Domino Msg
    Fixes introduced in CU4.2(1)_ES143
    Fixes introduced in CU4.2(1)_ES142
    CSCsl79289
    CSCsl79289 - MWI lengthy after Exchange Cluster Failover
    Fixes introduced in CU4.2(1)_ES140
    CSCsl59482
    CSCsl59482 - VMO reports errors when form is published by not locally installed
    Fixes introduced in CU4.2(1)_ES139
    CSCsk79469
    CSCsk79469 - DST: Venezuela
    Fixes introduced in CU4.2(1)_ES137
    CSCsl56254
    CSCsl56254 - GC total resync should sync typically most important objects first
    Fixes introduced in CU4.2(1)_ES135
    CSCdx12345
    CSCdx12345
    Fixes introduced in CU4.2(1)_ES134
    Fixes introduced in CU4.2(1)_ES133
    CSCsh9258
    CSCsh9258
    CSCsf2633
    CSCsf2633
    CSCse7788
    CSCse7788
    CSCsg0314
    CSCsg0314
    Fixes introduced in CU4.2(1)_ES132
    CSCsl10496
    CSCsl10496 - Conversation Exception can cause Unity to ring-no-answer (RNA)
    CSCsk88930
    CSCsk88930 - Duplicate Alias can cause system to become unresponsive
    Fixes introduced in CU4.2(1)_ES131
    CSCsh61500
    CSCsh61500 - Can't forward Domino msgs without an intro via TUI with streamlined conv
    Fixes introduced in CU4.2(1)_ES130
    Fixes introduced in CU4.2(1)_ES129
    CSCsi43057
    CSCsi43057 - Heap Corruption in Miu during ASR cleanup
    CSCsk67827
    CSCsk67827 - MWI's may fail for PIMG integrations greater than the first integration.
    Fixes introduced in CU4.2(1)_ES127
    CSCsd16651
    CSCsd16651 - When invalid password entered at known extension, do not prompt for ID
    Fixes introduced in CU4.2(1)_ES126
    CSCsk08880
    CSCsk08880 - SA: SA use causes memory spikes/leak in AvCsMgr process
    Fixes introduced in CU4.2(1)_ES125
    CSCsk08880
    CSCsk08880 - SA: SA use causes memory spikes/leak in AvCsMgr process
    Fixes introduced in CU4.2(1)_ES123
    CSCsj76543
    CSCsj76543 - No audio if SIP call not cleared correctly, UDP port re-used
    Fixes introduced in CU4.2(1)_ES122
    CSCsd93217
    CSCsd93217 - Cross box login SIP not functioning
    Fixes introduced in CU4.2(1)_ES121
    CSCsj53656
    CSCsj53656 - New Call Routing Rules Should be disabled by default
    CSCsh15836
    CSCsh15836 - Unity 4.1.1 multiple admin adding call routing rules get mixed
    CSCsc8690
    CSCsc8690
    CSCsi1374
    CSCsi1374
    CSCsg4933
    CSCsg4933
    Fixes introduced in CU4.2(1)_ES120
    CSCsc51996
    CSCsc51996 - DInterop-Interop subs on member servers not deleted from Global sub tbl
    CSCsf10680
    CSCsf10680 - DOM: deleted Domino users are not removed from GlobalSubscriber table
    Fixes introduced in CU4.2(1)_ES119
    CSCsj80282
    CSCsj80282 - User name with Apostrophe will generate error
    Fixes introduced in CU4.2(1)_ES118
    CSCsj81527
    CSCsj81527 - Unity Inbox: time stamp adjustment not valid for DST change in 2007 NZ
    CSCsh35828
    CSCsh35828 - Unity Inbox: time stamp adjustment not valid for DST change in 2007
    Fixes introduced in CU4.2(1)_ES117
    CSCse77587
    CSCse77587 - TMP files in Unity Message Store account's temp folder fill drive
    Fixes introduced in CU4.2(1)_ES116
    Fixes introduced in CU4.2(1)_ES115
    Fixes introduced in CU4.2(1)_ES114
    Fixes introduced in CU4.2(1)_ES113
    Fixes introduced in CU4.2(1)_ES112
    CSCsj57251
    CSCsj57251 - Errors during Play Speed Adj with g.711 to g.729a conversion
    Fixes introduced in CU4.2(1)_ES111
    CSCsi73888
    CSCsi73888 - PCA Unity4.2.1- UK language reverse day with month in Alternate Greeting
    Fixes introduced in CU4.2(1)_ES110
    CSCsd39975
    CSCsd39975 - PCA cannot read or write to database when JDBC connections are refused
    Fixes introduced in CU4.2(1)_ES109
    CSCsi76164
    CSCsi76164 - DOM: Msg sent to a sub even if deleted from reply to all recipient list
    Fixes introduced in CU4.2(1)_ES108
    CSCsj16707
    CSCsj16707 - Crossbox showing event log warnings on caller disconnect
    CSCsj03459
    CSCsj03459 - Streamlined Conversations are inconsistent
    Fixes introduced in CU4.2(1)_ES107
    CSCsg76524
    CSCsg76524 - BusinessLogicManagerSvr.dll violates DLLMain rules and causes deadlock
    Fixes introduced in CU4.2(1)_ES106
    Fixes introduced in CU4.2(1)_ES105
    Fixes introduced in CU4.2(1)_ES104
    CSCsi95296
    CSCsi95296 - Optional Conversion Help (Zero for Help) is not functioning
    Fixes introduced in CU4.2(1)_ES103
    CSCsi88008
    CSCsi88008 - AvConcCVMENU006.wav causes call to terminate prematurely
    Fixes introduced in CU4.2(1)_ES102
    Fixes introduced in CU4.2(1)_ES101
    CSCsi98311
    CSCsi98311 - PIMG: Notifier should disable port when PIMG unavailable
    Fixes introduced in CU4.2(1)_ES100
    Fixes introduced in CU4.2(1)_ES99
    CSCsi77374
    CSCsi77374 - Unity Mobile Messaging Cannot Handle Spaces
    Fixes introduced in CU4.2(1)_ES98
    CSCsd46384
    CSCsd46384 - NodeMgr gives error in Eventlog: DeleteFile() fails with 80070020
    Fixes introduced in CU4.2(1)_ES97
    CSCsi85034
    CSCsi85034 - Extension remapping fails for calling # with SIP Fwd'd calls
    Fixes introduced in CU4.2(1)_ES96
    Fixes introduced in CU4.2(1)_ES95
    CSCsi64012
    CSCsi64012 - FCW fails to verify SQL is installed with WS03 3SP2
    Fixes introduced in CU4.2(1)_ES94
    CSCsi86913
    CSCsi86913 - Crossbox: No configurable timeout for digits received during transfer
    Fixes introduced in CU4.2(1)_ES93
    CSCsi82851
    CSCsi82851 - Crossbox: transfer fails with Handoff Response = ##
    Fixes introduced in CU4.2(1)_ES92
    Fixes introduced in CU4.2(1)_ES91
    CSCsh94992
    CSCsh94992 - Domino NDN causes Unity crash
    Fixes introduced in CU4.2(1)_ES89
    CSCsi69607
    CSCsi69607 - MIU fails to initialize TTS on Win2003 SP2.
    Fixes introduced in CU4.2(1)_ES88
    CSCsd76986
    CSCsd76986 - Unity MTA Counter Do not Increment in Performance Monitor
    Fixes introduced in CU4.2(1)_ES87
    Fixes introduced in CU4.2(1)_ES86
    CSCsg49334
    CSCsg49334 - License Pooling does not work between Unity 4x and 5x versions.
    Fixes introduced in CU4.2(1)_ES85
    CSCsi56850
    CSCsi56850 - Crash in AvCsMgr while loading Event Log
    Fixes introduced in CU4.2(1)_ES84
    CSCsg64120
    CSCsg64120 - Unity MWI resync performance needs improvement
    Fixes introduced in CU4.2(1)_ES83
    Fixes introduced in CU4.2(1)_ES82
    CSCsd75873
    CSCsd75873 - Miu exception under load referencing MiuCall without lock
    CSCsd75912
    CSCsd75912 - AvWav errors during 144 port load
    CSCsi16038
    CSCsi16038 - Heap Corruption in UnitySipStack.dll
    CSCsi19521
    CSCsi19521 - Unity 4.2ES - Allow 144 ports
    Fixes introduced in CU4.2(1)_ES81
    CSCsi13742
    CSCsi13742 - Exception with variant holding a date
    Fixes introduced in CU4.2(1)_ES80
    CSCsi16038
    CSCsi16038 - Heap Corruption in UnitySipStack.dll
    Fixes introduced in CU4.2(1)_ES79
    CSCsi02306
    CSCsi02306 - ACN should follow the active transfer rule
    CSCsi01131
    CSCsi01131 - Unity should prevent occurrences of accidental reply-all to PDLs
    CSCsi01116
    CSCsi01116 - sub restricted from sending to PDLs can still reply-all to PDLs
    CSCsf14610
    CSCsf14610 - Reply-To-All to a large number of recipients can cause delays..
    CSCsg52066
    CSCsg52066 - Subscriber not able to toggle between Standard and Alternate greeting
    Fixes introduced in CU4.2(1)_ES78
    CSCsh35894
    CSCsh35894 - MWI doesn't work for VPT added Unity subscribers
    Fixes introduced in CU4.2(1)_ES77
    CSCsi04112

  • Install to external drive: good or bad idea

    I have an iMac that is currently on 10.5.5. However, it was originally a Tiger install. I performed an update install to 10.5.6 and while it runs, I have stability issues that came with the Tiger -> Leopard update that I know I can eliminate by doing a clean install.
    Of course, the problem with a clean install is that the total execution time is very lengthy (from install to last app license re-registered) and my workstation is DOA (or nearly so) until completion. And then, there's always the odd detail I forgot about that I have to research to find the answer.
    So, why can't or shouldn't I do the following, or how to make it better?
    1) Do a clean install to an external drive (I have a 500 GB USB drive I can use) Leave the internal drive intact until step #4.
    2) Install the OS, apps and utilities until it matches my current machine.
    3) Once ready, back up the internal drive to the external drive as a DMG. (BTW: there will be another time machine BU on another machine on the network -- so there will be redundancy.)
    4) Do a secure 7-pass erase of the internal hard disk (this performs hardware-managed low-level sector checks, turning off sectors that error on read/write)
    5) Use Carbon Copy Cloner to copy the external data to the internal boot disk
    6) Copy my documents from the backup to the new user folder.
    7) Viola! Reinstallation complete but I can access my data at nearly any time (latency depends on current task) if I must (except during #4)
    Where's the fly in this ointment?
    TIA!

    However, is there a way of achieving zero-ing out defective sectors, like SpinRite, <http://www.grc.com/sr/spinrite.htm> without my having to remove the hard disk?
    AFAIK, SpinRite does not actually "zero out" defective sectors in modern IDE hard drives. To better understand what it does (& in general the link between analog & digital data reading mechanisms in magnetic media), look beyond the brochures & study the “What's Under The Hood” technical note at http://www.grc.com/files/technote.pdf, especially the "Surface Analysis" section beginning on page 9.
    SpinRite's makers want you to believe that "weak" sectors are something to be very concerned about, in effect that reputable drive makers design their modern high density drives (ones several generations beyond those using MFM) to regularly rely on these 'defective' sectors to boost capacity, & that only SpinRite's technology will map them out before they cause data loss. This is a dubious idea at best. The techniques used in SpinRite's surface analysis are essentially the same ones modern ATA drives use to monitor for "grown defects" -- except that modern ATA drives contain their own highly capable, purpose-designed proprietary hardware & dedicated operating systems that SpinRite can access only indirectly through clever use of standardized extensions to the ATA command set to do what the drive does anyway.
    This is not to say that the product is without merit. It is primarily purposed as a data recovery tool, & for this the extended, low level statistical analysis of the 'raw' analog data from unreliable sectors is a powerful (if not unique to this product) method of data recovery.
    There is also some merit to the idea of proactive early detection of unreliable sectors that if used for data storage would eventually require the drive to struggle & perhaps to fail to get 'clean' data from them. (I believe this is what you mean by "zero-ing out defective sectors," just in more technically precise terms.) However, be aware that drives already do this, just with actual data instead of specially designed signals, & in general this is enough to detect sectors that are going bad before the data becomes unrecoverable, at which point the drive moves the data to another sector & maps out the first one to prevent its future use.
    In real world terms, these unrecoverable 'hard" errors due to grown defects are very rare in healthy drives, only becoming problematic in drives that are dying, typically because of head crashes, exceeding operating or storage temperature limits, or other traumatic events that affect the magnetic media layer. So something like SpinRite's surface scan is most useful for extending the life of a drive that has already become unreliable or for prescreening drives for gross manufacturing defects. Since the first use makes little economic sense in these days of cheap hard drives & the second use is potentially superfluous because gross defects would likely be quickly detected anyway, users must judge for themselves if using the product for this is worth it.
    (The same considerations apply for deciding if or when the frequently seen user advice to 'zero out the drive' as part of preparing it for use accomplishes anything of real worth or not.)
    Finally, getting back to the idea of moving the drive to a PC to run SpinRite & why I think it doesn't actually "zero out" defective sectors, I can think of no way it can force the drive to actually map out a sector unless the drive itself determines it should do so. This leaves the alternative of marking the sector in use in the file system's directory structures, which in effect would accomplish the same purpose, but with one important exception: its effectiveness is dependent on the file system remaining in place on the drive. IOW, if a user changed the file system of the volume or changed the partition scheme, the file system metadata marking the sector as in use would be lost, & SpinRite's surface scan would have to be done again after these changes to get it back.
    I want to make it clear that I am not certain that this alternative, file system based method of achieving what Spinrite claims it can do is actually how it works, but I can find nothing in the product's documentation that contradicts or conflicts with it, nor am I aware of any standard extension to the ATA command set that would allow SpinRite to directly set the grown defect list. If someone has info that shows I'm wrong, please post it. I have no problem abandoning theories that don't pan out.
    Message was edited by: R C-R

  • Create new file system

    When i am trying to create new filesystem with #newfs /dev/rdsk/c0t0d0s4 getting the error message
    device busy ,
    please help me what to do

    The message "device busy" means what it says. Since newfs trashes any data on the device you specify, it is a good thing that this check is made. A typo could a major loss of data without such a safeguard. First, check that you have entered the device name correctly. If it is correct, you can run the format command and select the device in queustion. The format command should report which slices (that is, partitions) on the device are busy and for what. For example:
    # format
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
    0. c0t0d0 <DEFAULT cyl 38307 alt 2 hd 16 sec 255>
    /pci@1f,0/pci@1,1/ide@3/dad@0,0
    Specify disk (enter its number): 0
    selecting c0t0d0
    [disk formatted, no defect list found]
    Warning: Current Disk has mounted partitions.
    /dev/dsk/c0t0d0s0 is in use for live upgrade /. Please see ludelete(1M).
    /dev/dsk/c0t0d0s1 is currently used by swap. Please see swap(1M).
    /dev/dsk/c0t0d0s4 is in use for live upgrade /var. Please see ludelete(1M).
    /dev/dsk/c0t0d0s5 is part of active ZFS pool z. Please see zpool(1M).
    /dev/dsk/c0t0d0s6 is currently mounted on /. Please see umount(1M).
    /dev/dsk/c0t0d0s7 is currently mounted on /var. Please see umount(1M).
    (the menu appears here)
    As you can see, this disk has several slices (partitions) in use for various purposes. This command should give you the information you need. This is the most generic way I know of obtaining this information; otherwise, you'd have to search for the device using commands like df, mount, swap, metastat, metadb, etc.

  • Over 40 crashes since yesterday; almost no tolerance for heat

    I have been running a MacBook Pro for about three years now, and have been plagued with crashes for a long time. I can hardly use it now. Seems to be extremely heat sensitive. I have SMC Fan Control running, as well as sitting it on a cooling stand with two fans. It will crash if the temp rises above about 50 or 55 degrees, and then will not restart til it cools back down. Means I often cannot restart for 10-30 minutes.
    Sometimes it crashes on the startup blue screen, sometimes it gets all the way to the login screen but then freezes before I can enter my password. Other times I login but then it crashes before loading. Sometimes I can get to the apps but then it crashes when I load Apple Mail or Firefox or anything. Then, seemingly for no reason, it will just start working fine and I can run for 10 or 20 hours without a hitch, running Dreamweaver, Photoshop, Flash, and other programs without a problem.
    Any ideas what is happening here? I sometimes get multicolored streaks across the screen. Other times it seems to "tear" or distort blocks of the screen, or tint a block some odd color, which then returns to normal when that part of the screen refreshes or moves.
    I have seen several posts saying that the video cards were defective, but mine is a Radeon X1600, and I don't think they were included in the defective lists.
    I am also in a remote area, with no Apple stores within several days' drive, and cannot afford to lose my Mac for a few weeks while it is sent away for repairs. Anything anyone can suggest would be a great help!
    Thanks

    Thanks very much Allan for sticking with me on this. I think I'm really coming to understand some things here. Would really appreciate one more reply if you could...
    1) I don't think the mdworker is the problem. Yes it runs heavily when nothing else is on, but if I run apps, it drops down to a very low level. It only seems to take a lot of the CPU when nothing else is running, and that seems logical to me. Just using available resources. So technically, I don't think that that mdworker is my problem.
    2) The system runs flawlessly in safe mode. No heat issues at all. Unfortunately though, it also lacks wireless, audio, video, and other operations that safe mode discontinues. So it's not a suitable working environment. It does though suggest that the issue is something that works in normal mode, but not in safe mode. The big question, of course, is what. I removed everything from the startupItems folders, and also shut down anything I could find that affects normal startup, but the problem is still there in normal mode. It will almost never even let me get to the user sign-in screen; just crashes on the blue screen.
    3) I found this thread from a few months ago, and it includes a screen shot that looks a lot like the trouble I'm having. His problem was a bad video card. Makes me wonder. Here's that thread:
    http://discussions.apple.com/thread.jspa?messageID=8487954&#8487954
    So with all that said, I'll phone Apple tech support tomorrow to see if I can get them to tackle that mother board, or help me track down the issue. I'm well over warranty, but something has to be done here. This Mac is pretty much dead in normal mode.
    Thanks again for your help. Comments Allan or anyone?

Maybe you are looking for