Sponsored Content
Operating Systems Solaris Solaris 10 luupgrade flash archive file system creation failed Post 302953254 by hicksd8 on Wednesday 26th of August 2015 10:06:04 AM
Old 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

Solaris 10 flash archive Postdeployment Script

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

flash file system

Can any one suggest me how to start writing a flash file system (2 Replies)
Discussion started by: shivaraj.bh
2 Replies

3. Solaris

Solaris 8 using Flash Archive for Disaster Recovery

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

creat flash archive

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

Flash archive with VxVM

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

What is being backup using Flash Archive on Solaris 10 x86?

:)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

Failed to identify flash rom on Sunfire V240 running Solaris 10

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
csx_MakeDeviceNode(9F)					   Kernel Functions for Drivers 				    csx_MakeDeviceNode(9F)

NAME
csx_MakeDeviceNode, csx_RemoveDeviceNode - create and remove minor nodes on behalf of the client SYNOPSIS
#include <sys/pccard.h> int32_t csx_MakeDeviceNode(client_handle_t ch, make_device_node_t *dn); int32_t csx_RemoveDeviceNode(client_handle_t ch, remove_device_node_t *dn); INTERFACE LEVEL
Solaris DDI Specific (Solaris DDI) PARAMETERS
ch Client handle returned from csx_RegisterClient(9F). dn Pointer to a make_device_node_t or remove_device_node_t structure. DESCRIPTION
csx_MakeDeviceNode() and csx_RemoveDeviceNode() are Solaris-specific extensions to allow the client to request that device nodes in the filesystem are created or removed, respectively, on its behalf. STRUCTURE MEMBERS
The structure members of make_device_node_t are: uint32_t Action; /* device operation */ uint32_t NumDevNodes; /* number of nodes to create */ devnode_desc_t *devnode_desc; /* description of device nodes */ The structure members of remove_device_node_t are: uint32_t Action; /* device operation */ uint32_t NumDevNodes; /* number of nodes to remove */ devnode_desc_t *devnode_desc; /* description of device nodes */ The structure members of devnode_desc_t are: char *name; /* device node path and name */ int32_t spec_type; /* device special type (block or char) */ int32_t minor_num; /* device node minor number */ char *node_type; /* device node type */ The Action field is used to specify the operation that csx_MakeDeviceNode() and csx_RemoveDeviceNode() should perform. The following Action values are defined for csx_MakeDeviceNode(): CREATE_DEVICE_NODE Create NumDevNodes minor nodes The following Action values are defined for csx_RemoveDeviceNode(): REMOVE_DEVICE_NODE Remove NumDevNodes minor nodes REMOVE_ALL_DEVICE_NODES Remove all minor nodes for this client For csx_MakeDeviceNode(), if the Action field is: CREATE_DEVICE_NODE The NumDevNodes field must be set to the number of minor devices to create, and the client must allocate the quan- tity of devnode_desc_t structures specified by NumDevNodes and fill out the fields in the devnode_desc_t structure with the appropriate minor node information. The meanings of the fields in the devnode_desc_t structure are identi- cal to the parameters of the same name to the ddi_create_minor_node(9F) DDI function. For csx_RemoveDeviceNode(), if the Action field is: REMOVE_DEVICE_NODE The NumDevNodes field must be set to the number of minor devices to remove, and the client must allocate the quantity of devnode_desc_t structures specified by NumDevNodes and fill out the fields in the devnode_desc_t structure with the appropriate minor node information. The meanings of the fields in the devnode_desc_t struc- ture are identical to the parameters of the same name to the ddi_remove_minor_node(9F) DDI function. REMOVE_ALL_DEVICE_NODES The NumDevNodes field must be set to 0 and the devnode_desc_t structure pointer must be set to NULL. All device nodes for this client will be removed from the filesystem. RETURN VALUES
CS_SUCCESS Successful operation. CS_BAD_HANDLE Client handle is invalid. CS_BAD_ATTRIBUTE The value of one or more arguments is invalid. CS_BAD_ARGS Action is invalid. CS_OUT_OF_RESOURCE Unable to create or remove device node. CS_UNSUPPORTED_FUNCTION No PCMCIA hardware installed. CONTEXT
These functions may be called from user or kernel context. SEE ALSO
csx_RegisterClient(9F), ddi_create_minor_node(9F), ddi_remove_minor_node(9F) PC Card 95 Standard, PCMCIA/JEIDA SunOS 5.11 19 Jul 1996 csx_MakeDeviceNode(9F)
All times are GMT -4. The time now is 01:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy