Although I think these disks probably died a long time ago and were replaced with external storage.
My new question based on this was, all of this new storage was mounted to "u1 u2 u3 u4" but it doesn't show the block mapping, and i'm not sure where it was set to automount if not in /etc/vfstab?
Code:
# format -e
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@780/pci@0/pci@9/scsi@0/sd@0,0
1. c0t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@780/pci@0/pci@9/scsi@0/sd@1,0
2. c0t2d0 <drive type unknown>
/pci@780/pci@0/pci@9/scsi@0/sd@2,0
3. c0t3d0 <drive type unknown>
/pci@780/pci@0/pci@9/scsi@0/sd@3,0
4. c2t10d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/pci@7c0/pci@0/pci@8/pci@0/scsi@8/sd@a,0
5. c2t11d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/pci@7c0/pci@0/pci@8/pci@0/scsi@8/sd@b,0
6. c3t8d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/pci@7c0/pci@0/pci@8/pci@0/scsi@8,1/sd@8,0
7. c3t9d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/pci@7c0/pci@0/pci@8/pci@0/scsi@8,1/sd@9,0
Specify disk (enter its number): 2
AVAILABLE DRIVE TYPES:
0. Auto configure
1. Quantum ProDrive 80S
2. Quantum ProDrive 105S
3. CDC Wren IV 94171-344
4. SUN0104
5. SUN0207
6. SUN0327
7. SUN0340
8. SUN0424
9. SUN0535
10. SUN0669
11. SUN1.0G
12. SUN1.05
13. SUN1.3G
14. SUN2.1G
15. SUN2.9G
16. Zip 100
17. Zip 250
18. Peerless 10GB
19. SUN72G
20. SUN146G
21. other
Specify disk type (enter its number):
I am getting this error message (sh: No: not found) and I have no idea what line in my unix script its coming from or what it means. Can anyone help?
thanks,
Cindy (2 Replies)
Dear Experts and Advanced User,
I encounter a rare problem as mentioned above. I am not able to read the tape cartridge using the following command:
#dd if=/dev/rmt/0mnb ibs=16k | tar tvf -
It will prompt me with the message saying DD I/O error, broken pipe; everytime the above command is... (2 Replies)
Greetings, using ksh on Solaris, I am trying to identify the current version of a package installed on multiple servers using if statement in a precursor to upgrading.
I have searched the forums and have found many hits, reviewed 3 pages and have tried the different variations noted there. Also... (3 Replies)
Hi folk,
Hope you enjoy the summer.
I am stock after one day working, the problems are the following:
1) I want to write a for loop in a shell script code that has a double precision step as:
#!/bin/bash
START=0.00001
STOP=0.001
for((i = START ; i< STOP ; i=2*i)) do
echo "$i"... (1 Reply)
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Hi Friends,
I set up the sendmail in my perosnal home lab. I am using mutt to send the email in between the machines. Everything is working fine if i send email like <username>@<hostname>. Now i set up the MX record for my domain "home.com" and then i was trying to send the email to like... (2 Replies)
Hi,
I am facing issue with one of the drive is solaris 10. it is showing offline in the messages file
scsi: WARNING: /pci@2,600000/QLGC,qlc@0/fp@0,0/ssd@w5006016746e00b1b,0 (ssd0):
drive offline
genunix: WARNING: Page83 data not standards compliant DGC LUNZ 0430
... (1 Reply)
Hello.
System : opensuse leap 42.3
I have a bash script that build a text file.
I would like the last command doing :
print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt
where :
print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 Replies
LEARN ABOUT NETBSD
pciback
PCIBACK(4) BSD/xen Kernel Interfaces Manual PCIBACK(4)NAME
pciback -- Xen backend paravirtualized PCI pass-through driver
SYNOPSIS
pciback* at pci?
DESCRIPTION
The pciback driver is the backend part of the PCI pass-through functionality that can be used by the Xen dom0 to export pci(4) devices to a
guest domain. To export a PCI device to a guest domain, the device has to be attached to pciback in the dom0.
When the guest domain is NetBSD, the device attached to the pciback driver will attach to a xpci(4) bus inside the guest domain.
EXAMPLES
To attach a device to the pciback driver, follow these steps:
1. look for the device PCI ID, via pcictl(8).
2. edit boot.cfg(5) and add the PCI ID to the list of PCI IDs that you want to attach to pciback, in bus:device.function notation.
The list is passed to dom0 module via the pciback.hide parameter:
pciback.hide=(bus:dev.fun)(bus:dev.func)(...)
See also boot(8).
3. reboot dom0.
4. add the PCI ID to the list of PCI devices in the domain configuration file:
pci = ['bus:dev.fun', '...']
5. start the guest domain.
SEE ALSO pci(4), xpci(4), boot(8), pcictl(8)HISTORY
The pciback driver first appeared in NetBSD 5.1.
AUTHORS
The pciback driver was written by Manuel Bouyer <bouyer@NetBSD.org>.
CAVEATS
Currently, to attach a device to the pciback backend, this procedure has to be performed at boot(8) time. In the future, it will be possible
to do it without requiring a dom0 reboot.
SECURITY CONSIDERATIONS
As PCI passthrough offers the possibility for guest domains to send arbitrary PCI commands to a physical device, this has direct impact on
the overall stability and security of the system. For example, in case of erroneous or malicious commands, the device could overwrite physi-
cal memory portions, via DMA.
BSD January 8, 2011 BSD