Sponsored Content
Operating Systems Solaris Sun Fire 480 - devfsadm -C not working after replacing one of the boot disks Post 302912496 by hicksd8 on Friday 8th of August 2014 02:39:24 PM
Old 08-08-2014
As I already said in post#4, if you really think it necessary, you can delete a device node by using:

Code:
# rm -f /dev/dsk/<device node>

You should also remove the same device node from /dev/rdsk and /dev/cfg
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Sun Fire v1280 is crashing

I still haven't got an answer to this question... Excerpt from My SysAd Blog A colleague of mine is having a problem with a Sun Fire v1280 server crashing. He tried Googling for the error message in red but hasn't found anything yet. Your insights would be greatly appreciated. "cannot... (2 Replies)
Discussion started by: esofthub
2 Replies

2. UNIX for Dummies Questions & Answers

Sun Fire 280R

Hello all, I'm lost and can't figure this problem out. I have a Sun fire 280R running Solaris 8. Everything was working great. I have one drive in bay 1(not 0). But when I reboot the system it trys to open files in /dev/rdsk/c1t1d0s0. Should it have been opeing /dev/rdsk/c1t0d0s0, the... (4 Replies)
Discussion started by: larryase
4 Replies

3. Solaris

Sun Fire v440 keeps shutting down

Hello, I hope you can help me. I am new to Sun servers and we have a Sun Fire v440 server in which one power supply failed, we are waiting for new one. But now our server is shutting down constantly. Is there any setting with which we can prevent this behaviour? (1 Reply)
Discussion started by: Tibor
1 Replies

4. Solaris

Sun Fire won't boot anymore

Hi all - I have an issue with our (way old) single processor SunFire 280R, running Solaris 9.0.4. It won't boot even after multiple power cycles. There was a power outage last week end in the computer room, so this might have to do. In normal boot mode, the screen shows a single line : ... (5 Replies)
Discussion started by: bostella
5 Replies

5. Solaris

Sun Fire 280R Sun Solaris CRT/Monitor requirements

I am new to Sun. I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor? Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies

6. Solaris

Error while trying to boot from cdrom on Sun Fire T2000

Hi Guyz, I recently downloaded sol-10-u6-ga1-sparc-dvd.iso from Sun. I burned the disk as cd .iso. When trying to boot at the ok> boot cdrom i get the following error: ----------------------------------------------------------------------- Boot device:... (2 Replies)
Discussion started by: Mwamba
2 Replies

7. Solaris

Sun-Fire V440 boot disk issue

Hi, I have Sun Fire V440. Boot disks are mirrored. system crashed and it's not coming up. Error message is Insufficient metadevice database replicas located. Use Metadb to delete databases which are broken. Boot disks are mirrored and other disks are ZFS configuration. Please... (2 Replies)
Discussion started by: samnyc
2 Replies

8. Solaris

Sun Fire 4800 is not powering-on

I switched on the power to the server. But, the server did not power on i.e., none of the 3 LEDs on the front panel is lighted. (Power supplies are showing only amber LEDs with "Ready to remove" sign). I tried to turn on the power supplies via System Controller menu (platform shell), but it... (6 Replies)
Discussion started by: solind
6 Replies

9. Solaris

Sun fire x2270

Hello, I have purchaced an old SUn fire x2270 server . I wanted to make ILOM upgrade to the latest version of software : ILOM 3.0.9.18.a r126592 BIOS vers. 2.09 Server 2.2.3 (10-Aug-2018) Because my version is very outdated. But i can't download the updatebecause it's require... (4 Replies)
Discussion started by: LouisLakoute
4 Replies
NG_DEVICE(4)						   BSD Kernel Interfaces Manual 					      NG_DEVICE(4)

NAME
ng_device -- device netgraph node type SYNOPSIS
#include <netgraph/ng_device.h> DESCRIPTION
A device node is both a netgraph node and a system device interface. When a device node is created, a new device entry appears which is accessible via the regular file operators such as open(2), close(2), read(2), write(2), etc. The first node is created as /dev/ngd0, all subsequent nodes /dev/ngd1, /dev/ngd2, etc. HOOKS
A device node has a single hook with an arbitrary name. All data coming in over the hook will be presented to the device for read(2). All data coming in from the device entry by write(2) will be forwarded to the hook. CONTROL MESSAGES
The device node supports one non-generic control message: NGM_DEVICE_GET_DEVNAME Returns device name corresponding to a node. SHUTDOWN
This node shuts down upon receipt of a NGM_SHUTDOWN control message, or upon hook disconnection. The associated device entry is removed and becomes available for use by future device nodes. SEE ALSO
netgraph(4), ngctl(8) HISTORY
The device node type was first implemented in FreeBSD 5.0. AUTHORS
Mark Santcroos <marks@ripe.net> Gleb Smirnoff <glebius@FreeBSD.org> BSD
October 19, 2004 BSD
All times are GMT -4. The time now is 01:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy