Cannot open /dev/rmt/0un (or any other /dev/rmt/??n)

Cannot open /dev/rmt/0un (or any other /dev/rmt/??n)

Post by jgsa.. » Sat, 20 May 2006 02:01:04



(I see this group is much more active)

I've moved an L9 autoloader from a Solaris 9 E250 to a Solaris 9 V120.

I've duplicated the info from st.conf

tape-config-list=
"QUANTUM DLT8000","Quantum DLT8000","DLT8k-data";
DLT8k-data = 1,0x38,0,0x10639,4,0x84,0x85,0x88,0x89,3;

and sgen.conf

device-type-config-list="changer", "sequential"
.....
name="sgen" class="scsi" target=0 lun=0;
name="sgen" class="scsi" target=1 lun=0;
name="sgen" class="scsi" target=2 lun=0;
name="sgen" class="scsi" target=3 lun=0;
name="sgen" class="scsi" target=4 lun=0;
name="sgen" class="scsi" target=5 lun=0;
name="sgen" class="scsi" target=6 lun=0;
name="sgen" class="scsi" target=7 lun=0;
name="sgen" class="scsi" target=8 lun=0;

# ls -la /dev/scsi
total 14
drwxr-xr-x   4 root     other        512 May 16 08:31 .
drwxr-xr-x  15 root     sys         4096 May 17 07:26 ..
drwxr-xr-x   2 root     other        512 May 16 08:31 changer
drwxr-xr-x   2 root     other        512 May 16 08:31 sequential

My problem is every time I do a backup I get the following:

  DUMP: Date of this level 0 dump: Wed May 17 10:44:21 2006
  DUMP: Date of last level 0 dump: the epoch
  DUMP: Dumping /dev/rdsk/c1t0d0s0 (west:/) to /dev/rmt/0un.
  DUMP: Mapping (Pass I) [regular files]
  DUMP: Mapping (Pass II) [directories]
  DUMP: Writing 63 Kilobyte records
  DUMP: Estimated 269898 blocks (131.79MB).
  DUMP: NEEDS ATTENTION: Cannot open `west:/dev/rmt/0un'.  Do you want
to retry the open?: ("yes" or "no") no
  DUMP: The ENTIRE dump is aborted.
  DUMP: Date of this level 0 dump: Wed May 17 10:44:24 2006
  DUMP: Date of last level 0 dump: the epoch
  DUMP: Dumping /dev/rdsk/c1t0d0s4 (west:/var) to /dev/rmt/0un.
  DUMP: Mapping (Pass I) [regular files]
  DUMP: Mapping (Pass II) [directories]
  DUMP: Writing 63 Kilobyte records
  DUMP: Estimated 544350 blocks (265.80MB).
  DUMP: NEEDS ATTENTION: Cannot open `west:/dev/rmt/0un'.  Do you want
to retry the open?: ("yes" or "no")

When the L9 was connected to the E250, I had no problems.  I tried
every /dev/rmt/ that ended with an "n" and all return the same error.

I think I am overlooking something obvious but so far no luck on a
solution.

Thanks!

 
 
 

Cannot open /dev/rmt/0un (or any other /dev/rmt/??n)

Post by Darren Dunha » Sat, 20 May 2006 02:14:05



> My problem is every time I do a backup I get the following:
>   DUMP: Date of this level 0 dump: Wed May 17 10:44:21 2006
>   DUMP: Date of last level 0 dump: the epoch
>   DUMP: Dumping /dev/rdsk/c1t0d0s0 (west:/) to /dev/rmt/0un.
>   DUMP: Mapping (Pass I) [regular files]
>   DUMP: Mapping (Pass II) [directories]
>   DUMP: Writing 63 Kilobyte records
>   DUMP: Estimated 269898 blocks (131.79MB).
>   DUMP: NEEDS ATTENTION: Cannot open `west:/dev/rmt/0un'.  Do you want
> to retry the open?: ("yes" or "no") no

Are you running the ufsdump on the new machine with the tape drive or
trying to send the data over the network?

You don't post the actual ufsdump command.  Please do.

--

Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

 
 
 

Cannot open /dev/rmt/0un (or any other /dev/rmt/??n)

Post by Oscar del Ri » Sat, 20 May 2006 02:56:05



> (I see this group is much more active)

than what?  :)

Quote:> When the L9 was connected to the E250, I had no problems.  I tried
> every /dev/rmt/ that ended with an "n" and all return the same error.

devfsadm

mt -f /dev/rmt/0 status

 
 
 

Cannot open /dev/rmt/0un (or any other /dev/rmt/??n)

Post by jgsa.. » Sat, 20 May 2006 05:06:52


# devfsadm
# mt -f /dev/rmt/0 status
/dev/rmt/0: No such device or address

Quote:>>Are you running the ufsdump on the new machine with the tape drive or

trying to send the data over the network?

New machine with the tape drive connected via scsi cable

Quote:>>You don't post the actual ufsdump command.  Please do.

ufsdump 0ucf /dev/rmt/0un /
ufsdump 0ucf /dev/rmt/0un /var
ufsdump 0ucf /dev/rmt/0un /usr
ufsdump 0ucf /dev/rmt/0un /a

Quote:>>.than what?  :)

more active than the "solaris admin" group
 
 
 

Cannot open /dev/rmt/0un (or any other /dev/rmt/??n)

Post by Oscar del Ri » Sat, 20 May 2006 05:37:53



> # devfsadm
> # mt -f /dev/rmt/0 status
> /dev/rmt/0: No such device or address

are there any other devices in /dev/rmt/  (1,2,3?)

does the drive show at the OBP's "probe-scsi-all"?

it looks like the device is not communicating. check scsi cables,
scsi IDs, termination, power-cycle it... the usual.

one (third-party) library we have sometimes loses the scsi ID of one of
the drives and we have to manually reset it by changing it to a free ID
and then back to the regular one (usually after a cold power-cycle)

 
 
 

Cannot open /dev/rmt/0un (or any other /dev/rmt/??n)

Post by Cesar » Sat, 20 May 2006 14:55:18




Quote:> # devfsadm
> # mt -f /dev/rmt/0 status
> /dev/rmt/0: No such device or address

Have you run commands: drvconfig, disks, tape ?

Please post the content of /dev/rmt directory

Cesare

 
 
 

Cannot open /dev/rmt/0un (or any other /dev/rmt/??n)

Post by from the » Sat, 20 May 2006 20:36:18



> (I see this group is much more active)

> I've moved an L9 autoloader from a Solaris 9 E250 to a Solaris 9 V120.

Can we assume you moved the HVD SCSI controller too?

--
Dave K     MCSE.

MCSE = Minefield Consultant and Solitaire Expert.

Please note my email address changes periodically to avoid spam.

for a couple of months only. Later set it manually.

 
 
 

Cannot open /dev/rmt/0un (or any other /dev/rmt/??n)

Post by jgsa.. » Sat, 20 May 2006 23:37:47


Yeah, I saw the device when I ran the probe-scsi-all.  That's when it
showed up.

# ls -la /dev/rmt
total 106
drwxr-xr-x   2 root     sys         1024 May 12 10:07 .
drwxr-xr-x  15 root     sys         4096 May 18 13:03 ..
lrwxrwxrwx   1 root     other         45 Apr 10 08:24 0 ->

lrwxrwxrwx   1 root     other         46 Apr 10 08:24 0b ->

lrwxrwxrwx   1 root     other         47 Apr 10 08:24 0bn ->

lrwxrwxrwx   1 root     other         46 Apr 10 08:24 0c ->

lrwxrwxrwx   1 root     other         47 Apr 10 08:24 0cb ->

lrwxrwxrwx   1 root     other         48 Apr 10 08:24 0cbn ->

lrwxrwxrwx   1 root     other         47 Apr 10 08:24 0cn ->

lrwxrwxrwx   1 root     other         46 Apr 10 08:24 0h ->

lrwxrwxrwx   1 root     other         47 Apr 10 08:24 0hb ->

lrwxrwxrwx   1 root     other         48 Apr 10 08:24 0hbn ->

lrwxrwxrwx   1 root     other         47 Apr 10 08:24 0hn ->

lrwxrwxrwx   1 root     other         46 Apr 10 08:24 0l ->

lrwxrwxrwx   1 root     other         47 Apr 10 08:24 0lb ->

lrwxrwxrwx   1 root     other         48 Apr 10 08:24 0lbn ->

lrwxrwxrwx   1 root     other         47 Apr 10 08:24 0ln ->

lrwxrwxrwx   1 root     other         46 Apr 10 08:24 0m ->

lrwxrwxrwx   1 root     other         47 Apr 10 08:24 0mb ->

lrwxrwxrwx   1 root     other         48 Apr 10 08:24 0mbn ->

lrwxrwxrwx   1 root     other         47 Apr 10 08:24 0mn ->

lrwxrwxrwx   1 root     other         46 Apr 10 08:24 0n ->

lrwxrwxrwx   1 root     other         46 Apr 10 08:24 0u ->

lrwxrwxrwx   1 root     other         47 Apr 10 08:24 0ub ->

lrwxrwxrwx   1 root     other         48 Apr 10 08:24 0ubn ->

lrwxrwxrwx   1 root     other         47 Apr 10 08:24 0un ->

lrwxrwxrwx   1 root     root          43 May 12 10:07 1 ->

lrwxrwxrwx   1 root     root          44 May 12 10:07 1b ->

lrwxrwxrwx   1 root     root          45 May 12 10:07 1bn ->

lrwxrwxrwx   1 root     root          44 May 12 10:07 1c ->

lrwxrwxrwx   1 root     root          45 May 12 10:07 1cb ->

lrwxrwxrwx   1 root     root          46 May 12 10:07 1cbn ->

lrwxrwxrwx   1 root     root          45 May 12 10:07 1cn ->

lrwxrwxrwx   1 root     root          44 May 12 10:07 1h ->

lrwxrwxrwx   1 root     root          45 May 12 10:07 1hb ->

lrwxrwxrwx   1 root     root          46 May 12 10:07 1hbn ->

lrwxrwxrwx   1 root     root          45 May 12 10:07 1hn ->

lrwxrwxrwx   1 root     root          44 May 12 10:07 1l ->

lrwxrwxrwx   1 root     root          45 May 12 10:07 1lb ->

lrwxrwxrwx   1 root     root          46 May 12 10:07 1lbn ->

lrwxrwxrwx   1 root     root          45 May 12 10:07 1ln ->

lrwxrwxrwx   1 root     root          44 May 12 10:07 1m ->

lrwxrwxrwx   1 root     root          45 May 12 10:07 1mb ->

lrwxrwxrwx   1 root     root          46 May 12 10:07 1mbn ->

lrwxrwxrwx   1 root     root          45 May 12 10:07 1mn ->

lrwxrwxrwx   1 root     root          44 May 12 10:07 1n ->

lrwxrwxrwx   1 root     root          44 May 12 10:07 1u ->

lrwxrwxrwx   1 root     root          45 May 12 10:07 1ub ->

lrwxrwxrwx   1 root     root          46 May 12 10:07 1ubn ->

lrwxrwxrwx   1 root     root          45 May 12 10:07 1un ->

As far as the card, I did move it over.

 
 
 

Cannot open /dev/rmt/0un (or any other /dev/rmt/??n)

Post by jgsa.. » Sat, 20 May 2006 23:44:20


I should add that I can currently control the autoloader using MTX.  I
can load and unload tapes into the drive and return a "status".
 
 
 

Cannot open /dev/rmt/0un (or any other /dev/rmt/??n)

Post by Thomas Schu » Sun, 21 May 2006 01:31:09





>> # devfsadm
>> # mt -f /dev/rmt/0 status
>> /dev/rmt/0: No such device or address

>are there any other devices in /dev/rmt/  (1,2,3?)

>does the drive show at the OBP's "probe-scsi-all"?

>it looks like the device is not communicating. check scsi cables,
>scsi IDs, termination, power-cycle it... the usual.

>one (third-party) library we have sometimes loses the scsi ID of one of
>the drives and we have to manually reset it by changing it to a free ID
>and then back to the regular one (usually after a cold power-cycle)

Unless you did a reconfiguration reboot or ran the devfsadm command,
the system will not know about the tape drive.  The devfsadm command
replaces the older drvconfig, disks, tapes & devlinks commands.
The older commands should still work, but devfsadm is preferred.
--
Tom Schulz

 
 
 

Cannot open /dev/rmt/0un (or any other /dev/rmt/??n)

Post by jgsa.. » Wed, 24 May 2006 03:36:55


I have a resolution.

I mv'd /dev/rmt to /dev/rmt.old  and ran devfsadm again to recreate
/dev/rmt

This time when I ran the backup, it had no problem recognizing the
drive.

Thanks for all your help guys!

Jim

 
 
 

1. /dev/rmt/0cbn or /dev/rmt/0mbn?

I'm gonna try it for myself anyway, but in Networker 5.0.1, the device listed
for my tape backup device is /dev/rmt/0mbn.

The drive is a Sun DLT 4700, with a native capacity of 20GB per tape, 40GB
compressed. I always seem to get between 19GB and 21GB on a tape. The problem
is, most of the data being backed up is highly-compressible ASCII source code!
Obviously, there is no compression going on here.

If I use /dev/rmt/0cbn instead of 0mbn, shouldn't I be able to get more than
20GB of ASCII data on a tape?

2. Helpppp before i go back to using NT!!!

3. tape device bulebud01 / 57 <> mt status /dev/rmt/3n /dev/rmt/0n: Device busysy?

4. Unix - Frequently Asked Questions (Contents) [Frequent posting]

5. Cannot open /dev/rmt/0

6. printing problem in Redhat

7. tape drive /dev/rst11 instead of /dev/rmt/0

8. linux quotas

9. What is the difference between /dev/rmt/0 and /dev/rst5?

10. Can not open dev/rmt/0n

11. Linux rmt incompatible with Solaris rmt

12. Empty /dev/rmt on Solaris 2.1 / x86 HELP

13. Slow writes to /dev/rmt/0c