WAE Disk Status "Not Up To Date"

After an Upgrade Image to 4.1.3b.9, i got this command output:
NO-HOSTNAME#show disks details
Physical disk information:
disk00: Present WD-WCANY3489733 (h02 c00 i00 l00 - Int DAS-SATA)
238472MB(232.9GB)
disk01: Present WD-WCANY3489714 (h02 c00 i01 l00 - Int DAS-SATA)
238472MB(232.9GB)
Mounted file systems:
MOUNT POINT TYPE DEVICE SIZE INUSE FREE USE%
/sw internal /dev/md0 991MB 912MB 79MB 92%
/swstore internal /dev/md1 991MB 459MB 532MB 46%
/state internal /dev/md2 5951MB 168MB 5783MB 2%
/local/local1 SYSFS /dev/md4 11903MB 130MB 11773MB 1%
.../local1/spool PRINTSPOOL /dev/data1/spool 991MB 32MB 959MB 3%
/obj1 CONTENT /dev/data1/obj 101177MB 128MB 101049MB 0%
/dre1 CONTENT /dev/data1/dre 79354MB 128MB 79226MB 0%
/ackq1 internal /dev/data1/ackq 1189MB 32MB 1157MB 2%
/plz1 internal /dev/data1/plz 2379MB 65MB 2314MB 2%
Software RAID devices:
DEVICE NAME TYPE STATUS PHYSICAL DEVICES AND STATUS
/dev/md0 RAID-1 NORMAL OPERATION disk00/00[GOOD] disk01/00[GOOD]
/dev/md1 RAID-1 NORMAL OPERATION disk00/01[GOOD] disk01/01[GOOD]
/dev/md2 RAID-1 REBUILDING disk00/02[GOOD] disk01/02[!!NOT U
P TO DATE!!]
/dev/md3 RAID-1 REBUILDING disk00/03[GOOD] disk01/03[!!NOT U
P TO DATE!!]
/dev/md4 RAID-1 REBUILDING disk00/04[GOOD] disk01/04[!!NOT U
P TO DATE!!]
/dev/md5 RAID-1 REBUILDING disk00/05[GOOD] disk01/05[!!NOT U
P TO DATE!!]
*** NOTE ***
One or more RAID constituent disk partitions appear to be abnormal.
This could be because of
problem in drive's partition(s) and it is being rebuilt
Possible I/O errors on a disk drive
Please run "show alarms critical detail support"
to check any critical disk errors.
RAID-1 volumes will continue to operate on the remaining disk drive.
Please refer to the product documentation for further
information on how to handle this situation.
There are not alarms about disks...
I powered-on the appliances almost 20 mins ago... and this still continuous saying that . Is it normal ?
Best Regards,
Bruno Petrónio

ARGGGGGGGG....
Ensuring a Successful RAID Pair Rebuild
RAID pairs will rebuild on the next reboot after you use the restore factory-default command, replace or add a hard disk drive, delete disk partitions, or reinstall WAAS from the booted recovery CD-ROM.
Caution You must ensure that all RAID pairs are done rebuilding before you reboot your WAE device. If you reboot while the device is rebuilding, you risk corrupting the file system.
To view the status of the drives and check if the RAID pairs are in "NORMAL OPERATION" or in "REBUILDING" status, use the show disk details command in EXEC mode. When you see that RAID is rebuilding, you must let it complete that rebuild process. This rebuild process may take several hours. **

Similar Messages

  • Partititon1,2,3 in  group ODS,FAC status not change after data redistribute

    Hello,
    first thanks for your help. By now the db2 data redistribute has been sucessful. but another issue occurs , could you give me some suggestion?
    1. run Tcode dbacockpit-->db2 for linux, unix, and windows database > configuration>database partiton group
    i found the stutus in db partion group NGRP_FAC_AB7 and NGRP_ODS_AB7 and partion 1,2.3. is partion not in partitioning map containers created. I know if we want to change the status from this to partion in partioning map status , we should do a redistribute.
    i have made a redistribute action like this
    1. double click what i want to distribute
    2. select the relevant partition , for example partition 0001
    3 click the execute immediatelly button .
    when i finished , the status is not changed . so i change the redistribute log located in /db2/db2ab7/sqllib/redist/ AB7.NGRP_FACT_AB7.2008022808582 .
    the log message is
    Data Redistribution cannot be continued.
    Error: Redistribution failed with SQLCODE=-6047 (rc=-2145779603).
    the SQL 6047 detail information is like the following. I don't know what happens.
    it's a SAP bug just like the previous issue ? Could you give me some suggestion ? Thanks
    db2 => ? sql6047
    SQL6047N Database partition group cannot be redistributed
    because table "<name>" does not have a partitioning
    key.
    Explanation:
    At least one table in the single-node database partition does not
    have a partitioning key. All tables in the single-node database
    must have a partitioning key before the database partition group
    can be redistributed to a multiple-node database partition
    group.
    The operation was not performed.
    User Response:
    Use the ALTER TABLE command to specify partitioning keys for
    tables that do not have one. Then try the request again

    Before redistribution, do your tables reside on only one partition? Does the error message you get list the table or tables that do not have a partitioning key?
    All fact tables, ODS tables and PSA tables are created with a partitioning key in a SAP BI system. However, in the FACT and ODS tablespace, there are a few BI management tables (name starting with 'RS') that do not get a partitioning key by default if created in a tablespace on only one partition. The BI data distribution wizard in the DBA Cockpit takes care of some of these tables, for example RSDMFACTAB and RSDMODSTAB. Maybe there are some additional ones.
    Please list the names of the tables without partitioning key. If the error message does not contain them, you can get them with the following SQL statement:
    select varchar(tabname,30)
    from syscat.tables a
    where tbspace='<your_tablespace>'
      and not exists (select partkeyseq from syscat.columns b
                             where a.tabschema=b.tabschema and a.tabname=b.tabname
                                      and b.partkeyseq > 0)
    Brigitte

  • I have received an error message from an attached USB hard drive (not Time Capsule) stating "Disk Name" cannot be repaired. Back up your data and reformat. I opened the Disk Utility in an attempt to repair the disk but am advised that the disk "could not

    I have received an error message relating to an attached USB hard drive (not a back up and not Time Capsule) advising that "disk name" cannot be repaired. Back up your data and reformat. When I attempted to verify the disk with Disk Utility, I was advised that the disk could not be unmounted. What can I do to repair the disk?
    Write Status is Read/Write
    SMART Status is Not Supported
    Partition Map Scheme is Master Boot Record
    HELP!
    timothy7712

    You need something stronger, such as DiskWarrior, TechTools Pro, or Data Rescue.

  • Status 51 material document data and po data do not match(vendor)

    i am using we19 to try an inbound idoc mbgmcr(receipt for po)
    i put in gm_code 01
    movement indicator B(goods receipt for po)
    vendor 3815
    PO 4500015241
    PO Order Item 00030
    Movement type 101
    qty in unit of entry  1
    iso code unit of measurement pc
    on the po screen i see the po item and qty to be delivered is 75
    when i run the inbound idoc i get
    status 51 material document data and po data do not match(vendor) but as i say on the po inquiry screen i see the po vendor item with 75 to be delivered
    what am i missing????????????????

    thank you
    i put in the leading zeros and got rid of that problem
    now i am getting status 51
    posting only possible in 2004/07 and 2004/06
    but in the posting date i use 07/02/2004  i have tried several dates in the period but get the same error
    any ideas?
    thanks you

  • External drive not showing up - which disk initialization method will NOT erase the data on that external hard drive?

    Hi,
    as thousands of other users, my WD Passport drive worked like a charm until yesterday and now it wont show on any computer, but does show in the Disk management and when plugged in , the Disk Management offers two ways of initialization : MBR and GPT
    i dont understand any of that and want to know if any of those two methods will make the disk initialize wITHOUT loosing the data on the drive?
    i looked on so many forums and some people say that it will and others that it will not erase the data. 
    can you please tell me what is correct?? also a suggestion is to add some more wording to that initializaiton dialog box so that we can know what initialization does and doesnt
    thank you so much
    t 

    Try connecting it to a different computer to see if you can access the data, under no circumstances should you Initialize the drive as all existing data will be lost.
    If you still can't access your files, then remove the drive from the case and connect it via an extra SATA cable and power connector (you usually need a desktop PC in order to do this if the drive is a 3.5 inch model, a 2.5in drive will fit into a laptop
    if you have a spare slot).
    J W Stuart: http://www.pagestart.com
    Never be afraid to ask. This forum has some of the best people in the world available to help.

  • When insert my lexar USB flash drive I get the message that the disk was not readable by this computer.  It has worked previous to this and I do not want to lose the data by reformatting the drive.  How can I reformat this drive and not lose my data?

    When insert my lexar USB flash drive I get the message that the disk was not readable by this computer.  It has worked previous to this and I do not want to lose the data by reformatting the drive.  How can I reformat this drive and not lose my data?

    You can't reformat it and not wipe everything on it.
    Have you tried a different USB port?
    Only other option, back it up on a different computer.

  • I unplugged a USB data device without ejecting it properly via 'Finder'.  Now whenever I plug in the device I received an error message stating that the 'disk was not ejected properly

    Now when I plug in the device I receive an error message stating that the disk was not ejected properly & that next time I connect the 'disk', MAC OS X will attempt to repair any damage to the information on the disk.
    It has not repaired.
    The data I am trying to import is photos & even when I change to a different SD card I receive the same message.
    I am a recent convert from Windows and am new to the MAC way of things.  

    You can repair the SD card using Disk Utility.
    I suggest you copy the photos from your SD card, if you haven't done so already, before using Disk Utility to repair your SD card.

  • Mountain lion has killed my mac book pro. After downloading and trying to install, I am stuck in a loop of "not enough room to install on this disk" and not being able to access the old disk's data to open up space.

    Mountain lion has killed my mac book pro. After downloading and trying to install, I am stuck in a loop of "not enough room to install on this disk" and not being able to access the old disk's data to open up space.

    Nope. It just opened the installer and stayed in the same loop.
    It tells me to choose a startup disk but the only option is the HD which it will not use because it says it cannot gather enough information.
    Eveything was working fine until the mountain lion failed install.

  • Window pops up saying can not complete request data base error, disk is full

    Window pops up saying can not complete request data base error, disk is full

    I am using the latest ID version with update and I am using a Mac running 10.9.5. This all started when I tried to make a PDF file from a pub I was working on. The application made the file but went into a spinning beach ball and I had to force quit. Now the window pops up when I open ID and also when I am working on a documents.

  • Saving data from XP (via LAN) to iMac get "The disk is not ready" on the XP

    I have Quicken 99 runing on a LAN connected XP and want to have it back up to the iMac (and subsequent time machine backups). I have mapped the path to the folder on the iMac from the XP as the Q drive so Quicken won't choke on the network connection. Start the backup, select the Q drive, get the message that "a file with the same file name in the backup directory..." (so the XP can see the mapped iMac drive), click on OK and get the subject message "The disk is not ready."
    I can access the Q drive from the XP and manually copy, create, files, but quicken chokes...
    Any help appreciated.
    Thanks,
    Chet

    Had to apply permissions to all the files... did via the following:
    To apply the same permissions to every item contained in the selected folder or disk, open the Action (gear) menu and choose “Apply to enclosed items.”

  • Moving library to external hard drive and get the error "Copying files failed. The disk could not be read from or written to"

    Hello,
    I'm moving my library to an external hard drive.
    I've made sure to use the 'Keep iTunes Media Folder Organized' option when pointing to the new library location.
    I select 'File'->'Library'->'Organize Library', I select to 'Consolidate Files', click 'OK' and get ther error message "Copying files failed. The disk could not be read from or written to".
    I've read elsewhere that there may be a corrupted file that I need to sequester somehow and perhaps add it back however I'm not certain how I can locate that file because the status window doesn't indicate which file it's attempting to transfer when the error appears.
    Any tips?
    Thank you,
    Greg H
    iTunes 10.6.3

    OK I figured it out!
    It was a dodgy file....I sorted the file folders by date, and as it turned out within the "compilations" folder there was a CD where only about half the tracks seemed to have been copied over. Could not have identified this simply from the time indicated on the finder folder sort, because there were several CDs copied over in the that same minute.
    I went back to the original itunes folder, deleted all the files from that CD in itunes, then also deleted all those files from the original disk and the target disk.
    Tried the "consolidate library" again, and it completed nicely. 200megs of music and videos.
    Very happy to solve this problem after 3 weeks.

  • Disks do not auto-failover; must metaset take first

    Hello,
    In Solaris 10, Cluster 3.2, two node:local zone cluster.
    The SAN disks do not auto-failover when I do a switch on the resource group. Instead, to fail over, I must:
    - clrg online fails
    - manually mount the SAN disks to the node
    - clrg online success
    To fail over to other node, must
    - clrg switch [2nd node] fails with messages:
    # Dec 10 11:03:35 pluto SC[SUNW.HAStoragePlus:6,ftp4-com-rg,ftp4-data-has,hastorageplus_prenet_start]: Mount of /zones/ftp_zone/root/ftp_user_data failed: (33) mount: /zones/ftp_zone/root/ftp_user_data: Device busy
    Dec 10 11:03:35 pluto SC[SUNW.HAStoragePlus:6,ftp4-com-rg,ftp4-data-has,hastorageplus_prenet_start]: Failed to mount: /zones/ftp_zone/root/ftp_user_data in global or local zone
    - so now the rg is offine
    - [on 2nd node] metaset -s [setname] -t so 2nd node becomes owner
    - [on 2nd node] manually mount the disk
    - clrg switch to 2nd node is successful
    So appears the rg is not failing over b/c metaset is owned by one node and doesn't release them so the other node can take ownership. Do I need to do a metaset -r [release] or metaset -A enable ??
    vfstab has been updated:
    /dev/md/ftpbin/dsk/d110 /dev/md/ftpbin/rdsk/d110 /zones/ftp_zone/root/mysql_data ufs 1 no logging
    /dev/md/ftpdata/dsk/d111 /dev/md/ftpdata/rdsk/d111 /zones/ftp_zone/root/ftp_user_data ufs 1 no logging
    jupiter /etc # metaset
    Set name = ftpbin, Set number = 1
    Host Owner
    jupiter Yes
    pluto
    Driv Dbase
    d2 Yes
    Set name = ftpdata, Set number = 2
    Host Owner
    jupiter Yes
    pluto
    Driv Dbase
    d3 Yes
    Edited by: onetree on Dec 10, 2008 10:02 PM

    Ok, I found the cause. Need help finding solution.
    I verified I have patch 124918-02, which is obsoleted by 120011-14
    http://sunsolve.sun.com/search/document.do?assetkey=1-26-102546-1
    The cause is in device groups and/or metasets. Need to get rid of ftpbin group, which points to the same disks as ftpabin.
    pluto:/dev/md# ls -l
    total 14
    lrwxrwxrwx 1 root root 31 Jul 10 13:05 admin -> ../../devices/pseudo/md@0:admin
    drwxr-xr-x 2 root root 512 Aug 18 11:13 dsk
    lrwxrwxrwx 1 root root 8 Dec 10 16:13 ftpabin -> shared/3
    lrwxrwxrwx 1 root root 8 Dec 10 16:13 ftpbin -> shared/1
    lrwxrwxrwx 1 root root 8 Dec 10 16:13 ftpdata -> shared/2
    drwxr-xr-x 2 root root 512 Aug 18 11:13 rdsk
    lrwxrwxrwx 1 root root 42 Sep 25 18:17 shared -> ../../global/.devices/node@2/dev/md/shared
    pluto:/dev/md/shared# find . -ls
    7 1 drwxrwxr-x 5 root root 512 Dec 10 15:42 .
    4291 1 drwxr-xr-x 4 root root 512 Dec 3 14:01 ./1
    4292 1 drwxr-xr-x 2 root root 512 Dec 10 16:13 ./1/dsk
    4300 1 lrwxrwxrwx 1 root root 44 Dec 10 16:13 *./1/dsk/d110* -> ../../../../../devices/pseudo/md@0:1,110,blk
    4295 1 drwxr-xr-x 2 root root 512 Dec 10 16:13 ./1/rdsk
    4304 1 lrwxrwxrwx 1 root root 44 Dec 10 16:13 *./1/rdsk/d110* -> ../../../../../devices/pseudo/md@0:1,110,raw
    4298 1 drwxr-xr-x 4 root root 512 Dec 3 14:22 ./2
    4299 1 drwxr-xr-x 2 root root 512 Dec 10 16:13 ./2/dsk
    4296 1 lrwxrwxrwx 1 root root 44 Dec 10 16:13 ./2/dsk/d111 -> ../../../../../devices/pseudo/md@0:2,111,blk
    4302 1 drwxr-xr-x 2 root root 512 Dec 10 16:13 ./2/rdsk
    4310 1 lrwxrwxrwx 1 root root 44 Dec 10 16:13 ./2/rdsk/d111 -> ../../../../../devices/pseudo/md@0:2,111,raw
    4305 1 drwxr-xr-x 4 root root 512 Dec 10 15:42 ./3
    4306 1 drwxr-xr-x 2 root root 512 Dec 10 16:13 ./3/dsk
    4307 1 lrwxrwxrwx 1 root root 44 Dec 10 16:13 *./3/dsk/d110* -> ../../../../../devices/pseudo/md@0:3,110,blk
    4309 1 drwxr-xr-x 2 root root 512 Dec 10 16:13 ./3/rdsk
    4311 1 lrwxrwxrwx 1 root root 44 Dec 10 16:13 *./3/rdsk/d110* -> ../../../../../devices/pseudo/md@0:3,110,raw
    # cldg status
    Device Group Name Primary Secondary Status
    ftpbin - - Offline
    ftpdata jupiter pluto Online
    ftpabin jupiter pluto Online
    # cldg show
    Device Group Name: ftpbin
    Type: SVM
    failback: false
    Node List: pluto
    preferenced: false
    numsecondaries: 1
    diskset name: ftpbin
    pluto:/dev/md# cldg delete ftpbin
    cldg: (C795573) This operation is not allowed for Solaris Volume Manager device groups.
    cldg: (C747142) Use the metaset(1M) or metassist(1M) commands to modify or delete Solaris Volume Manager device groups.
    cldg: (C178871) Deletion of device group "ftpbin" failed.
    pluto:/dev/md# metaclear -s ftpbin
    metaclear: pluto: setname "ftpbin": no such set
    pluto:/dev/md# metaset
    Set name = ftpdata, Set number = 2
    Host Owner
    jupiter
    pluto
    Driv Dbase
    d3 Yes
    Set name = ftpabin, Set number = 3
    Host Owner
    jupiter
    pluto
    Driv Dbase
    d2 Yes
    pluto:/dev/md# metaset -s ftpbin
    metaset: pluto: setname "ftpbin": no such set
    pluto:/dev/md/shared# metaset -s ftpbin -C purge
    metaset: pluto: setname "ftpbin": no such set
    Also tried devfsadm -C and boot -r
    Ran 'metaclusterbinddevs' to recreate the device links, but no diff.
    # /usr/cluster/lib/sc/metaclusterbinddevs

  • Backups failing with error 19: the backup disk could not be resolved, or there was a problem mounting it

    Hello all,
    Doubt this issue relates to a recent and ugly issue but sharing anyways (resolved thanks to a user here: LaPastenague)
    Time Capsule won't backup if Modem (Motorola SB6121) attached
    This was on Feb 10th resolved. Few days later I upgraded to Yosemite.  Backups were working fine since.  
    Yesterday I happen to notice my last backup was 5 days ago.  I looked in the console logs and saw:
    2/25/15 3:55:06.127 PM com.apple.backupd[2777]: Attempting to mount network destination URL: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
    2/25/15 3:55:17.778 PM com.apple.backupd[2777]: NAConnectToServerSync failed with error: 2 (No such file or directory) for url: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
    2/25/15 3:55:17.792 PM com.apple.backupd[2777]: Backup failed with error 19: The backup disk could not be resolved, or there was a problem mounting it.
    2/25/15 3:57:18.808 PM com.apple.prefs.backup.remoteservice[2021]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
    I called Apple.  Their front line was clueless. He suggested resetting the TC (latest "tower" model btw") which then a backup kicked off YEAH
    But the next hour it failed
    Called Apple again, this time to Sr Advisor.  He suggested factory reset of the TC and set up again.  Also first backup worked then rest failed
    Third call to Apple useless also.  He was asking questions I didn't feel relevant.  He also was asking me to reset the TC which I told him was done 2 hours prior. He asked me to reboot which I could NOT at that time.
    I begged him to collect data to submit to engineering, which will take days to get a reply.
    So I thought I would throw this out to the community....
    TC Is NEW (replaced from last issue).  Mac is 8 months old (iMac 27"), Os is Yosemite,  TC also new (latest model)
    Thanks...

    Yosemite is problematic on two fronts.. Networking and Time Machine.. so the combo of doing both with a Time Capsule is like bugs on bugs.
    Here is my standard list.. but your problem maybe difficult to resolve.. and my suggestion is simple.. until Apple get their act together and fix TM.. buy Carbon Copy Cloner and use that for your backup. It is solid and reliable.. even better if you use USB drive plugged into the computer and do a bootable clone.. because then you have a backup that is able to be tested for full functionality 2min after the end of the backup.
    This also starts from a factory reset.. but the reason for it is to change the configuration which is much more easily handled with factory reset to begin.. the instructions are there.. because this is my standard reply.. this is not uncommon!!
    Factory reset universal
    Power off the TC.. ie pull the power cord or power off at the wall.. wait 10sec.. hold in the reset button.. be gentle.. power on again still holding in reset.. and keep holding it in for another 10sec. You may need some help as it is hard to both hold in reset and apply power. It will show success by rapidly blinking the front led. Release the reset.. and wait a couple of min for the TC to reset and come back with factory settings. If the front LED doesn’t blink rapidly you missed it and simply try again. The reset is fairly fragile in these.. press it so you feel it just click and no more.. I have seen people bend the lever or even break it. I use a toothpick as tool.
    N.B. None of your files on the hard disk of the TC are deleted.. this simply clears out the router settings of the TC.
    Setup the TC again.
    ie Start from a factory reset. No files are lost on the hard disk doing this.
    Then redo the setup from the computer with Yosemite.
    1. Use very short names.. NOT APPLE RECOMMENDED names. No spaces and pure alphanumerics.
    eg TCgen5 and TCwifi for basestation and wireless respectively.
    Even better if the issue is more wireless use TC24ghz and TC5ghz with fixed channels as this also seems to help stop the nonsense. But this can be tried in the second round.
    2. Use all passwords that also comply but can be a bit longer. ie 8-20 characters mixed case and numbers.. no non-alphanumerics.
    3. Ensure the TC always takes the same IP address.. you will need to do this on the main router using dhcp reservation.. or a bit more complex setup using static IP in the TC. But this is important.. having IP drift all over the place when Yosemite cannot remember its own name for 5 min after a reboot makes for poor networking. If the TC is main router it will not be an issue.
    4. Check your share name on the computer is not changing.. make sure it also complies with the above.. short no spaces and pure alphanumeric.. but this change will mess up your TM backup.. so be prepared to do a new full backup. Sorry.. keep this one for second round if you want to avoid a new backup.
    5. Mount the TC disk in the computer manually.
    In Finder, Go, Connect to server from the top menu,
    Type in SMB://192.168.0.254 (or whatever the TC ip is which you have now made static. As a router by default it is 10.0.1.1 and I encourage people to stick with that unless you know what you are doing).
    You can use name.. SMB://TCgen5.local where you replace TCgen5 with your TC name.. local is the default domain of the TC and doesn't change.
    However names are not so easy as IP address.. nor as reliable. At least not in Yosemite they aren't. The domain can also be an issue if you are not plugged or wireless directly to the TC.
    6. Make sure IPv6 is set to link-local only in the computer. For example wireless open the network preferences, wireless and advanced / TCP/IP.. and fix the IPv6. to link-local only.
    There is a lot more jiggery pokery you can try but the above is a good start.. if you find it still unreliable.. don't be surprised.
    You might need to do some more work on the Mac itself. eg Reset the PRAM.. has helped some people. Clean install of the OS is also helpful if you upgrade installed.
    Tell us how you go.
    Someone posted a solution.. See this thread.
    Macbook can't find Time Capsule anymore
    Start from the bottom and work up.. What I list here is good network practice changes but I have avoided Yosemites bug heaven.
    This user has had success and a few others as well.
    RáNdÓm GéÉzÁ
    Yosemite has serious DNS bug in the networking application.. here is the lets say more arcane method of fixing it by doing a network transplant from mavericks.
    http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-yo u-can-do-to-fix-it/

  • Disk Utility's "Verify Disk" does not work

    For some reason I am not able to run the "Verify Disk" option in the Disk Utility application. I open up Disk Utility, I can click on the button, and it begins. However, while it says it is verifying the disk, and the status bar appears (just shows it working, doesn't show a time remaining), it continues like this for an inordinate amount of time. Eventually, the entire computer freezes up; I can move the mouse, but nothing responds to keyboard or mouse clicks. I am forced to hold down the power button to shut-down.
    To get more information I decided to run this command in the Terminal. This is what I get:
    +mycomputername~ root# diskutil verifyVolume /+
    +Started verify/repair on volume disk0s2 Macintosh HD+
    When I press enter after typing the first line, the second line appears, and it appears but nothing else shows up. Eventually, like in Disk Utility (which makes sense), the entire computer freezes up. (I've waited hours)
    Does anyone know why this tool might not be working? I know, when using the terminal, more dialog should show what it is working on, which is why I find it strange it doesn't even get past the "Started verify" point. For example, the following is supposed to show up eventually, but doesn't:
    +Checking HFS Plus volume.+
    +Checking Extents Overflow file.+
    +Checking Catalog file.+
    etc...
    I used the command line to verify with fsck too. +(sudo fsck_hfs -l /dev/disk0s2)+ This worked. From what I can tell, the problems it generated were benign.
    On a different note, the reason I want to do this is because I am trying to use Bootcamp Assistant 1.4 Beta to create an XP Partition (after I had to get rid of it due to a virus), but it gets stuck on the "Partitioning Disk", and the status (which doesn't show remaining time) just continues to stay the same after a few hours, eventually freezing the computer in the same way the Verify Disk does. See a theme here? I'm not sure if this is related or not.
    So why does the Verify Disk tool not work for me? Anyone have any ideas? I'm hesitant to try to use the Disk Repair tool, without the Verify Disk tool working.
    Thanks for any help! Oh, and Happy New Year!
    Michael
    (Disk info, if this is useful for some reason)
    +Device Node: /dev/disk0s2+
    +Device Identifier: disk0s2+
    +Mount Point: /+
    +Volume Name: Macintosh HD+
    +File System: Journaled HFS+ +
    +Journal size 16384 k at offset 0x7d01000+
    +Owners: Enabled+
    +Partition Type: Apple_HFS+
    +Bootable: Is bootable+
    +Media Type: Generic+
    +Protocol: SATA+
    +SMART Status: Verified+
    +Total Size: 148.7 GB+
    +Free Space: 51.6 GB+
    +Read Only: No+
    +Ejectable: No+
    +Disk Number: 0+
    +Partition Number: 2+

    Thank you so much!
    For some reason that didn't cross my mind. I booted with the OSX installer disk, and used DU and the Verify Disk worked!
    Oddly enough when it finished I got an error message. Maybe that's just because the Verify encountered errors. It said:
    +First Aid failed+
    +Disk Utility stopped verifying "Macintosh HD" beause the following error was encountered: The underlying task reported failure on exit+
    Here's the results of the scan:
    +Checking Catalog file.+
    +Resereved fields in the catalog record have incorrect data+
    +Incorrect block count for file Temp File 1.tmp+
    +(It should be 4529 instead of 0)+
    +Incorret number of thread records+
    +Overlapped extent allocation (file 1815158 /Users/..)+
    +Checking Volume bitmap+
    +Volume Bit Map needs minor repair+
    +Checking volume information+
    +Invalid volume free block count+
    +(It should be 13585467 instead of 13578598)+
    +The Volume Macintosh HD needs to be repaired.+
    +Error: The underlying task reported failure on exit.+
    I'm going to repair the disk, only after I backup my data. Not sure if these problems are 'benign' or not. Maybe that will solve my Boot Camp problems, maybe not. If not, well, it's either a complete reformat of the drive, or I'll have to buy Leopard so I can get Boot Camp support.
    Thanks for your help again! So nice to see something working right on my Mac, finally
    Michael

  • Alert : Logical Disk is not online

    Hello,
       On 2 of our Red Hat Linux systems(5.10 and 5.11) with the SCOM client install we are getting the error "Alert : Logical Disk is not online", although disk and Logical Volumes seem to be in good statuses and everything in /etc/fstab
    is mounted.   For the source it is giving something like this: /tmp/HOSTNAME-20140918_092643/data which doesn't even exist on the servers.
    This is the error I see in /var/opt/microsoft/scx/log/scx.log.
    2014-10-21T23:55:42,935Z Error      [scx.core.common.pal.system.disk.statisticallogicaldiskinstance:223:6731:47407558268688] statvfs() failed for /tmp/HOSTNAME-20140923_083643/data; errno = 2
    Both servers have this version of the client: Version: 1.5.1-112 (Labeled_Build - 20140321L)
    Has anyone seen this before, and if so can you offer any assistance?
    Thanks,
    Chris.

    Hi Chris,
    This is a pretty tricky one - I've never heard or seen anything like this before.
    Going out on a limb here: Is it possible that, at one time, you configured a memory-resident drive that resided on /tmp? If you configured that at one time, but then abandoned it but didn't remove all the links to it in /dev/disk or something like that,
    I could see how we could pick that up and get confused by it.
    If that's not it, then you did mention that only two of your Red Hat systems suffer from this. What's different between these two systems and other Red Hat systems that you may have?
    If none of the above is useful, then this should probably be escalated to Microsoft Support. They can engage, look at your machine, and collect information for us (in engineering) to diagnose this.
    Thanks,
    /Jeff

Maybe you are looking for