Ok so from the LPAR you are trying to find the CDROM run a lsdev -Cl cd0 -F parent
On one of my S824-42A's this is the path to the CD drive:
So, when you look at the HMC, the optical drive is hanging off P1-C14-T1.
This is why bakunin was saying VIO's make this easier. You could virtualize the optical drive and dynamically add it to any lpar. The above example I gave was from a box with no VIO. 100% of resources of the frame given to the lpar.
Last edited by RecoveryOne; 06-14-2019 at 10:11 AM..
After upgrading to solaris 10 (from sol 8) on a SUN Blade 1500, it seems that the dvd/cd-rom does not accept dvds nor cds in the dvd drive.
After I insert a dvd/cd in the drive, the disk is simply ejected (!)
Is it possible that the upgrade made the system not being able to recognize these... (2 Replies)
I would like to check for the existance of media in a DVD drive prior to running a mkcd. Is this possible? I have accomplished this in the past with tctl, but that was with a tape drive. Any help is appreciated.
Thanks (0 Replies)
Hi there
In our Data centre we have a mixture of SPARCS running from v100 and ultra10's to v800 and v1250 boxes we also have a large amount of x86 X2100 and X4100 boxes
I am looking to purchase an external DVD-ROM drive that we can plug into the back of any of the boxes if we need to (I... (2 Replies)
Hello,
It's some tool in AIX to check what kind of media (DVD+RW DVD-RW DVD-RAM) is inserted in drive?
In linux there is very nice tool called dvd+rw-mediainfo. (0 Replies)
I was having problems with the DVD-ROM drive not being recognized. I thought it was a configuration issue, but it appears to be a hardware problem. Now the system hangs at boot. This last time I tried it, it said:
At which point, it hangs. (1 Reply)
Currently have an issue were we use a script to load a security .dat key. The script was failing to load stating "Unable to open directory". I ssh'd into the server and performed an ls -la on the /cdrom directory. I show the usual cdrom0 but the directory on the cd should be key but is showing... (0 Replies)
I'm a technician who has been called upon to troubleshoot an ancient HP9000 K260, running HP UX 11.11.
After a power sag/crash/restart FSCK gave multiple error/warning messages about logical volumes and groups. I have some modest experience with Unix servers, but not on such an old and... (2 Replies)
Hi Guys,
I think i probably know the answer to this question, but ill put it out there.
I have access to one, and only one SunFire v240 with no DVD drive. I have been tasked with installing Solaris 10 on there (Solaris 8 is on at the moment).
The obvious thing was to try a USB DVD... (4 Replies)
· Next, you will need to install the software package that provides DHCP services (a.k.a. the DHCP daemon software). It is located on the installation DVD ISO image for the CentOS Linux Distribution. Associate the (Disc 1 of 2) DVD ISO with the virtual machine's CD/DVD optical drive, create a... (1 Reply)
Discussion started by: beerpong1
1 Replies
LEARN ABOUT FREEBSD
recoverdisk
RECOVERDISK(1) BSD General Commands Manual RECOVERDISK(1)NAME
recoverdisk -- recover data from hard disk or optical media
SYNOPSIS
recoverdisk [-b bigsize] [-r readlist] [-s interval] [-w writelist] source [destination]
DESCRIPTION
The recoverdisk utility reads data from the source file until all blocks could be successfully read. If destination was specified all data
is being written to that file. It starts reading in multiples of the sector size. Whenever a block fails, it is put to the end of the work-
ing queue and will be read again, possibly with a smaller read size.
By default it uses block sizes of roughly 1 MB, 32kB, and the native sector size (usually 512 bytes). These figures are adjusted slightly,
for devices whose sectorsize is not a power of 2, e.g., audio CDs with a sector size of 2352 bytes.
The options are as follows:
-b bigsize
The size of reads attempted first. The middle pass is roughly the logarithmic average of the bigsize and the sectorsize.
-r readlist
Read the list of blocks and block sizes to read from the specified file.
-s interval
How often we should update the writelist file while things go OK. The default is 60 and the unit is "progress messages" so if things
go well, this is the same as once per minute.
-w writelist
Write the list of remaining blocks to read to the specified file if recoverdisk is aborted via SIGINT.
The -r and -w options can be specified together. Especially, they can point to the same file, which will be updated on abort.
OUTPUT
The recoverdisk utility prints several columns, detailing the progress
start Starting offset of the current block.
size Read size of the current block.
len Length of the current block.
state Is increased for every failed read.
done Number of bytes already read.
remaining Number of bytes remaining.
% done Percent complete.
EXAMPLES
# recover data from failing hard drive ada3
recoverdisk /dev/ada3 /data/disk.img
# clone a hard disk
recoverdisk /dev/ada3 /dev/ada4
# read an ISO image from a CD-ROM
recoverdisk /dev/cd0 /data/cd.iso
# continue reading from a broken CD and update the existing worklist
recoverdisk -r worklist -w worklist /dev/cd0 /data/cd.iso
# recover a single file from the unreadable media
recoverdisk /cdrom/file.avi file.avi
# If the disk hangs the system on read-errors try:
recoverdisk -b 0 /dev/ada3 /somewhere
SEE ALSO dd(1), ada(4), cam(4), cd(4), da(4)HISTORY
The recoverdisk utility first appeared in FreeBSD 7.0.
AUTHORS
The original implementation was done by Poul-Henning Kamp <phk@FreeBSD.org> with minor improvements from Ulrich Sporlein <uqs@FreeBSD.org>.
This manual page was written by Ulrich Sporlein.
BUGS
Reading from media where the sectorsize is not a power of 2 will make all 1 MB reads fail. This is due to the DMA reads being split up into
blocks of at most 128kB. These reads then fail if the sectorsize is not a divisor of 128kB. When reading a full raw audio CD, this leads to
roughly 700 error messages flying by. This is harmless and can be avoided by setting -b to no more than 128kB.
recoverdisk needs to know about read errors as fast as possible, i.e. retries by lower layers will usually slow down the operation. When
using cam(4) attached drives, you may want to set kern.cam.XX.retry_count to zero, e.g.:
# sysctl kern.cam.ada.retry_count=0
# sysctl kern.cam.cd.retry_count=0
# sysctl kern.cam.da.retry_count=0
BSD October 1, 2013 BSD