Could the device naming be different between the failsafe and regular kernels?It's panicing when vfs_mountroot calls rootconf.Any tips much appreciated! 8747Views Tags: none (add) This content has been marked as final. But also your network interfaces have been changed and replaced with different models, so we must update your network configuration files. Any man[ual], white-paper, ARC case materias for this project ? -- Regards, Cyril Next Message by Thread: Odd pmap output Howdy, I ran into a weird issue today while playing around console login: root Password: Step 12:Now time to create the original metadevices and restore the server as original.
A. debugger entered. Re: zfs boot issues Cindys-Oracle Jan 31, 2014 4:21 PM (in response to dabih) Good job fixing this problem.
FCode UFS Reader 1.12 00/07/17 15:48:16. XXX=/[email protected],0/pci1000,[email protected]/[email protected],0:a in my case)5) TERM=sun-color; export TERMThis will make using vi easier.6) vi /a/boot/solaris/bootenv.rcupdate property "bootpath" (from above):setprop bootpath XXXin my case it was:setprop bootpath /[email protected],0/pci1000,[email protected]/[email protected],0:a7) cp /etc/path_to_inst /a/etc/path_to_inst8) rm /a/etc/devices/*9) Being no choice we stick with the same version and tried to recover and later we did.. It's probably c2t0d0s0 Touch up /etc/vfstab to use the /dev/* paths which correspond to your disk (don't forget to update the swap entry as well, using the same txdxsx with the
we tried with the net -boot options also but no luck. Both disks was 76G (or something like this). What is the output of the format utility?Also check the boot-device parameter in OBP, maybe you need to change the aliases to point to the new disks.Regards,Rei Like Show 0 Likes(0) http://www.unix.com/hardware/197245-cannot-mount-root-panic.html Some steps found under http://communities.vmware.com/thread/99064 Posts navigation ← Install grub in Solaris Activate gdm in solaris 10 → Leave a Reply Cancel reply Your email address will not be published.
DEBUG enabled features: 10e7fdf
You can not post a blank message. https://forums.gentoo.org/viewtopic-t-1046108.html?sid=5915935a78925a3850b380e35cffe49e Re: Converted Solaris image panics "cannot mount root path" radman Aug 20, 2007 12:12 PM (in response to radman) I figured this out. c1t1d0
More discussions in Solaris 10 All PlacesServer & Storage SystemsOracle SolarisSolaris 10 This discussion is archived 8 Replies Latest reply on Jan 31, 2014 4:21 PM by Cindys-Oracle zfs boot issues http://ecoflashapps.com/cannot-mount/cannot-mount-root-on-pseudo.html Please type your message and try again. I took a look (under the failsafe kernel) at the vfstab, and it looked funky (the / device name was something like /dev/dsk/c1td1s0), so I changed it to match the name The Hard Disk is "SCSI(0:0) Hard Disk 1" according to Settings.
Like Show 0 Likes (0) Actions 4. It can be something like:/devices/[email protected],0/pci1000,[email protected]/[email protected],0:a I'll use XXX to represent your pathname after /devices/ below just in case (e.g. At second step I've replaced remained small disk with bigger new one.As result I've got old zfs pool with totaly new disks. this contact form c1t0d0
siegfried UNIX for Dummies Questions & Answers 11 03-17-2007 11:36 PM unixware 7.1.3 can't mount root hushboy UNIX for Advanced & Expert Users 1 10-22-2005 09:46 AM Panic message with mount. path used for the root disk.In my case this was /devices/[email protected],0/pci1000,[email protected]/[email protected],0:aI don't know if this will vary, it may always be this path after Converter runs.I'll use XXX to represent your y CG 164: IMPOSSIBLE NUMBER OF CYLINDERS IN GROUP (0 is less than 1) REPAIR?
At the moment it's just stuck in a loop of Reboot-panic-reboot. The contents of this document, unless otherwise expressly stated, are licensed under the CC-BY-SA-3.0 license. FCode UFS Reader 1.12 00/07/17 15:48:16. Cannot mount root on /pseudo/[email protected]:0,0,blk fstype ufs panic[cpu0]/thread=140a000: vfs_mountroot: cannot mount root 0000000001409970 genunix:vfs_mountroot+70 (0, 0, 0, 200, 14a8270, 0) %l0-3: 000000000149bc00 000000000149bc00 0000000000002000 00000000014e5b00 %l4-7: 00000000014eb800 0000000001422568 000000000149c400 000000000149f400 0000000001409a20
WARNING: /[email protected],0/[email protected],600000/[email protected]/[email protected],0 (sd30): Error for Command: read(10) Error Level: Retryable Requested Block: 286637632 Error Block: 286637632 Vendor: SEAGATE Serial Number: 0534424F0E Sense Key: Media Error ASC: 0x11 (unrecovered read error), ASCQ: I'm able to boot server in failsafe mode and successfuly import zfs-pool. gentoo.org sites gentoo.org Wiki Bugs Forums Packages Planet Archives Sources Infra Status Wiki Toggle navigation Main pageRecent changesHelp Gentoo Gentoo Projects Documentation Gentoo HandbookGentoo FAQFeatured DocumentsTopicsCore systemHardwareSoftwareDesktopServer & SecurityProject & Community Step6: copy the current bootpath: [email protected] # prtconf -vp|grep bootpath bootpath: ‘/[email protected],0/[email protected],600000/[email protected]/[email protected],0:a' Step6: commented all MD entries in /a/etc/vfstab and made a new entry of original device paths for mounting /
Unretrieved lom log history follows … 12/13/11 2:12:09 AM Domain Reboot A: Initiating keyswitch: on, domain A. Re: Converted Solaris image panics "cannot mount root path" MPowerLabs Nov 10, 2008 1:57 PM (in response to publish_or_perish) The above posts where very helpful. Move down to the 2nd (kernel) line, and type ‘e' to edit it Append "-r -s" to force device reconfiguration and boot single-user, then press Return, to return to the previous screen Attempting to configure interface ce5… Skipped interface ce5 Attempting to configure interface ce4… Skipped interface ce4…………………………………………………… output truncated… SINGLE USER MODE we checked the current update of Solaris 10 OS at
Anyone have any suggestions? Re: Converted Solaris image panics "cannot mount root path" acruizu Sep 3, 2008 9:45 AM (in response to publish_or_perish) Thank you very much. First created the root file system, since /var was part of root so did not create metadevice for /var. os-io Hardware watchdog enabled Booting to milestone "milestone/single-user:default".
value for your disk). Use is subject to license terms. Type ^D to go to multi-user Done! Thanks for any insight, - Ryan  #include
I had a problem with the file reverting back to the original boot device. Cannot mount root on /pseudo/[email protected]:0,0,blk fstype ufs panic[cpu0]/thread=140a000: vfs_mountroot: cannot mount root 0000000001409970 genunix:vfs_mountroot+70 (0, 0, 0, 200, 14a8270, 0) %l0-3: 000000000149bc00 000000000149bc00 0000000000002000 00000000014e5b00 %l4-7: 00000000014eb800 0000000001422568 000000000149c400 000000000149f400 0000000001409a20