12-10-2019
I'm thinking...............
1. Perhaps the new mobo is faulty as far as this peripheral is concerned
2. Have you accidentally bent a pin on the mobo socket where this device plugs in?
3. Does the mobo have a jumper wrongly set to enable this device? (Compare to old mobo)
4. Is there a separate power connector for this device which you forgot to connect? (Probably not if it's whirring)
Can you connect this optical to another system temporarily just to check that it's working?
If the system BIOS can't see it then you have no hope until it does.
Last edited by hicksd8; 12-10-2019 at 01:04 PM..
This User Gave Thanks to hicksd8 For This Post:
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I tried to install Magneto-Optical (MO) drive Fujutsu to COMPAQ Proliant ML350 with SCO Openserver 5.0.5. Harddisk and MO are connected to Adaptec UW-SCSI-3 (driver ad160).
During boot process system shows me that MO is connected to host adapter 1, bus 0, SCSI ID 1 and LUN 0. But when I... (2 Replies)
Discussion started by: yurist
2 Replies
2. UNIX for Dummies Questions & Answers
Trying to get my unix system to recognize an optical drive, it was delivered to us, so we assumed it worked, in the 2 years since no one ever has used it, we want to now. However, even running probe-scsi-all doesn't bring up that drive. It's a scsi address of 3, at the end of the chain, all... (1 Reply)
Discussion started by: kymberm
1 Replies
3. Shell Programming and Scripting
Dear all,
I have created a KornShell script containing swiches with getopts (command line switches). Normally, my script should work like this:
$ ./myscript.ksh -a 12 -b 4 -c 78
The switch a was selected with the argument 12
The switch b was selected with the argument 4
The switch c was... (3 Replies)
Discussion started by: dariyoosh
3 Replies
4. Solaris
i installed solaris 5.10 on dell vostro 1500...but it does not detect interface card....i need to pratice networking concepts ............please help me in this regard... (1 Reply)
Discussion started by: vivek_ng
1 Replies
5. Hardware
is rhel 6 compatible with dell xps 14.I tried to install it but could not install.Installation hanged at detecting hardware (1 Reply)
Discussion started by: shamapraveen
1 Replies
6. AIX
Hi all,
I have a problem here
root@host1 / # lsdev -Cc tape
rmt0 Defined 07-00-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt1 Defined 07-00-02 IBM 3580 Ultrium Tape Drive (FCP)
smc0 Defined 07-00-02 IBM 3573 Tape Medium Changer (FCP)
root@host1 / # cfgmgr -l fcs2
Method error... (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies
7. Ubuntu
I have Ubuntu 16.04 (dual boot with Windows 10) and a HP Spectre x360 laptop.
I have recently bought a Dell Ultrasharp U2515H monitor, which I connect via a Dell docking station.
When I plug the docking station to my laptop on Windows, both monitors are detected and everything works fine.
... (23 Replies)
Discussion started by: twelth_hour
23 Replies
LEARN ABOUT DEBIAN
diskseekd
diskseekd(1) General Commands Manual diskseekd(1)
Name
diskseek, diskseekd - disk seek daemon; simulates Messy Dos' drive cleaning effect
Note
This manpage has been automatically generated from fdutils's texinfo documentation. However, this process is only approximative, and some
items, such as cross-references, footnotes and indices are lost in this translation process. Indeed, these items have no appropriate rep-
resentation in the manpage format. Moreover, only the items specific to each command have been translated, and the general information
about fdutils has been dropped in the manpage version. Thus I strongly advise you to use the original texinfo doc.
* To generate a printable copy from the texinfo doc, run the following commands:
./configure; make dvi; dvips fdutils.dvi
* To generate a HTML copy, run:
./configure; make html
A pre-made HTML can be found at: `http://www.tux.org/pub/knaff/fdutils'
* To generate an info copy (browsable using emacs' info mode), run:
./configure; make info
The texinfo doc looks most pretty when printed or as HTML. Indeed, in the info version certain examples are difficult to read due to the
quoting conventions used in info.
Description
Several people have noticed that Linux has a bad tendency of killing floppy drives. These failures remained completely mysterious, until
somebody noticed that they were due to huge layers of dust accumulating in the floppy drives. This cannot happen under Messy Dos, because
this excuse for an operating system is so unstable that it crashes roughly every 20 minutes (actually less if you are running Windows).
When rebooting, the BIOS seeks the drive, and by doing this, it shakes the dust out of the drive mechanism. diskseekd simulates this effect
by seeking the drive periodically. If it is called as diskseek, the drive is sought only once.
Options
The syntax for diskseekd is as follows:
diskseekd [-d drive] [-i interval] [-p pidfile]
-d drive
Selects the drive to seek. By default, drive 0 (`/dev/fd0') is sought.
-i interval
Selects the cleaning interval, in seconds. If the interval is 0, a single seek is done. This is useful when calling diskseek from a
crontab. The default is 1000 seconds (about 16 minutes) for diskseekd and 0 for diskseek.
-p pidfile
Stores the process id of the diskseekd daemon into pidfile instead of the default `/var/run/diskseekd.pid'.
Bugs
1. Other aspects of Messy Dos' flakiness are not simulated.
2. This section lacks a few smileys.
See Also
Fdutils' texinfo doc
fdutils-5.5 03Mar05 diskseekd(1)