08-26-2015
Nearly a whole day and no replies so I'll try to get some dialogue going here.
I think the issue is occurring because of the change of hardware and the fact that all device nodes (/dev/rdsk/<node>) are going to be different from the original hardware. This is always a bit complex.
Therefore when it tries to create a filesystem on the original device node it's not there. This is also true if you were to try and boot from the new root filesystem.
I think therefore you may need to manage the creation of the new device nodes.
You are a new member on this forum so I have no clue how much Solaris experience you are carrying and therefore how easy you will find this to resolve.
You may well get some better answers than this but thought I'd chip in due to the lack of responses.
7 More Discussions You Might Find Interesting
1. Solaris
http://docs.sun.com/app/docs/doc/819-5779/6n7rcfdn1?a=view
-------------------------------------------------
To Create a Reboot Script
This script is kept in the archive and runs after the system is rebooted. The script does any final configuration after system reconfiguration.
After you... (0 Replies)
Discussion started by: kungpow
0 Replies
2. Programming
Can any one suggest me how to start writing a flash file system (2 Replies)
Discussion started by: shivaraj.bh
2 Replies
3. Solaris
Hello everyone I am Kevin and new to this forum.
I have encounter an issue I can't seem to resolve. I am currently using Solaris 8 02/04 on Sun V240 servers. I know how to create a flar image of the server and restore it using NFS (network server) or Local Tape (tape drive). What I need to do... (2 Replies)
Discussion started by: Kevin1166
2 Replies
4. Solaris
I want take a flash backup by flar command for specific files like:
/ , /boot, /tmp
I am trying this command but its not working
# flar -n archive1 -f /,/boot,/tmp -F -c /home/arc1.flar
Please can any body help me __.____._ (2 Replies)
Discussion started by: kmuqalled
2 Replies
5. Solaris
I'm writing a design doc and I got this feedback.
"Apparently flash archives have issues with VXVM root F/S's - May also impact licensing for “kick” systems. SVM may be more sensible / flexible option"
The VxVM will be use global zones. i intend on using flash archives of solaris 8/9... (3 Replies)
Discussion started by: frustin
3 Replies
6. Solaris
:)Hi Solaris Specialists,
I need to carry out a disaster recovery backup using Solaris 10 x86 Flash Archive (flarcreate - http://docs.oracle.com/cd/E18752_01/html/821-1912/flashoverview-2.html) on a critical productin server where maintenance downtime is reduced to a minimal. Only 2 filesystems... (5 Replies)
Discussion started by: gjackson123
5 Replies
7. Solaris
Hi Guys,
I have performed OBP & ALOM upgrade on V240 system. One of my system, running Solaris 10, having issue to identify flash rom during ALOM 1.6.10 version upgrade (OBP upgraded to latest one).
May I know what the reason of this error and how can I fix it so I can upgrade ALOM using... (0 Replies)
Discussion started by: myrpthidesis
0 Replies
LEARN ABOUT SUSE
debugreiserfs
DEBUGREISERFS(8) System Manager's Manual DEBUGREISERFS(8)
NAME
debugreiserfs - The debugging tool for the ReiserFS filesystem.
SYNOPSIS
debugreiserfs [ -dDJmoqpuSV ] [ -j device ] [ -B file ] [ -1 N ]
device
DESCRIPTION
debugreiserfs sometimes helps to solve problems with reiserfs filesystems. When run without options it prints the super block of the Reis-
erFS filesystem found on the device.
device is the special file corresponding to the device (e.g /dev/hdXX for an IDE disk partition or /dev/sdXX for a SCSI disk partition).
OPTIONS
-j device
prints the contents of the journal. The option -p allows it to pack the journal with other metadata into the archive.
-J prints the journal header.
-d prints the formatted nodes of the internal tree of the filesystem.
-D prints the formatted nodes of all used blocks of the filesystem.
-m prints the contents of the bitmap (slightly useful).
-o prints the objectid map (slightly useful).
-B file
takes the list of bad blocks stored in the internal ReiserFS tree and translates it into an ascii list written to the specified
file.
-1 blocknumber
prints the specified block of the filesystem.
-p extracts the filesystem's metadata with debugreiserfs -p /dev/xxx | gzip -c > xxx.gz. None of your data are packed unless a filesys-
tem corruption presents when the whole block having this corruption is packed. You send us the output, and we use it to create a
filesystem with the same strucure as yours using debugreiserfs -u. When the data file is not too large, this usually allows us to
quickly reproduce and debug the problem.
-u builds the ReiserFS filesystem image with gunzip -c xxx.gz | debugreiserfs -u /dev/image of the previously packed metadata with
debugreiserfs -p. The result image is not the same as the original filesystem, because mostly only metadata were packed with debu-
greiserfs -p, but the filesystem structure is completely recreated.
-S When -S is not specified -p deals with blocks marked used in the filesystem bitmap only. With this option set debugreiserfs will
work with the entire device.
-q When -p is in use, suppress showing the speed of progress.
AUTHOR
This version of debugreiserfs has been written by Vitaly Fertman <vitaly@namesys.com>.
BUGS
Please report bugs to the ReiserFS developers <reiserfs-dev@namesys.com>, providing as much information as possible--your hardware, kernel,
patches, settings, all printed messages; check the syslog file for any related information.
SEE ALSO
reiserfsck(8), mkreiserfs(8)
Reiserfsprogs 3.6.21 January 2009 DEBUGREISERFS(8)