08-18-2015
The OP has said that the drives can be plugged into other machines and behave. If it was a virus then all other machines would be infected and none of them would behave.
Anyway, as Corona688 has already said, a virus needs to be executed to do any damage and if the drives aren't mounting (or even being seen by the hardware), no code is being read leave alone being executed.
Last edited by hicksd8; 08-18-2015 at 03:22 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Will some one tell me what this means.
"warning: ida 0 <slot 6> : command timed out on dev 1/42 blk 4824290 logical unit=0 blocks=5512102, size 2, cmd=0x20."
I'm running SCO 505 on a proliant 1600r.
Thnank you in advance. (3 Replies)
Discussion started by: franruiz
3 Replies
2. Linux
I am using an Acer Aspire 4720Z with two partitions C and D. Windows is installed on C and I decided to install Red Hat Linux 9 in partition D. The two partitions are in NTFS file system. During my installation of the the Linux, a prompt was displayed on screen with the message: "No hard drives... (2 Replies)
Discussion started by: tamcomng
2 Replies
3. Solaris
I have a Solaris machine running OpenSolaris v5.11.
It came with a hard drive. It's called /dev/dsk/c4d0s0.
I added two new hard drives into the box. I can't figure out what it's called in /dev/dsk. There are 210 filenames in /dev/dsk.
How do I find out which filename corresponds to the... (2 Replies)
Discussion started by: sqa777
2 Replies
4. Solaris
Version: solaris 10 x86
I just got a western digital external harddrive formated with fat 32. this drive came with some setup files which is meant for windows or mac.
I want to reformat and partition this drive into two ( for solaris and windows) such that the setup files will still be there... (2 Replies)
Discussion started by: seyiisq
2 Replies
5. Filesystems, Disks and Memory
Folks;
I just added 2 physical new hard drives to my SUSE server. My server is already running SUSE 10.3 version.
Is there a command i can use to add the new space or even see if the system can sees them? (3 Replies)
Discussion started by: Katkota
3 Replies
6. Solaris
I have a T2000 Sun-Fire server. I have 2 sets of drives in a raid 1. Lets call them Set A and Set B. I had Set A installed and working. I needed a new install so I so build up Set B. After some time I wanted to put Set A back in the server. Now the system will not boot off of Set A. I tried to boot... (7 Replies)
Discussion started by: stu1811
7 Replies
7. Hardware
Hello everyone. I have a question which I may know the answer to, I'm just looking for a confirmation. When it comes to the MBR of a hard drive, i've read in multiple sources that it's always located in the first sector of the hard drive. Is the MBR there from the factory? When I buy a new blank... (3 Replies)
Discussion started by: Lost in Cyberia
3 Replies
8. Solaris
I have three Sun Oracle Netra T5220s. I am trying to just get the processor information psrinfo or prtdiag -v from the # prompt in single user mode.
I am needing to know the commands to get to boot the CD/DVD of the Solaris OS. I am using it via Serial Port Management.
Tinkering around I... (4 Replies)
Discussion started by: nerdboy
4 Replies
9. Solaris
Hi,
I have two SCSI Hard Drives in a Sun Solaris 8 server as shown below. I would like to access Disk1 and look at its contents, directory structure and files. How do I change my default directory from Disk 0 to Disk 1 and vice versa?
Thank you. (5 Replies)
Discussion started by: ssabet
5 Replies
10. UNIX for Beginners Questions & Answers
Ok so i thought i was smart but i can tell I need some help. I am playing around with understanding lvm and adding disks to a linux box. I added a disk and then ran what i thought were commands to add this disk to the box but I think I messed up and would like some help. My question is did i... (5 Replies)
Discussion started by: cptkirkh
5 Replies
LEARN ABOUT MOJAVE
mount_udf
MOUNT_UDF(8) BSD System Manager's Manual MOUNT_UDF(8)
NAME
mount_udf -- mount a UDF filesystem
SYNOPSIS
mount_udf [-o options] [-s sessionStart] [-n lastRecordedLBA] [-b blockSize] [-p packetSizeInBlocks] [-v verificationPolicy] [-w] devicePath
mountPath
DESCRIPTION
The mount_udf command attaches the UDF filesystem residing on the device devicePath to the global filesystem namespace at the location indi-
cated by mountPath. This command is normally executed by mount(8) at boot time.
The options are as follows:
-o options
Options are specified with a -o flag followed by a comma separated string of options. See the mount(8) man page for possible options
and their meanings.
-v verificationPolicy
This is an advanced option not useful for regular use. It controlls the verification policy when writing to RW type optical media.
Its value can be "meta", "all", or "none". Policy "meta" means only the metadata are verified after they are written. This is the
default policy. Policy "all" means to verify data written, which could be several times slower than policy "meta". Policy "none"
does not verify any data. It is only slightly faster than "meta" in normal cases, but may result a corrupted UDF disc if the write
of metadata fails.
-s sessionStart
This is an advanced option not useful for regular use. When manually mounting a UDF volume with Virtual Partition, it specifies the
start Logical Block Address of the last session where UDF data structures (VRS and AVDP) resides. This value overrides the value
obtained from the device.
-n lastRecordedLBA
This is an advanced option not useful for regular use. When manually mounting a UDF volume with Virtual Partition, it specifies the
last recorded Logical Block Address where the UDF VAT ICB will be searched. This value overrides the value obtained from the device.
-b blockSize
This is an advanced option not useful for regular use. It specifies the block size in bytes used when mounting the UDF volume. This
value overrides the value obtained from the device.
-p packetSizeInBlocks
This is an advanced option not useful for regular use. It specifies the packet size in blocks when manually mounting the UDF volume.
This value overrides the value obtained from the device.
-w This is an advanced option not useful for regular use. It forces to enable the experimental packet writing function on optical media
that has not been fully supported, such as CD-R, CD-RW, DVD-R, DVD+R, HD DVD-R, and BD-R. Writing to these media does not work on
some drives and may cause data corruption or data loss on some other drives. Therefore, this flag should be used only by file system
developers when debugging the experimental write functions.
The -s, -n, -b, and -p flags are not useful in normal use. They are mainly used for debugging and data recovery. Since the -s, -n, and -p
flags are all specified in units of block size, when any of these flags are specified, it is strongly recommended that the -b flag is also
specified.
SEE ALSO
mount(2), unmount(2), fstab(5), mount(8)
BUGS
Reading of all UDF revisions (1.02 - 2.60) on both block device (e.g., hard drives and USB drives) and most optical media is supported.
Writing to block devices, DVD-RW and DVD+RW is supported with the following exceptions: (1) Cannot write Finder Info, Resource Fork, or other
extended attributes in UDF volumes of revision 1.02 and 1.50; (2) Cannot write to mirrored metadata partition.
HISTORY
The mount_udf utility first appeared in Mac OS X.
4th Berkeley Distribution December 6, 2006 4th Berkeley Distribution