Unmounting ASMlib driver filesystems failed

Hi,
I have tried to stop ASMlib and unload module oracleasm
#oracleasm exit
However I am receiving the error:
Unmounting ASMlib driver filesystem: failed
Unable to unmount ASMlib driver filesystem
I have running ASM instance.
My main question is:
I have read that you do not need ASMlib for ASM (it is just an optional support), so why when I want to stop it it is not possible?
Note: I have tried to do so on the system without ASM instance running - actually no grid, no DB is installed, just ASMlib, and it was ok - I could do exit without any problems (sure, ).
If someone could give me an explanation what is going on, or what am I missing in ASMlib and ASM instance relationship I appreciate it so much.
#fuser -m /dev/oracleasm --> there are many processes using it (e.g. asm_dbw0_+ASM ...), which is all right I just do not understand why it is blocking ASMlib
xxx:/home/storage # rpm -qa| grep oracl
oracle-instantclient11.2-sqlplus-11.2.0.4.0-1
oracleasm-support-2.1.8-1.SLE11
oracleasmlib-2.0.4-1.SLE11
oracleasm-kmp-default-2.0.5_3.0.82_0.7-7.39.1
oracle-instantclient11.2-basic-11.2.0.4.0-1
oracleasm-2.0.5-7.39.1
Oracle 11g
SLE 11 SP3

Hi Dude,
Thanks.
And how it is connected with the ASM instance - I mean ASMlib, why it cannot be unmounted while ASM instance is running?
I thought that ASMlib is used for device management - labeling, connecting to /dev/oracleasm so it has not 'real' efect on ASM itself. I think it is just preparing devices for AMS so this is why I do not understand why it cannot be umnounted. Like separate process helping to user/admin deal with the devices, not helping ASM itself.
I am not against ASMlib (I will try udev, but ASMlib is simplifying things - at least for me ) - I saw there are many discussion, it is not my case, just wish to understand clearly.

Similar Messages

Inicialize the Oracle ASMlib driver : [FAILED]

Can You help me , where I do mistage ? ( I red all doc about ASM - may be don't carefully)
I can test a learn more about oracle RAC ( I have two VMWARE masine with rhel4) with Oracle custerware 11.1 and oracle db software 11.1
I can configure ASM with this RAC architecture (usin ASMlib technology) , but during configuration ASMlib i get error :
rhel4 kernel 2.6.26
instaled rpm :
oracleasm-2.6.9-78.0.8.EL-2.0.5-1.el4.i686.rpm
oracleasmlib-2.0.2-1.i386.rpm
oracleasm-support-2.1.1-1.el4.i386.rpm
I did
/etc/init.d/oracleasm configure
.... user to own driver-> oracle
.... group to own driver ->
inicializing the Oracle ASMlib driver : [FAILED]
Can You help me
Thank You Brano

Hi,
The oracleasm package (2.6.9) does not correspond to the kernel version you're using (2.6.26).
Oracle only supports the 2.6.9 kernel in RHEL 4.x
Kind regards,
Serge

How to solve the issue "OEL 5.6 boot Oracle ASMLib driver: FAILED" ?

Folks,
Hello. I am installing Oracle 11gR2 RAC using 2 VMs (rac1 and rac2) whose OS are Oracle Linux 5.6 in VMPlayer.
I downloaded Oracle Linux 5.6 Media Pack for x86_64 (file name V24479-01) from https://edelivery.oracle.com/linux.
I have installed OEL 5.6 for VM rac1 and done the follows:
1) install rpm and oracleasm packages for rac1.
2) edit /etc/hosts to set up IP addresses for eth0 and eth1 for rac1 and rac2.
3) edit eth0 and eth1 for rac1 by using command [root@rac1 \]# neat
But when boot the OS, I see "initializing Oracle ASMLib driver: FAILED".
When configure Oracle ASM library driver by running the command:
[root@rac1 /]#/etc/init.d/oracleasm configure -i
Its output "initializing Oracle ASMLib driver: FAILED"
I think the reason is the OS cannot initialize Oracle ASMLib driver. My question is:
Do any folk understand how to solve the issue "OEL 5.6 boot Oracle ASMLib driver: FAILED" ?
Thanks.

Folks,
Hello. Thanks a lot for replying. OEL 5.6 comes with 2 kernels: uek and red hat
I have chosen to use red hat kernel for 64-bit. I run the following command:
[root@rac1 /]# uname -rm
Output: 2.6.18-238.el5x86_64
I have downloaded 4 files for this version of kernel from
http://www.oracle.com/technetwork/server-storage/linux/downloads/rhel5-084877.html as below:
oracleasm-2.6.18-238.el5xen-2.0.5-1.el5.x86_64.rpm
oracleasm-2.6.18-238.el5debug-2.0.5-1.el5.x86_64.rpm
oracleasm-2.6.18-238.el5-debuginfo-2.0.5-1.el5.x86_64.rpm
oracleasm-2.6.18-238.el5-2.0.5-1.el5.x86_64.rpm
I have installed the 4 files and got the error messages for the first 2 files as below:
[root@rac1 /]# rpm -ivh /home/oracleasm-2.6.18-238.el5xen-2.0.5-1.el5.x86_64.rpm
Error: Failed dependencies: kernel-xen=2.6.18-238.el5 is needed by oracleasm-2.6.18-238.el5xen-2.0.5-1.el5.x86_64.rpm
[root@rac1 /]# rpm -ivh /home/oracleasm-2.6.18-238.el5debug-2.0.5-1.el5.x86_64.rpm
Error: Failed dependencies: kernel-debug=2.6.18-238.el5 is needed by oracleasm-2.6.18-238.el5debug-2.0.5-1.el5.x86_64.rpm
The last 2 files have been installed successfully. But when reboot Oracle Linux Server-Base 2.6.18-238.el5, I still see :
"Initializing ASMLib driver: FAILED."
[root@rac1 /]#/etc/init.d/oracleasm configure -i
Its output "initializing Oracle ASMLib driver: OK "
My questions are:
Does the issue OS "Initializing Oracle ASMLib driver: FAILED" have effect later ? Do we need to solve it ?
Thanks.

Initializing oracle asmlib driver failed

Hi
we are in the process of setting up oracleasm driver for linux and we are getting the following error when issuing oracleasm configure command
initializing oracle asmlib driver failed
Following are the packages i have
oracleasm-2.6.9-89.0.0.0.1.EL-2.0.5-1.el4
oracleasmlib-2.0.4-1.el4
oracleasm-support-2.1.3-1.el4
Following is my kernel vesion
uname -ar
Linux 2.6.9-89.0.0.0.1.ELSMP #1 SMP i686 i686 i386 GNU/LINUX
I even tried after disabling SE linux
# /usr/sbin/setenforce 0
/usr/sbin/setenforce : SELinux is disabled
(rebooted as well)
But still i am getting the same error..Is there anyway to fix this ?
Thanks
Pramod

Hi,
you installed the wrong
oracleasm-2.6.9-89.0.0.0.1.EL-2.0.5-1.el4
Your kernel is:
2.6.9-89.0.0.0.1.ELSMP
so you need
oracleasm-2.6.9-89.0.0.0.1.ELSMP-2.0.5-1.el4
You should find that on the CD on ULN or setup your server for public-yum.
http://public-yum.oracle.com
Regards
Sebastian

ASM creation problem Initializing the Oracle ASMLib driver: failed

hi
oel 5.6 64bit
db 11gR2 64bit
[root@rac-1 ASM]# rpm -qa | grep ora
oracleasm-2.6.18-164.el5xen-2.0.5-1.el5
libtheora-1.0alpha7-1
oracleasm-2.6.18-164.el5debug-2.0.5-1.el5
oracleasm-2.6.18-164.el5-2.0.5-1.el5
oracle-logos-4.9.17-10
oracle-validated-1.1.0-7.el5
oraclelinux-release-5-6.0.1
oracleasm-support-2.1.4-1.el5
[root@rac-1 ASM]# rpm -qa | grep asm
nasm-0.98.39-3.2.2
oracleasm-2.6.18-164.el5xen-2.0.5-1.el5
oracleasm-2.6.18-164.el5debug-2.0.5-1.el5
oracleasm-2.6.18-164.el5-2.0.5-1.el5
oracleasm-support-2.1.4-1.el5
[root@rac-1 ASM]#
[root@rac-1 ASM]# oracleasm configure
ORACLEASM_ENABLED=true
ORACLEASM_UID=oracle
ORACLEASM_GID=asmadmin
ORACLEASM_SCANBOOT=true
ORACLEASM_SCANORDER=""
ORACLEASM_SCANEXCLUDE=""
[root@rac-1 ASM]# service oracleasm restart
Dropping Oracle ASMLib disks:                              [ OK ]
Shutting down the Oracle ASMLib driver:                    [ OK ]
Initializing the Oracle ASMLib driver:                     [FAILED]
[root@rac-1 ASM]#can anyone help??

hi
just another confirmation i need :
i have some raw devices using /etc/rawdevices file and losetup to /dev/loop(n); can you say what are the udev rules to set so that all the permission and loop(n) devices come up before ASMLib driver initialization ?? eg.
http://www.idevelopment.info/data/Oracle/DBA_tips/Automatic_Storage_Management/ASM_20.shtml
[root@rac-1 ~]# oracleasm listdisks
VOL1
[root@rac-1 ~]# oracleasm createdisk VOL2 /dev/loop1
Unable to access device "/dev/loop1"
[root@rac-1 ~]# losetup /dev/loop1 /oracle_ASM_SWAP/ASM/ASM_FILE1
[root@rac-1 ~]# oracleasm createdisk VOL2 /dev/loop1
Writing disk header: done
Instantiating disk: done
[root@rac-1 ~]# losetup /dev/loop2 /oracle_ASM_SWAP/ASM/ASM_FILE2
[root@rac-1 ~]# oracleasm createdisk VOL3 /dev/loop3
Unable to access device "/dev/loop3"
[root@rac-1 ~]# oracleasm createdisk VOL3 /dev/loop2
Writing disk header: done
Instantiating disk: done
[root@rac-1 ~]# losetup /dev/loop3 /oracle_ASM_SWAP/ASM/ASM_FILE3
[root@rac-1 ~]# oracleasm createdisk VOL4 /dev/loop3
Writing disk header: done
Instantiating disk: done
[root@rac-1 ~]# losetup /dev/loop4 /oracle_ASM_SWAP/ASM/ASM_FILE4
[root@rac-1 ~]# oracleasm createdisk VOL5 /dev/loop5
Unable to access device "/dev/loop5"
[root@rac-1 ~]# oracleasm createdisk VOL5 /dev/loop4
Writing disk header: done
Instantiating disk: done
[root@rac-1 ~]# losetup /dev/loop5 /oracle_ASM_SWAP/ASM/ASM_FILE5
[root@rac-1 ~]# oracleasm createdisk VOL6 /dev/loop5
Writing disk header: done
Instantiating disk: done
[root@rac-1 ~]# oracleasm listdisks
VOL1
VOL2
VOL3
VOL4
VOL5
VOL6
[root@rac-1 ~]#http://admindba.com/forum.php?gcm=2&grid=115612
assigning to /etc/rc.local making the disk available only VOL1 not others.
can i still use ADVM ??
[oracle@rac-1 dbs]$ . ~/.orcl_ASM.profile
[oracle@rac-1 dbs]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Mon Apr 4 11:34:51 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> !
[oracle@rac-1 dbs]$ ls
hc_orcl.dat   init.ora      lkORCL     spfileorcl.ora
init+ASM.ora initorcl.ora orapworcl
[oracle@rac-1 dbs]$ exit
SQL> startup
ORA-01078: failure in processing system parameters
ORA-29701: unable to connect to Cluster Synchronization Service
SQL> startup pfile='/oracle_db/oracle/product/11.2.0/dbhome_1/dbs/init+ASM.ora';
ORA-29701: unable to connect to Cluster Synchronization Service
ORA-01078: failure in processing system parameters
SQL> Disconnected
[oracle@rac-1 dbs]$ cd /oracle_db/oracle/product/11.2.0/dbhome_1/bin/l
lbuilder      ldapcompare   ldapsearch    loadpsp       lxchknlb
lcsscan       ldapdelete    ldifmigrator loadpspO      lxegen
ldapadd       ldapmoddn     linkshlib     lsnodes       lxinst
ldapaddmt     ldapmodify    lmsgen        lsnrctl
ldapbind      ldapmodifymt loadjava      lsnrctl0
[oracle@rac-1 dbs]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Mon Apr 4 11:47:18 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> create spfile from pfile='/oracle_db/oracle/product/11.2.0/dbhome_1/dbs/init+ASM.ora';
File created.
SQL> startup
ORA-29701: unable to connect to Cluster Synchronization Service
SQL> Disconnected
[oracle@rac-1 dbs]$ vi .orcl_ASM.profile
[oracle@rac-1 dbs]$ vi .orcl_ASM.profile
[oracle@rac-1 dbs]$ . .orcl_ASM.profile
[oracle@rac-1 dbs]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Mon Apr 4 11:50:29 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup mount
ORA-29701: unable to connect to Cluster Synchronization Service
SQL> Disconnected
[oracle@rac-1 dbs]$ ls
hc_orcl.dat   init.ora      lkORCL     spfile+ASM.ora
init+ASM.ora initorcl.ora orapworcl spfileorcl.ora
[oracle@rac-1 dbs]$ vi init+ASM.ora
[oracle@rac-1 dbs]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Mon Apr 4 11:51:25 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> create spfile from pfile='/oracle_db/oracle/product/11.2.0/dbhome_1/dbs/init+ASM.ora';
File created.
SQL> startup mount
ORA-29701: unable to connect to Cluster Synchronization Service
SQL>how to get rid of ORA-29071 for this new ASM instance creation??
http://www.oracledba.org/10g/asm/asm_install.html
this is 10g related.
kind regards

Unmounting Filesystem Failing

After the recent initscripts upgrade, whenever I poweroff or reboot my EeePC 901, the root filesystem is not unmounted, and at reboot the disk is fscked.
Unmounting Filesystem [Fail]
Remounting Root Filesystem Read-only [Fail]
All of the daemons are successfully reported stopped (including Laptop-mode which I stop with a script in rc.local.shutdown when on battery: https://bbs.archlinux.org/viewtopic.php … 14#p930314).
The laptop is completely up-to-date. How would I go about diagnosing what is preventing the clean shutdown?

jasonwryan wrote:
Sure.
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs defaults 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
UUID=78b9738e-dd5b-4616-a6dc-1ca8c96e0209 / ext2 defaults,noatime 0 1
UUID=f1e7eedd-66e0-4e86-821d-f57b1fa2c0ca /home ext2 defaults,noatime 0 1
tmpfs /var/log tmpfs size=1M 0 0
Hmm, nothing at all stands out here, and we we explicitly don't unmount API filesystems or anything else mounted on a RAM based FS. I'd be curious what's running right before the call to umount. Just before line 55 of /etc/rc.shutdown where everything is unmounted, can you stick in a call to ps and lsof?
/bin/ps aux > /ps.out; /usr/sbin/lsof > /lsof.out
Unrelated -- you don't need those /dev/{pts,shm} entries anymore. They're mounted by /etc/rc.sysinit. Also, your home should have a passno of 2, not 1, meaning fsck it after root. (reference fstab(5)).

Mounting local filesystem - FAIL (yet the fs still mounts...) [SOLVED]

After modifying my time/date setup (setting the hardware clock to UTC, and using a custom timezone file) I started to get a [FAIL] message during boot (after the system had resynched to drive times to the system time), and shutdown.
@ boot time
Mounting local filesystem
Ext3-fs: barriers not enabled
kjournal starting. Commit interval 5 seconds
Ext3-fs (sda4): using internal journal
Ext3-fs (sda4): mounted filesystem with ordered data mode
[FAIL]
@ shutdown
Unmounting Filesystem [FAIL]
Nothing seems to be negatively affected, and the boot and shutdown processes continue without even pausing, and sda4 (my /home directory) certainly seems to by mounted (since I'm using it now).
I've run fsck at boot a couple times, but the drives keep coming back clean. I've tried using my old timezone setup, but the fail message persists. I've successfully unmounted and mounted sda4 as Root, trying to generate an error message of some kind, but all I get is a successfully unmounted, or mounted, drive. I've unmounted sda4 priod to shutdown as well, but the message persists.
The only place in the logs the [FAIL] message shows up is in /var/log/boot:
Mounting local filesystem [BUSY] [FAIL]
I'm at a loss. I would like to fix this, if only to be sure that it's not a symptom of a larger problem. At the very least, I'd like to know what is causing it.
Last edited by uxrs75 (2011-08-02 06:40:31)

You interpret correctly, Logicien. BIOS is set to UTC; HARDWARECLOCK="UTC". Time and date are a-ok.
I ran mkinitcpio -p kernel26, but the message persists. I also tried using the live cd, and mounting each of the drives in turn. All of them mounted successfully, with no error messages. To verify that it is sda4, I commented the sda4 line out in fstab, and rebooted the machine. I got:
Mounting Local Filesystems [FAIL]
but none of the Ext3-fs stuff, and the boot process continued successfully. I'm wondering if it's something else.
I'll try adding quiet to the kernel boot line later this evening and see what that brings about.
rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged, using "" makes hwclock fall back
# to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# Note: if unset, the value in /etc/localtime is used unchanged
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="PST"
KEYMAP="uk"
CONSOLEFONT="ter-116n.psf.gz"
#CONSOLEMAP="8859-1"
USECOLOR="yes"
# HARDWARE
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
# Replace every !module by an entry as on the following line in a file in
# /etc/modprobe.d:
# blacklist module
# See "man modprobe.conf" for details.
MODULES=()
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="darkstar"
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
# - broadcast: broadcast address (ignored for DHCP) (optional)
# - gateway: default route (ignored for DHCP)
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
interface=eth0
address=
netmask=
broadcast=
gateway=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
DAEMONS=(hwclock syslog-ng dbus !network !netfs crond alsa mpd)
fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
#none /proc/bus/usb usbfs auto,busgid=101,busmode=0775,devgid=101,devmode=0664 0 0
/dev/sr0 /media/sr0 auto ro,users,noauto,unhide 0 0
/dev/sr1 /media/sr1 auto ro,users,noauto,unhide 0 0
#/dev/sda1 /boot ext2 defaults 0 1
#/dev/sda2 swap swap defaults 0 0
#/dev/sda3 / ext3 defaults 0 1
#/dev/sda4 /home ext3 defaults 0 1
UUID=597bd99a-173b-4b23-947d-b8a50859bcdd /boot ext2 defaults 0 1
UUID=a51a3b55-7c5c-45bb-96eb-79cfd1a77f54 swap swap defaults 0 0
UUID=c6ecf0fe-d2c4-4743-b639-1550295b65c6 / ext3 defaults 0 1
UUID=ff7030b8-890a-4673-bd1c-f502ca5efb2b /home ext3 defaults 0 1
/dev/sdb1 /media/sdb1 auto noauto,owner,users 0 0
/dev/sdb1 /media/sdb1 auto noauto,owner,users 0 0
/dev/sdc1 /media/sdc1 auto noauto,owner,users 0 0
/dev/sdd1 /media/sdd1 auto noauto,owner,users 0 0
/dev/sde1 /media/sde1 auto noauto,owner,users 0 0
/dev/sdf1 /media/sdf1 auto noauto,owner,users 0 0
fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 * 1 208844 104422 83 Linux
/dev/sda2 208845 738989 265072+ 82 Linux swap / Solaris
/dev/sda3 738990 103153364 51207187+ 83 Linux
/dev/sda4 103153365 976768064 436807350 83 Linux
dumpe2fs -h /dev/sda1
dumpe2fs 1.41.14 (22-Dec-2010)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 597bd99a-173b-4b23-947d-b8a50859bcdd
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: ext_attr resize_inode dir_index filetype sparse_super
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: not clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 26208
Block count: 104420
Reserved block count: 5221
Free blocks: 84721
Free inodes: 26177
First block: 1
Block size: 1024
Fragment size: 1024
Reserved GDT blocks: 256
Blocks per group: 8192
Fragments per group: 8192
Inodes per group: 2016
Inode blocks per group: 252
Filesystem created: Fri Apr 30 20:35:47 2010
Last mount time: Thu Aug 19 05:44:48 2010
Last write time: Mon Aug 1 13:58:14 2011
Mount count: 8
Maximum mount count: 23
Last checked: Mon Aug 1 07:23:24 2011
Check interval: 15552000 (6 months)
Next check after: Sat Jan 28 07:23:24 2012
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Default directory hash: half_md4
Directory Hash Seed: f5f22ff8-0cb1-4c30-a172-ead082f0ad8a
dumpe2fs -h /dev/sda3
dumpe2fs 1.41.14 (22-Dec-2010)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: c6ecf0fe-d2c4-4743-b639-1550295b65c6
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 3203072
Block count: 12801796
Reserved block count: 640089
Free blocks: 10487133
Free inodes: 3000642
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1020
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Fri Apr 30 20:35:51 2010
Last mount time: Mon Aug 1 13:58:14 2011
Last write time: Mon Aug 1 07:22:14 2011
Mount count: 8
Maximum mount count: 23
Last checked: Mon Aug 1 07:22:14 2011
Check interval: 15552000 (6 months)
Next check after: Sat Jan 28 07:22:14 2012
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
First orphan inode: 262152
Default directory hash: half_md4
Directory Hash Seed: 08e3f2db-7bb4-41fc-9364-9a9f637951ff
Journal backup: inode blocks
Journal features: journal_incompat_revoke
Journal size: 128M
Journal length: 32768
Journal sequence: 0x0007df4e
Journal start: 1
dumpe2fs -h /dev/sda4
dumpe2fs 1.41.14 (22-Dec-2010)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: ff7030b8-890a-4673-bd1c-f502ca5efb2b
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 27303936
Block count: 109201837
Reserved block count: 5460091
Free blocks: 80860937
Free inodes: 27074933
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 997
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Fri Apr 30 20:36:07 2010
Last mount time: Mon Aug 1 13:58:14 2011
Last write time: Mon Aug 1 13:58:14 2011
Mount count: 8
Maximum mount count: 25
Last checked: Mon Aug 1 07:23:25 2011
Check interval: 15552000 (6 months)
Next check after: Sat Jan 28 07:23:25 2012
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: e8dbb219-f7fe-4878-96b6-9137361ce1e2
Journal backup: inode blocks
Journal features: journal_incompat_revoke
Journal size: 128M
Journal length: 32768
Journal sequence: 0x0011b560
Journal start: 1
Last edited by uxrs75 (2011-08-02 06:19:11)

HT2173 How to know when a hard drive has failed ?

How to know when a hard drive has failed ?

Machine doesn't boot. You experience strange crashes. Gets wrong results. Your harddrive is five or more years old. Time to consider repacing it.   You do have backup?
You may want to run these "standard" fixes if the problem persists.
1) Check the amount of free space on your harddrive. You should have a several gigs free.
2) You should run disk utility
     a) verify the disk
     b) update your permissions.
3) Try a safe boot.
    Shutdown your machine. Hold down the shift key. Poweron. Wait awhile Wait awhile while you harddrive
      is being checked.
    http://support.apple.com/kb/ht1455
4) You may want to run applejack to clean up your machine.
     http://applejack.sourceforge.net/
a lot more ways to fix your Mac.
http://www.thexlab.com/faqs/faqs.html
verify & repair your startup drive
To verify & repair you file system on the startup drive, you will need to run disk utility from you installation DVD.
This article will tell you how to get to disk utility. Once in a disk utility, you can go and attempt to recover the disk.
http://support.apple.com/kb/TS1417
To repair your startup drive, you will need to run disk utility from your startup DVD.
Mac OS X 10.4: About the utilities available on the Mac OS X 10.4 Install DVD
http://support.apple.com/kb/HT2055
How to run disk utility from your startup DVD.
Insert your startup DVD into your reader. Power down your machine. Hold down to the c key. Power on your machine. This will bootup your startup DVD.
This will bring you to a panel asking you for your language. Pick your language.
You you come to the Install Mac OS panel. Do not install.
Click on Utilities menu item. This will give you a pulldown list of utilities.
Click on the disk utility.
You are now in disk utility. Pick your disk. Click on repair it should be on the lower right of the panel.
Once the repair completes successfully, you should update your permissions.
Verify a disk
As an alternative, you can verify that the filesystem on the disk is correct. You will not be able to repair the file system.
I suggest that you use disk utility to verify that your startup disk is OK.
Macintosh-HD -> Applications -> Utilities -> Disk Utility
Start up disk utility. On the left pane view, you will see a list of all your disks.
Click on your startup disk.
Click on the First Aid Tab.
Click on verify.
Hopefully your disk will verify. If not, you have to boot from your installation DVD and run Disk Utility from there to attempt to repair your file-system.

How do I restore from time machine backup onto unmounted disk drive "disk0s2?" :-(

In trying to restore my MacBook Pro after a strange freeze, I seemed to have unmounted the main disk drive. So, I have no drive on which to restore my computer using my time machine backup. What do I do now???

Give this a try:
Repair the Hard Drive and Permissions - Lion/Mountain Lion
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported then click on the Repair Permissions button. When the process is completed, then quit DU and return to the main menu. Select Restart from the Apple menu.
See if you are able to get the partition to mount. If not select the Terminal from the Utiilities menu. At the prompt enter:
sudo mount disk0s1
Press RETURN and authenticate. Your password will not be echoed. Press RETURN again. I'm assuming you have a disk with one partition. If that's not correct, then do not use the above command.

Restoring time machine files from unmounted external drive

Help please..
I have a time machine backup I need to restore. It's a backup from an external drive that has failed.
When I go "enter time machine," I can't see the contents from the external drive anymore to restore it.. because the external drive isn't mounted. It's not mounted because it has failed. I can see when I browse the TM backup directly via finder there are files from the amounted drive in the backup... as I'd expect.
So... How do I restore drives from an unmounted external drive?
Do I need to buy a new drive and name it the same as the old drive? Then will it show up?

While in Time Machine, press the key combination shift-command-C. The front window will show all mounted volumes. All snapshots should now be accessible. Select the one you want and navigate to the files you want to restore.

What are my options when Disc Utility says my hard drive is failing?

Before I upgraded to Tiger on my G4 (this morning), I ran Disk Utility, repair permissions. After the Tiger installation, I ran Disk Utility again and got the message that my hard drive is "failing" in red letters, something I have never seen before.
I started up with the Installer Disk and tried to run Disk repair from that, but the red remains and I am prevented from doing a repair.
What are my options?
(I added this question to another thread, but got a little confused about the answered/not answered option when my message was not accepted as a "not answered." Anyway, John Huber1's response to my original question was helpful. I thought it was better to start a new thread.)
Thanks,
Jeanie
Power PC G4 Mac OS X (10.4.5)

Hey, guys.
I ran into a problem this morning that I've never ran into before and I wasn't sure where to write it but I thought this is best.
Here it goes...
Last night I had a power surge and when I restarted my computer, my external hard drive did not mount on my desktop. I than proceeded with restarting my computer, I relinked all my connections and I cant seem to get it fixed. I have a lot of material on my external drive that I dont have backed up (I know, a stupid move) anyways, I dont want to lose that information. Also, when I open up disk utility, the icon for my external drive is there and the partition I made for my external drive shows up also but the title of my partition for my external hard drive is not in bolded font. I tried to click the button to mount my external drive cause the specs tell me that it is not mounted but when I press the mount button, it does nothing. I than tried clicking the unmount button and than restart my computer and still nothing.
What problem am I facing and how can it be fixed?
Thanks.

Disk Utility - Restore can not unmount target drive

Just got a brand new MacBook Pro with Lion. As usual there are "issues"..
I wanted to move my old TimeMachine backup (250 GB) to a larger Firewire drive (500 GB) and found a lot of instructions on that.. Problem is they don't work on Lion. (Both are Iomega drives with Firewire)
The instructions suggest that using Disk Utility to "restore" the new drive from the old will work but I always get the Error "Can not unmount target drive..." and I can see that the source drive is unmounted but not the target. I did all of the "First Aid" stuff to both drives.. (and the target drive was turned into a MacOS partition and verified..)
I then tried the exact same process on my old MacBook Pro (Leopard) and everything worked as expected..
Was there another way to do this in Lion.. or is this broken..???
Thanks for any feedback..
John..

Is the new drive prepped?
Drive Preparation
1. If you are preparing an external or a non-startup drive, then open Disk Utility in your Utilities folder.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Security button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
In Disk Utility you clone as follows:
Clone using Restore Option of Disk Utility
Open Disk Utility from the Utilities folder.
Select the destination volume from the left side list.
Click on the Restore tab in the DU main window.
Check the box labeled Erase destination.
Select the destination volume from the left side list and drag it to the Destination entry field.
Select the source volume from the left side list and drag it to the Source entry field.
Double-check you got it right, then click on the Restore button.
Destination means the new backup drive. Source means the old backup drive.
If you still have a problem then boot into the Recovery HD:
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Choose Disk Utility from the main menu then click on the Continue button.

Bit locker drive encryption failed due to power failer and hard disk corrupted

I ran Bitlocker drive ecryption drive D. My pc is windows 7 ultimate, while it was in progress of 1% due to power failer the encryption failed, when power resume the drive didn't showed the file format nor the size but it shows the size in disk management.
It showed like this in My computer
I do Have the recovery code password and back of recovery password so I ran the "manage-bde-_unlock D:-rp[my code ]
and my pc got hang no other option rather than to press the restart button.
then I used commang "repair-bde -force D:I:-rp[my rp] and following info showed but it stucked in 1% about 8 hours, and there was no increase in the pecentage
I also connected the hardisk to mac but all othe partation showed but didn't showed the encrypted one.
I had lots of memorable picture and other backups so any one kindly help me to get out of this problem. Thanks for help

Hi,
The BitLocker encryption and decryption processes can be interrupted by turning the computer off, and it will resume where it left off the next time Windows starts. This is true even if the power is suddenly unavailable.
Bitlocker-repair (repair-bde) tool
can't repair a drive that failed during the encryption or decryption process.
In addition, could you please explain a bit for what drive you are trying to deal with? external one?
When you first restart your PC, have you seen any signs that indicate that the encryption is in process?
Regarding your scenario, please take a look to see if the following articles could help here:
Scenario 11: Recovering Data Protected by BitLocker Drive Encryption (Windows 7)
Besides, when running manage-bde command, did we followed the steps mentioned in the below article?
Scenario 14: Using a Data Recovery Agent to Recover BitLocker-Protected Drives (Windows 7)
Best regards
Michael Shao
TechNet Community Support

How to backup data when hard drive is failing.

I think my hard drive is failing..
I booted using Install DVD, and got message in Disc Utility that "this drive has a hardware problem that can't be repaired." It mentioned I should backup data and consult apple representative..
I clicked on Macintosh HD under the red physical drive (500.11 GB Hitachi HTS) and did disc repair.
Strangely, the message went away on the physical drive when I finished. It turned back to black wording and gave green "verified/repaired" messages in the log.
I am still able to boot my macbook, although everything is running slowly... Desktop excel files take 15 mins to open.
Does this still sound like a failing hard drive?
I am trying to act fast and borrowed my sister's external harddrive/ "passport for mac", and it slowly prompted a time machine backup. It is slowly working through "8.34GB of 200.33GB"
I do not really understand what I am doing, but hoping this is the right move. Could someone explain what time machine will do or how it will help?
Is there any chance I will harm her external hd?
I am mostly worried about iPhoto and itunes library, iMovie projects,and important excel spreadsheets on my desktop. Is time machine looking after these concerns?
Any help greatly appreciated.

Where is you TM backup?
Where are your external data redundancies?
Now you will need to use very expensive data recovery experts to recover data when you could have had it safely on a $100 worth of 2 external HD.
Mechanical HD failure circumvents using recovery software.......so, now you backed yourself into a corner and needed expensive data expert recovery.
You took a wrong turn a long while back before reaching this cliff edge.
that wrong term was not having (preferably 2) external HD as a redundant data archive.

Is there an issue with the hitachi hard drives in the MacBook Pro's ? Got a 15 inch and a 13 inch at the same time and both drives have failed in under two years. I have heard from a few other people with same issue.

Is there an issue with the hitachi hard drives in the MacBook Pro's ? Got a 15 inch and a 13 inch at the same time and both drives have failed in under two years. I have heard from a few other people with same issue. Other drive I have had have lasted at least 5 or more years.

there is a dylib you can put in the springboard if jailbroken but if not you have to find an apple store

Unmounting ASMlib driver filesystems failed

Similar Messages

Maybe you are looking for