VxVM : Can't open /dev/vx/rdsk/bootdg/rootvol
in [Solaris]
|
Prev: SMC and JAVA error
Next: Solaris 10 as openldap client
From: M.H on 19 May 2005 04:46 Hi, When the server started, it drops on the maintenance shell because it can't mount the /dev/vx/rdsk/bootdg/rootvol. Trying to do a "fsck -F ufs ..." did not help. Any hints please ! The output of some vxvm commands (on the maintenace shell ): bash-2.03# mount /dev/vx/rdsk/bootdg/rootvol /mnt mount: /dev/vx/rdsk/bootdg/rootvol not a block device bash-2.03# fsck -F ufs /dev/vx/rdsk/bootdg/rootvol Can't open /dev/vx/rdsk/bootdg/rootvol bash-2.03# vxdg list NAME STATE ID rootdg enabled 1021303648.6.lerenan bash-2.03# vxdiskadm VxVM vxdiskadm ERROR V-5-2-3540 Cannot create lock file /var/spool/locks/.DISKAD D.LOCK ================ bash-2.03# vxprint -Ath Disk group: rootdg DG NAME NCONFIG NLOG MINORS GROUP-ID ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK CO NAME CACHEVOL KSTATE STATE VT NAME NVOLUME KSTATE STATE V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE DC NAME PARENTVOL LOGVOL SP NAME SNAPVOL DCO dg rootdg default default 63000 1021303648.6.lerenan dm rootdg01 c0t1d0s2 auto 9423 35358848 - dm rootdg02 c0t0d0s2 auto 9423 35358848 - v rootdg023vol - DISABLED ACTIVE 103664 ROUND - gen pl rootdg023vol-01 rootdg023vol DISABLED ACTIVE 103664 CONCAT - RW sd rootdg02-03 rootdg023vol-01 rootdg02 35250472 103664 0 c0t0d0 ENA pl rootdg023vol-02 rootdg023vol DISABLED ACTIVE 103664 CONCAT - RW sd rootdg01-03 rootdg023vol-02 rootdg01 35222200 103664 0 c0t1d0 ENA v rootvol - ENABLED ACTIVE 33158344 ROUND - root pl rootvol-01 rootvol ENABLED ACTIVE 33158344 CONCAT - RW sd rootdg02-02 rootvol-01 rootdg02 2092128 33158344 0 c0t0d0 ENA pl rootvol-02 rootvol ENABLED ACTIVE 33158344 CONCAT - RW sd rootdg01-02 rootvol-02 rootdg01 2063856 33158344 0 c0t1d0 ENA v swapvol - ENABLED ACTIVE 2063856 ROUND - swap pl swapvol-01 swapvol ENABLED ACTIVE 2063856 CONCAT - RW sd rootdg02-01 swapvol-01 rootdg02 0 2063856 0 c0t0d0 ENA pl swapvol-02 swapvol ENABLED ACTIVE 2063856 CONCAT - RW sd rootdg01-01 swapvol-02 rootdg01 0 2063856 0 c0t1d0 ENA ======== BR haed
From: neo4897 on 19 May 2005 10:11 you should try /usr/lib/fs/vxfs/fsck /dev/??? or fsck -F vxfs /dev/********** VJ
From: Darren Dunham on 19 May 2005 13:03 M.H <haed98(a)excite.com> wrote: > The output of some vxvm commands (on the maintenace shell ): > bash-2.03# mount /dev/vx/rdsk/bootdg/rootvol /mnt > mount: /dev/vx/rdsk/bootdg/rootvol not a block device Don't mount the 'rdsk' device, mount the 'dsk' device. That's the 'not a block device' error. > bash-2.03# fsck -F ufs /dev/vx/rdsk/bootdg/rootvol > Can't open /dev/vx/rdsk/bootdg/rootvol Why do both of these commands have "bootdg" in them when everything in your output is in the "rootdg" diskgroup? Is there a typo in your /etc/vfstab? > bash-2.03# vxdg list > NAME STATE ID > rootdg enabled 1021303648.6.lerenan ....as verified right there. -- Darren Dunham ddunham(a)taos.com Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. >
From: Darren Dunham on 19 May 2005 13:04 neo4897 <vinayjs(a)gmail.com> wrote: > you should try /usr/lib/fs/vxfs/fsck /dev/??? or fsck -F vxfs > /dev/********** No. VxFS can never be used as a boot filesystem. He's using a UFS filesystem. -- Darren Dunham ddunham(a)taos.com Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. >
From: Colin B. on 19 May 2005 13:37
M.H <haed98(a)excite.com> wrote: > Hi, > > When the server started, it drops on the maintenance shell because it > can't mount the /dev/vx/rdsk/bootdg/rootvol. It's not bootdg, it's rootdg. Note that the Veritas commands are all giving you information on volumes in rootdg, and your Sun error messages are complaining about bootdg. I suspect you have this mythical bootdg in /etc/vfstab as well. Colin |