Hello Uwe, > [i]did you do a devfsadm after plugging in the drive?[/i] > > Sean, > > of course not! I have only been on Unix and Linux for 10 years, but not on > Solaris; and therefore completely ignorant of the mere existence of that > command! >
10 years? Still a novice, then? ;-) Me too, after 20 (I still have a working Altos 986 running XENIX 3.0b) ;-} devfsadm/devfsadmd is a comparatively new introduction. Its predecessor was use of disks/tapes and then devlinks. > Thanks a bunch! And now it works ... > I'm very happy. > [I do wonder, though, why it is necessary to do so manually, the drive showed > anywhere else (other OSes, I mean), when I panickedly thought it was DOA. It > was not.] > We have all at some time panicked over "dead/DOA" hardware, and later found that it was in fact defective grey cells. Don't worry. It has always been necessary to do some of this stuff manually > Now I wonder if my earlier batch of troubles with weird behaviour of LU might > have had to do with me ignorantly plugging drives about without ever using > this command (boot archive and format would point to different drives)? > Before, the old DVD was always /dev/rdsk/c0t1d0 against all odds: it is the > one and only IDE and I always expected it to be on c0t0d0. Now, finally, it > is. As Ron said, when jiggling around hardware, doing a reconfiguration boot is always recommended. devfsadm also has a useful switch "-C" (cap-c), which also cleans out unused device nodes; thus making your /dev and /devices actually reflect the state of your system at the time of executing the command. A common invocation would thus be "devfsadm -Cvc disk" after adding new drive(s). Regards... Sean.
