Cannot mount root

Hi.
I just installed the Solaris 8 from CD on Enterprise 420R. Went through the Install process ok. Formatted the disk in the process and accepted the system boot partition size of 512MB. Rebooted and now I get an error:
panic CPU0, cannot mount root, and then it reboots in the loop.
Any ideas what is wrong and how to get back to the boor prompt?
Thanks a lot!

Again, the detail error is
Cannot mount root on /pci@0,0/pci-ide@7,1/ide@0/sd@1,0:a fstype ufs
panic[cpu0]/thread=fec17440:vfs-mountroot:cannot mount root

Similar Messages

Cannot mount root during Solaris install on SPARCengine ULTRA axi

I use boot cdrom which sucessfully formats swp partition and copies files to hd. But then when I reboot I get the following:
SPARCengine(tm)Ultra(tm) AXi (UltraSPARC-IIi 440MHz), PS/2 Keyboard
OpenBoot 3.10.10 ME, 512 MB memory installed, Serial #10660686.
Ethernet address 8:0:20:a2:ab:4e, Host ID: 80a2ab4e.
ok boot disk4
Boot device: /pci@1f,0/pci@1/scsi@1/disk@4,0 File and args:
SunOS Release 5.8 Version Generic_108528-11 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
Cannot mount root on /pci@1f,0/pci@1/scsi@1/disk@4,0:a fstype ufs
panic[cpu0]/thread=10408000: vfs_mountroot: cannot mount root
0000000010407970 genunix:vfs_mountroot+70 (10435c00, 0, 0, 10410920, 10, 14)
%l0-3: 0000000010435c00 00000000104391c8 000000002f000000 0000000010435dc0
%l4-7: 0000000000000000 00000000104136b8 00000000000b7bf6 0000000000001bf6
0000000010407a20 genunix:main+94 (10410168, 2000, 10407ec0, 10408030, fff2, 1004
ef88)
%l0-3: 0000000000000001 0000000000000001 0000000000000015 0000000000000ea5
%l4-7: 0000000010428c28 0000000010462320 00000000000cd920 0000000000000540
skipping system dump - no dump device configured
rebooting...
Resetting ...
PS: I have recently reset the NVRAM on this machine not sure if there are any env settings I should have setup in OBP (I reset HOST ID and MAC-ADDRESS).

disk@0,0:a is slice/partition 0
disk@0,0:b is slice/partition 1
I'm not sure where you told it your swap slice was going to be. Looks like slice 1. Mini-root gets installed in slice 1 and then the install begins from there.
In the future, if you just "boot cdrom" from disk 1 of 2 you won't run into these issues.

Sol - Intel - cannot mount root - J Keil

J Keil,
Some how my first messages were deleted off your site - none the mater.
As you suggested, I changed target hard drive to Sec Master and Cd to Sec Slave. Like before I get a similar message, from the install CD:
Cannot mount root on /pci@0,0/pci-ide@7,1/ide@1/sd@1,0:a fstype ufs
panic[cpu0]/thread=fec17540: vfs_mountroot: cannot mount root
I downloaded CD 1 again, burn't image - I still get "Cannot find boot.bin." Error message.
Phil

I copied this over to the intel install board. Sorry
I lost it

Persistent device naming - cannot mount root as rw

hello people,
i started using persistent block device naming but quickly realized i can only use it for non-root (/) partitions in fstab otherwise it will only get mounted as readonly and my system (arch current) will cease to boot.
# this line only mounts fs as ro
#/dev/disk/by-uuid/d02a0ef4-8cb3-460c-a48a-471f2798e4ad / ext3 default 0 1
# i get stuck while mounting fs as ro when using this line
#UUID=d02a0ef4-8cb3-460c-a48a-471f2798e4ad / ext3 default 0 1
# so i have to use the old format (non persistent device naming)
/dev/sda6 / ext3 defaults 0 1
# the other partitions (same disk) work just fine
/dev/disk/by-uuid/cc295f7d-3927-433d-bcc0-2d2267e0d672 /home ext3 defaults 0 1
/dev/disk/by-uuid/936823be-b9bb-4a9d-a4e4-b4d62972f0af swap swap defaults 0 0
/dev/disk/by-uuid/E8A04533A0450A10 /mnt/win-c ntfs-3g locale=sk_SK.utf8,nls=utf8,users 0 0
snippet from menu.lst:
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/d02a0ef4-8cb3-460c-a48a-471f2798e4ad ro
initrd /boot/kernel26.img
does anyone have an idea what may be causing this?
thanks.
jozef

Both of the UUID fstab lines for your root filesystem have 'default' instead of 'defaults'. Is that intentional, or is it a typo in your post?.
I don't know offhand whether 'default' is even a valid option, or what effect it would have if it is.

"cannot mount root, errno 19...BSD root:disk0s2, major 14, minor 2"

I have been trying to startup my MacBook Pro in Safe Mode for over 30 min, and this is part of the msg that keeps appearing.
Does anyone have any suggestions, please?

i've tried all this, and keeps spitting the disk out. ive rarely used the internal cd/dvd drive as i have an external, so im not sure if thats even funtioning right.
going to try and make a bootable usb drive on my mates macbook and see if that works.
but if anybody else has any input in the meantime, im all ears.

Cannot mount certain partitions: /dev/ entries do not exist

Hello all. Strange problem here. First I will describe my disk layout. I triple boot Gentoo, Arch, and FreeBSD. My partitions look like this:
/dev/hda = MAXTOR 6L040J2, ATA DISK drive 40GB
hda1 = shared '/boot' partition
hda2 = gentoo '/' partition
hda3 = gentoo '/usr/' partition
hda4 = gentoo '/home' partition
/dev/hdb = SAMSUNG SP0802N, ATA DISK drive 80GB
hdb1 = shared music partition mounted as /home/music on both Gentoo and Arch
hdb2 = shared swap partition
hdb3 = FreeBSD partition
hdb4 = logical Partition
hdb5 = archlinux '/' partition
hdb6 = shared video partition mounted as /home/music/video on both Gentoo and Arch
Now both gentoo and arch use devfs. From gentoo I can see all partitions in the /dev directory and mount accordingly, however, from Arch I cannot mount my gentoo partitions on /dev/hda, and in fact they do not even exist in the /dev directory. Only /dev/hda1 is visible (the shared boot partition which holds all my kernels regardless of distro).
Running fdisk -l /dev/hda from arch gives me this puzzling output:
Disk /dev/hda: 40.0 GB, 40027029504 bytes
255 heads, 63 sectors/track, 4866 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 4111 33021576 55 EZ-Drive
So it would seem that fdisk thinks that /dev/hda1 takes up the entire drive, and is labeled as 'EZ-Drive'?!?!?!?!?!? I can assure you that running the same command from gentoo gives me the correct partitions and disklabels ie: id 83 Linux
Does anyone have a clue as to what is going on here? This isn't really a big deal at this point, just an interesting annoyance that I would like to discover the cause of.
TIA

I don't know how it could be that the kernels interpret the partition table differently, and I'm certainly not sure that this is what's going on. That's why I suggested loading Arch with the Gentoo kernel. I wouldn't expect the system to be its true self, but merely satesfy the curiosity by checking whether it would see the right partitions (a.k.a. trouble-shooting).
It shouldn't be a problem to test this, unless your Arch root uses a file system that is not built into your Gentoo kernel. If for instance hdb5 is reiserfs and your 2.4 kernel has that as a module, you're probably out of luck regarding my suggestion. If this is the case, you could also try the Arch 2.4 kernel. It can coexist with your current kernel because the kernel packages for the two trees have different names.
pacman -S kernel
Hope this helps,
-bogo

Cannot mount volume

Hi
I have a server connected to a MDC.
The MDC is running 10.4.8 server, XSan 1.4.1.
The MDC can mount the SAN correctly.
The client is running 10.4.8 server, XSan 1.4.1
The client cannot mount the SAN.
What I've tried:
Re-installing XSAN
Re-installing the 10.4.8 combo update
Re-installing the 2006-007 security update
Changing from Controller, medium to client and back.
mount -t ... /Volumes/SAN
Every time I get this in the syslog:
Dec 13 13:54:35 xsanclient kernel[0]: Could not mount filesystem SAN, cvfs error ' Timeout' (25)
any ideas

More from the log:
Dec 13 22:17:51 multimedia kernel[0]: Could not mount filesystem SAN, cvfs error ' Timeout' (25)
Dec 13 22:18:37 multimedia kernel[0]: Could not mount filesystem SAN, cvfs error ' Timeout' (25)
Dec 13 22:18:53 multimedia sudo: admin : TTY=ttyp1 ; PWD=/Users/admin ; USER=root ; COMMAND=/usr/bin/tail -f /var/log/system.log
Dec 13 22:19:01 multimedia kernel[0]: Could not mount filesystem SAN, cvfs error ' Timeout' (25)
Dec 13 22:19:23 multimedia servermgrd: xsan: [39/36E6F0] ERROR: getfsmvol_atindex: Could not connect to FSM because Admin Tap Connection to FSM failed. - Operation timed out
Dec 13 22:19:24 multimedia kernel[0]: Could not mount filesystem SAN, cvfs error ' Timeout' (25)

Cannot mount external USB drive

During a recent update I remember pacman asking about replacing some package with another package to handle disk mounting. I think the added package was "gnome-volume-manager" or "gnome-disk-utility" (or both). I didn't see any postings describing problems with doing this, so went ahead and allowed the change. Now it's a few days later and I find I cannot mount an external USB hard drive anymore. It has an entry in fstab, and although I have tried mutiple edits of the device to associate the drive with, nothing works.
The disk used to associate with /dev/sdb1. Now this device no longer exists. Here is what has happened to my /dev/sd* entries:
brw-rw---- 1 root disk 8, 0 2009-10-27 11:08 /dev/sda
brw-rw---- 1 root disk 8, 3 2009-10-27 11:08 /dev/sda3
brw-rw---- 1 root disk 8, 1 2009-10-27 11:08 /dev/sda1
brw-rw---- 1 root disk 8, 2 2009-10-27 11:08 /dev/sda2
brw-rw---- 1 root disk 8, 4 2009-10-27 11:08 /dev/sda4
brw-rw---- 1 root storage 8, 16 2009-11-04 13:00 /dev/sdb
Trying to force association with "/dev/sdb" "/dev/sda5" (or some other number not in use) or "sdb1" (or 2,3,4, whatever) just yields "special device ... does not exist".
Does anybody know how to deal with this?
Does anybody know what package(s) I replaced when the update in question took place? I think I'd like to reverse whatever happened.
And on another note, I think another gnome-based package also recently replaced a package relating to printing. Yesterday I discovered I have printing problems too:
At first there were no printers found. Although cups is supposed to start according to rc.conf, cupsd was not running. I started it manually and then all the printers showed up again, though I cannot print duplex (again, worked fine before). What is going on with these gnome packages?!? Anyone know which package(s) I need to remove (and then what to put back) to make printing work like it used to also?
thanks much.

oddly, fdisk -l shows nothing, even for disks which are mounted (eg. /dev/sda4). when I insert a standard USB thumb drive, the following show up properly:
brw-rw---- 1 root storage 8, 32 2009-11-05 10:50 /dev/sdc
brw-rw---- 1 root storage 8, 33 2009-11-05 10:50 /dev/sdc1
and I am able to mount and use the drive as usual.
The external drive I've been struggling with has xfs for filesystem type. After using the thumb drive, /dev/sdb showed up spontaneously, but no /dev/sdb1. attempting to mount gives:
mount: /dev/sdb is not a valid block device
or
mount: special device /dev/sdb1 does not exist
depending on which device is specified in fstab.
I am thinking that either a) my ability to mount xfs filesystems has somehow been hosed, or b) there is something wrong with drive, which must have spontaneously failed very recently (it is less than 1 yr old, but this happens from time to time).
If the drive is okay, any ideas about how mounting xfs filesystems could have been broken by recent upgrades?
btw, the fstab entry (which worked fine until a couple days ago) is: /dev/sdb1 /mnt/external_1 xfs rw,noauto,user,exec 0 0

Oracle ORA-01102故障: cannot mount database in EXCLUSIVE mode

SQL> conn /as sysdba
Connected to an idle instance.
SQL> startup
oracle instance started.
Total System Global Area 276824064 bytes
Fixed Size 778736 bytes
Variable Size 137371152 bytes
Database Buffers 138412032 bytes
Redo Buffers 262144 bytes
ORA-01102: cannot mount database in EXCLUSIVE mode
出现这个问题，可能是由于断电的问题，解决方法是
出现1102错误可能有以下几种可能：
一、在HA系统中，已经有其他节点启动了实例，将双机共享的资源（如磁盘阵列上的裸设备）占用了；
二、说明 oracle 被异常关闭时，有资源没有被释放，一般有以下几种可能，
1、 oracle 的共享内存段或信号量没有被释放；
2、 oracle 的后台进程（如SMON、PMON、DBWn等）没有被关闭；
3、用于锁内存的文件lk<sid>和sgadef<sid>.dbf文件没有被删除。
首先，虽然我们的系统是HA系统，但是备节点的实例始终处在关闭状态，这点通过在备节点上查数据库状态可以证实。
其次、是因系统掉电引起数据库宕机的，系统在接电后被重启，因此我们排除了第二种可能种的1、2点。最可疑的就是第3点了。
查$ORACLE_HOME/dbs目录：
$ cd $ORACLE_HOME/dbs
$ ls sgadef*
sgadef* not found
$ ls lk*
lkORA92
果然，lk<sid>文件没有被删除。将它删除掉
$ rm lk*
再启动数据库，成功。
如果怀疑是共享内存没有被释放，可以用以下命令查看：
$ipcs -mop
IPC status from /dev/kmem as of Thu Jul 6 14:41:43 2006
T ID KEY MODE OWNER GROUP NATTCH CPID LPID
Shared Memory:
m 0 0×411c29d6 –rw-rw-rw- root root 0 899 899
m 1 0×4e0c0002 –rw-rw-rw- root root 2 899 901
m 2 0×4120007a –rw-rw-rw- root root 2 899 901
m 458755 0×0c6629c9 –rw-r—– root sys 2 9113 17065
m 4 0×06347849 –rw-rw-rw- root root 1 1661 9150
m 65541 0xffffffff –rw-r–r– root root 0 1659 1659
m 524294 0×5e100011 –rw——- root root 1 1811 1811
m 851975 0×5fe48aa4 –rw-r—– oracle oinstall 66 2017 25076
然后它ID号清除共享内存段：
$ipcrm –m 851975
对于信号量，可以用以下命令查看：
$ ipcs -sop
IPC status from /dev/kmem as of Thu Jul 6 14:44:16 2006
T ID KEY MODE OWNER GROUP
Semaphores:
s 0 0×4f1c0139 –ra——- root root
s 14 0×6c200ad8 –ra-ra-ra- root root
s 15 0×6d200ad8 –ra-ra-ra- root root
s 16 0×6f200ad8 –ra-ra-ra- root root
s 17 0xffffffff –ra-r–r– root root
s 18 0×410c05c7 –ra-ra-ra- root root
s 19 0×00446f6e –ra-r–r– root root
s 20 0×00446f6d –ra-r–r– root root
s 21 0×00000001 –ra-ra-ra- root root
s 45078 0×67e72b58 –ra-r—– oracle oinstall
根据信号量ID，用以下命令清除信号量：
$ipcrm -s 45078
如果是 oracle 进程没有关闭，用以下命令查出存在的 oracle 进程：
$ ps -ef|grep ora
oracle 29976 1 0 Jun 22 ? 0:52 ora_dbw0_ora92
oracle 29978 1 0 Jun 22 ? 0:51 ora_dbw1_ora92
oracle 5128 1 0 Jul 5 ? 0:00 oracleora92 (LOCAL=NO)
然后用kill -9命令杀掉进程
$kill -9 <PID>
总结：
当发生1102错误时，可以按照以下流程检查、排错：
1.如果是HA系统，检查其他节点是否已经启动实例；
2.检查 oracle 进程是否存在，如果存在则杀掉进程；
3.检查信号量是否存在，如果存在，则清除信号量；
4.检查共享内存段是否存在，如果存在，则清除共享内存段；
5.检查锁内存文件lk<sid>和sgadef<sid>.dbf是否存在，如果存在，则删除

No, its still not helping..even after trying to kill the semaphores:
/opt/oracle/product/db10g/dbs (ac4orcloms01-ac4:emrep)> ipcs
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00000000 0 oracle 640 538968064 1 dest
0x00000000 32769 oracle 600 192 1 dest
0x00000000 65538 oracle 600 1474564 8 dest
------ Semaphore Arrays --------
key semid owner perms nsems
------ Message Queues --------
key msqid owner perms used-bytes messages
/opt/oracle/product/db10g/dbs (ac4orcloms01-ac4:emrep)> ipcrm -m 32769
/opt/oracle/product/db10g/dbs (ac4orcloms01-ac4:emrep)> ipcrm -m 65538
/opt/oracle/product/db10g/dbs (ac4orcloms01-ac4:emrep)> ipcs
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00000000 0 oracle 640 538968064 1 dest
0x00000000 32769 oracle 600 192 1 dest
0x00000000 65538 oracle 600 1474564 8 dest
------ Semaphore Arrays --------
key semid owner perms nsems
------ Message Queues --------
key msqid owner perms used-bytes messages
/opt/oracle/product/db10g/dbs (ac4orcloms01-ac4:emrep)> ps -e f|grep emrep
3273 ? Ds 0:00 ora_ckpt_emrep
/opt/oracle/product/db10g/dbs (ac4orcloms01-ac4:emrep)>

After boot can't mount SDS file systems on 3300 mount: cannot mount /dev/md

Hi
I have a SUNW,Netra-440 with two SE 3300 SCSI each with two controllers. The server was working fine but after a boot, it can not see the metadevices stored in the 3300.
I have tried restarting the SE3300 and a boot -r from ok prompt but I still can see those disks or partitions.
Metaset Import
metaset: log01: setname "appvol": no such set
mount all SVM filesystems for group appvol
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d101
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d102
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d103
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d104
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d105
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d106
metaset: log01: setname "dbvol": no such set
mount all SVM filesystems for group dbvol
mount: No such device
mount: cannot mount /dev/md/dbvol/dsk/d107
mount: No such device
mount: cannot mount /dev/md/dbvol/dsk/d108
i can see the devices in /dev/md/appvol but i can't mount them.
Any ideas what this could be? using metaset shows nothing, metastat -s dbvol hangs.
Am I missing some patch or am I missing something here? is the SE3300 damaged? or is it a problem with SDS (solstice). I have solaris 9.
The system was working fine until we had to boot and power off to perform power tests in the rack.
thanks
Ryck
this is the output of prtdiag
root@log01 >prtdiag
System Configuration: Sun Microsystems sun4u Netra 440
System clock frequency: 177 MHZ
Memory size: 8GB
==================================== CPUs ====================================
E$ CPU CPU Temperature
CPU Freq Size Implementation Mask Die Amb. Status Location
0 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
1 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
2 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
3 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
================================= IO Devices =================================
Bus Freq Slot + Name +
Type MHz Status Path Model
pci 66 PCI5 scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1c,600000/scsi@1
pci 66 PCI5 scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1c,600000/scsi@1,1
pci 66 MB pci108e,abba (network) SUNW,pci-ce
okay /pci@1c,600000/network@2
pci 66 PCI4 scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1d,700000/scsi@1
pci 66 PCI4 scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1d,700000/scsi@1,1
pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
okay /pci@1d,700000/pci@2/network@0
pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
okay /pci@1d,700000/pci@2/network@1
pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
okay /pci@1d,700000/pci@2/network@2
pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
okay /pci@1d,700000/pci@2/network@3
pci 33 MB isa/su (serial)
okay /pci@1e,600000/isa@7/serial@0,3f8
pci 33 MB isa/su (serial)
okay /pci@1e,600000/isa@7/serial@0,2e8
pci 33 MB isa/rmc-comm-rmc_comm (seria+
okay /pci@1e,600000/isa@7/rmc-comm@0,3e8
pci 33 PCI0 SUNW,XVR-100 (display) SUNW,375-3290
okay /pci@1e,600000/SUNW,XVR-100
pci 33 MB pciclass,0c0310 (usb)
okay /pci@1e,600000/usb@a
pci 33 MB pciclass,0c0310 (usb)
okay /pci@1e,600000/usb@b
pci 33 MB pci10b9,5229 (ide)
okay /pci@1e,600000/ide@d
pci 66 MB pci108e,abba (network) SUNW,pci-ce
okay /pci@1f,700000/network@1
pci 66 MB scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1f,700000/scsi@2
pci 66 MB scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1f,700000/scsi@2,1
============================ Memory Configuration ============================
Segment Table:
Base Address Size Interleave Factor Contains
0x0 2GB 4 BankIDs 0,1,2,3
0x1000000000 2GB 4 BankIDs 16,17,18,19
0x2000000000 2GB 4 BankIDs 32,33,34,35
0x3000000000 2GB 4 BankIDs 48,49,50,51
Bank Table:
Physical Location
ID ControllerID GroupID Size Interleave Way
0 0 0 512MB 0,1,2,3
1 0 1 512MB
2 0 1 512MB
3 0 0 512MB
16 1 0 512MB 0,1,2,3
17 1 1 512MB
18 1 1 512MB
19 1 0 512MB
32 2 0 512MB 0,1,2,3
33 2 1 512MB
34 2 1 512MB
35 2 0 512MB
48 3 0 512MB 0,1,2,3
49 3 1 512MB
50 3 1 512MB
51 3 0 512MB
Memory Module Groups:
ControllerID GroupID Labels Status
0 0 C0/P0/B0/D0
0 0 C0/P0/B0/D1
0 1 C0/P0/B1/D0
0 1 C0/P0/B1/D1
1 0 C1/P0/B0/D0
1 0 C1/P0/B0/D1
1 1 C1/P0/B1/D0
1 1 C1/P0/B1/D1
2 0 C2/P0/B0/D0
2 0 C2/P0/B0/D1
2 1 C2/P0/B1/D0
2 1 C2/P0/B1/D1
3 0 C3/P0/B0/D0
3 0 C3/P0/B0/D1
3 1 C3/P0/B1/D0
3 1 C3/P0/B1/D1
root@log01 >

Hi,
thanks for your answer.
Yes format displays the physical devices, but metadb -i only shows the internal disks of the netra 440, not the ones in the 3320. metadb -s dbvol -i doesnt show anything.
metaset which is supposed to show me the metadevices, says the program is not registered.
cat /etc/lvm/md.tab has the configuration but since the scsi can be seen, the devices aren't mounted.
Any suggestions?
Cheers
Oscar
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> bootdisk
/pci@1f,700000/scsi@2/sd@0,0
1. c1t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> bootmirr
/pci@1f,700000/scsi@2/sd@1,0
2. c1t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> spare1
/pci@1f,700000/scsi@2/sd@2,0
3. c1t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> spare2
/pci@1f,700000/scsi@2/sd@3,0
4. c2t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> appvol
/pci@1c,600000/scsi@1/sd@8,0
5. c2t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol01
/pci@1c,600000/scsi@1/sd@9,0
6. c2t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol02
/pci@1c,600000/scsi@1/sd@a,0
7. c2t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol03
/pci@1c,600000/scsi@1/sd@b,0
8. c2t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol04
/pci@1c,600000/scsi@1/sd@c,0
9. c2t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol05
/pci@1c,600000/scsi@1/sd@d,0
10. c3t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol06
/pci@1c,600000/scsi@1,1/sd@8,0
11. c3t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free1
/pci@1c,600000/scsi@1,1/sd@9,0
12. c3t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free2
/pci@1c,600000/scsi@1,1/sd@a,0
13. c3t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free3
/pci@1c,600000/scsi@1,1/sd@b,0
14. c3t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotAPP
/pci@1c,600000/scsi@1,1/sd@c,0
15. c3t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotDB
/pci@1c,600000/scsi@1,1/sd@d,0
16. c4t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> APPVOLm
/pci@1d,700000/scsi@1/sd@8,0
17. c4t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@9,0
18. c4t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@a,0
19. c4t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@b,0
20. c4t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@c,0
21. c4t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@d,0
22. c5t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> d6Mirr
/pci@1d,700000/scsi@1,1/sd@8,0
23. c5t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free1M
/pci@1d,700000/scsi@1,1/sd@9,0
24. c5t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free2M
/pci@1d,700000/scsi@1,1/sd@a,0
25. c5t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free3M
/pci@1d,700000/scsi@1,1/sd@b,0
26. c5t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1,1/sd@c,0
27. c5t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotDBm
/pci@1d,700000/scsi@1,1/sd@d,0
root@log01 >metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c1t0d0s7
a p luo 8208 8192 /dev/dsk/c1t0d0s7
a p luo 16400 8192 /dev/dsk/c1t0d0s7
a p luo 16 8192 /dev/dsk/c1t1d0s7
a p luo 8208 8192 /dev/dsk/c1t1d0s7
a p luo 16400 8192 /dev/dsk/c1t1d0s7
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
root@log01 >
root@log01 >metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c1t0d0s7
a p luo 8208 8192 /dev/dsk/c1t0d0s7
a p luo 16400 8192 /dev/dsk/c1t0d0s7
a p luo 16 8192 /dev/dsk/c1t1d0s7
a p luo 8208 8192 /dev/dsk/c1t1d0s7
a p luo 16400 8192 /dev/dsk/c1t1d0s7
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
root@log01 >metadb -s appvol -i
metadb: log01: setname "appvol": no such set
root@log01 >metaset
metaset: log01: metad client create: RPC: Program not registered
root@log01 >cat /etc/lvm/md.tab
# Copyright 2002 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
# ident "@(#)md.tab 2.4 02/01/29 SMI"
# md.tab
# metainit utility input file.
dbvol/d57 1 1 c2t12d0s0
dbvol/d58 1 1 c4t12d0s0
dbvol/d4 -m dbvol/d57 dbvol/d58 1
dbvol/d55 1 1 c2t11d0s0
dbvol/d56 1 1 c4t11d0s0
dbvol/d3 -m dbvol/d55 dbvol/d56 1
dbvol/d61 1 1 c3t8d0s0
dbvol/d62 1 1 c5t8d0s0
dbvol/d6 -m dbvol/d61 dbvol/d62 1
dbvol/d59 1 1 c2t13d0s0
dbvol/d60 1 1 c4t13d0s0
dbvol/d5 -m dbvol/d59 dbvol/d60 1
dbvol/d53 1 1 c2t10d0s0
dbvol/d54 1 1 c4t10d0s0
dbvol/d2 -m dbvol/d53 dbvol/d54 1
###dbvol/d51 1 1 c2t9d0s0
dbvol/d52 1 1 c4t9d0s0
#dbvol/d1 -m dbvol/d51 dbvol/d52 1
dbvol/d1 -m dbvol/d52 1
# SOFT Partitions
dbvol/d129 -p dbvol/d5 -o 19933376 -b 526336
dbvol/d128 -p dbvol/d5 -o 19407008 -b 526336
dbvol/d127 -p dbvol/d5 -o 18880640 -b 526336
dbvol/d126 -p dbvol/d5 -o 10489952 -b 8390656
dbvol/d125 -p dbvol/d5 -o 2099264 -b 8390656
dbvol/d123 -p dbvol/d4 -o 4724864 -b 133120
dbvol/d122 -p dbvol/d4 -o 4460640 -b 264192
dbvol/d121 -p dbvol/d4 -o 4196416 -b 264192
dbvol/d120 -p dbvol/d4 -o 32 -b 4196352
dbvol/d119 -p dbvol/d3 -o 30972032 -b 526336
dbvol/d118 -p dbvol/d3 -o 10489952 -b 20482048
dbvol/d117 -p dbvol/d3 -o 4196416 -b 6293504
dbvol/d116 -p dbvol/d3 -o 32 -b 4196352
dbvol/d115 -p dbvol/d2 -o 8925408 -b 526336
dbvol/d114 -p dbvol/d2 -o 8399040 -b 526336
dbvol/d113 -p dbvol/d2 -o 7872672 -b 526336
dbvol/d112 -p dbvol/d2 -o 7346304 -b 526336
dbvol/d111 -p dbvol/d2 -o 5247072 -b 2099200
dbvol/d110 -p dbvol/d2 -o 1050688 -b 4196352
dbvol/d109 -p dbvol/d2 -o 32 -b 1050624
dbvol/d108 -p dbvol/d1 -o 33554496 -b 1572864
dbvol/d107 -p dbvol/d1 -o 32 -b 33554432
dbvol/d124 -p dbvol/d5 -o 32 -b 2099200
dbvol/d138 -p dbvol/d4 -o 38416608 -b 133120
dbvol/d137 -p dbvol/d3 -o 31498400 -b 264192
dbvol/d136 -p dbvol/d4 -o 21637312 -b 16779264
dbvol/d135 -p dbvol/d4 -o 4858016 -b 16779264
dbvol/d134 -p dbvol/d6 -o 69212288 -b 23070720
dbvol/d133 -p dbvol/d6 -o 46141536 -b 23070720
dbvol/d132 -p dbvol/d6 -o 23070784 -b 23070720
dbvol/d131 -p dbvol/d6 -o 32 -b 23070720
dbvol/d130 -p dbvol/d5 -o 20459744 -b 526336
root@log01 >metadb -s dbvol -i
metadb: log01: setname "dbvol": no such set
root@log01 >\

Cannot mount Xsan volume on Mac Pro

Hi,
I installed a new workstation - a first Mac Pro in our PPC Xsan deployment. I installed Xsan, then latest updates. However, I cannot mount an Xsan volume on this workstation. This is an abstract from the log:
May 16 19:06:14 Mac-Pro kernel[0]: Xsan Client Revision 2.7.201 Build 7.23 Built for Darwin 8.0 Created on Mon Nov 13 11:53:07 PST 2006
May 16 19:06:14 Mac-Pro sudo: root : TTY=unknown ; PWD=/Library/Filesystems/Xsan/debug ; USER=root ; COMMAND=/sbin/kextload -v -s /Library/Filesystems/Xsan/debug /System/Library/Extensions/acfsctl.kext
May 16 19:06:14 Mac-Pro /Library/Filesystems/Xsan/bin/fsmpm: NSS: No FS Name Servers file - NAME SERVICE DISABLED.
May 16 19:06:14 Mac-Pro fsmpm[246]: Portmapper: ComputerInfo: computer_name = "Mac Pro", hostname = "Mac-Pro"
May 16 19:06:14 Mac-Pro fsmpm[246]: PortMapper: CVFS Volume Meta on device: /dev/rdisk1 (blk 0xe000003 raw 0xe000003) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.50] controller # '5000393000018365' serial # '5000393000018365L0' Size: 490190848 Sector Size: 512
May 16 19:06:14 Mac-Pro fsmpm[246]: PortMapper: CVFS Volume RAID2_Left on device: /dev/rdisk2 (blk 0xe000004 raw 0xe000004) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.50] controller # '5000393000018A78' serial # '5000393000018A78L0' Size: 5860554719 Sector Size: 512
May 16 19:06:14 Mac-Pro fsmpm[246]: PortMapper: CVFS Volume RAID2_Right on device: /dev/rdisk3 (blk 0xe000005 raw 0xe000005) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.50] controller # '5000393000018805' serial # '5000393000018805L0' Size: 5860554719 Sector Size: 512
May 16 19:06:14 Mac-Pro fsmpm[246]: PortMapper: CVFS Volume RAID1_Right on device: /dev/rdisk4 (blk 0xe000006 raw 0xe000006) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.50] controller # '5000393000018319' serial # '5000393000018319L0' Size: 5860554719 Sector Size: 512
May 16 19:06:15 Mac-Pro servermgrd: xsan: [52] main: Waited 21 secs for fsmpm to start (now running)
May 16 19:06:15 Mac-Pro fsmpm[246]: PortMapper: Local FSD client is registered.
May 16 19:06:17 Mac-Pro servermgrd: xsan: [52] Done waiting for fsmpm to start
May 16 19:06:40 Mac-Pro servermgrd: xsan: [52/358E60] ERROR: mountvolumenamed(EditSAN): Cannot mount volume, file system does not know about it.
I tried reinstalling Xsan on this workstation, re-entering a licence key to the Xsan admin and rewriting Xsan settings, with no success.
All of the other 10 PowerMac workstations can access the Xsan volume with no problems.
Your help would be highly appreciated.

Hi,
I am accessing this WS via ARD, so public LAN is definitely there. I have not connected the "Xsan" network (but it should be no problems communicating the Xsan traffic over this single LAN connection).
With the firewall, the situation is more strange. When I try to open the Firewall settings on Sharing, there is a dialog "Other firewall software is running on this computer." I googled this and it seems that this was a common problem on 10.3. They suggest to delete com.apple.sharing.firewall.plist file but it is not there on 10.4.
"sudo ipfw list" shows this:
00001 allow udp from any 626 to any dst-port 626
65535 allow ip from any to any
Any ideas on how to make Firewall behave as expected? I will try to reinstall if I don't receive a reply.
Thanks.

[SOLVED] Cannot mount kindle

I have looked up at different posts on this topic but am still at a loss. I cannot mount a kindle
dmesg
[29881.943452] usb 2-1.5: new high-speed USB device number 75 using ehci-pci
[29882.049006] usb-storage 2-1.5:1.0: USB Mass Storage device detected
[29882.049194] scsi host18: usb-storage 2-1.5:1.0
[29883.051858] scsi 18:0:0:0: Direct-Access Kindle Internal Storage 0100 PQ: 0 ANSI: 2
[29883.061942] sd 18:0:0:0: [sdb] Attached SCSI removable disk
ls -l /dev/disk/by-id/
lrwxrwxrwx 1 root root 9 1. Jän 13:59 usb-Kindle_Internal_Storage_90231702303604DT-0:0 -> ../../sdb
But both mount and fdisk do not see it
fdisk -l /dev/sdb
fdisk: cannot open /dev/sdb: No medium found
Last edited by snovik (2015-01-01 16:41:25)

I have a Gen 2 connected right now, it most definitely uses UMS. I have a Gen 4 at home that also uses UMS. I've got to assume your Gen 3 would as well.
Does it go to the "USB Drive Mode" screen when you plug it in?
Edit: Do remember having an issue one time where it would not go into USB mode. Rebooting the Kindle fixed it. On my Gen 2, you would go to the Home screen, then hit menu and settings, hit menu again and there's an option for "Restart".
Last edited by Scimmia (2015-01-01 15:25:07)

Kernel panic since upgrade to core. Unable to mount root fs on

kernel panic : not syncing; VFS; Unable to mount root fs on unknown-block (0,0)
I get that error since I upgraded archlinux to the latest version. The last time I upgraded before that was while the repos was still named current. Since I upgraded to core that happened.
What should I do? How could I fix this? I have this problem on the fallback kernel too.
Last edited by sokuban (2007-09-23 01:49:57)

Hello All,
I have two hard drives installed in my pc, one is ATA and the other one is a SATA.
ATA is /dev/sda 200GB
SATA os /dev/sdb 40GB
I have installed arch linux onto sdb. grub also is installed to sdb.
Whenever I do a pacman -Syu and reboot I get the kernel panic not synching attempted to kill init error message at boot
I then boot the pc using the fallback image and copied the fallback config to /etc/mkinicpio.conf and ran mkinitcpio -p kernel26 and rebooted. everything works fine. but just running the command pacman -Syu and rebooting will end up with the same problem. though pacman -Syu does not install any updates. what is it that I'm doing wrong?
Thanks
Last edited by xboxer21 (2007-09-28 18:11:36)

Cannot mount any firewire/USB external drive after software update 10.5.4

After the last software update on 10.5.4 it did not complete the installation, and get stuck at the last step of running installation script for hours. So I have to restart the computer, and it restarted fine. Then I use Disk Utility to check my hard disk, and discovered some file system inconsistency error, so I repaired it (in target disk mode by another Mac). After it is repaired, the file system passed with no error.
But ever since then, I cannot mount any external firewire drive or USB drive. I cannot use Time Machine to backup my disk. I think my firewire and USB ports are fine because I can restart my iMac in target mode and connect to my MacBook via firewire, so the hardwire ports are functional, except that it seems 10.5.4 cannot detect or mount any external drive after the failed software update.
Does anyone encounter similar problem? How can I fix it? I have my disk backed up by TimeMachine but I cannot restore it if it won't let me mount my TimeMachine disk. Is there any other way other than completely reinstall 10.5 from scratch?

first, you should try reinstalling 10.5.4. download the [combo update|http://www.apple.com/downloads/macosx/apple/macosx_updates/macosx1054com boupdate.html] and run it. If that doesn't fix the issue, you can use full system restore from TM to go back to a time before the troubles started. to do that boot from the leopard install dvd, once past the language screen go to the Utilities menu at the top and choose "restore from backup".

Disk Utility says everything's fine, but Install disk doesn't find my internal drive as a possible destination. When I startup with Command S, I get a looping "cannot mount errno = 19" message.

Disk Utility says everything's fine, but Install disk doesn't find my internal drive as a possible destination. When I startup with Command + S, I get a looping "cannot mount errno = 19" message.
Problem started when I used Tech Tool Pro 6 to "de-fragment volume". Had to cancel that process before it finished because I ran out of time. Thereafter, when I startup my machine normally, I get the gray Apple logo at first, but it changes to a prohibited symbol (circle with a slash thru it) and hangs.
When I startup holding the Option key, I can see my internal drive, but I get the same results as above.
When I startup using the MacBook OSX Install DVD, it does not find my internal drive as possible destination.
When I startup using the MacBook OSX Install DVD and then run Disk Utility, it finds my drive, allows me to "repair" and says everything is fine.
When I startup with Command + S, I get a looping error message "errno = 19" and cannot stop it to do anything else.
When I startup from Disk Warrior v4.4, it does not find my internal drive to do any repairs.
When I startup from Tech Tool Pro 6 and run the "computer check" diagnostics, everything passes but the Volume Structure, which fails at "Volume Extents (B-tree)." When I use TTP's "Tools" option to run "volume repair" it will show my internal drive and allow me to click the GO button, but nothing happens and nothing changes.
I have a Time Machine backup on an external USB drive, but for as long as the internal drive doesn't mount, I can't use the backup to restore.

It's a false report and should be ignored.
I would not rely on TT as I've already said earlier even before Grant posted similar advice.
I really think the Rigid Disk Block may be corrupted. This holds the partition map and could prevent a volume from being unmounted. Unfortunately, there is no way to fix that without repartitioning the drive which will remove everything. So, before going down this road I hope you have backups or can make a backup.
Drive Partition and Format
1. Boot from your Snow Leopard Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
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. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
4. Quit DU and return to the installer. Proceed with reinstalling OS X.
5. Download and install Mac OS X 10.6.8 Update Combo v1.1.

Cannot mount root

Similar Messages

Maybe you are looking for