10-30-2010
root@arumator--net:/home/arumator# mount -o loop /media/250189482C661005/recovery_image.img /mnt -t vfat
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
I need to mount the image sorry if i wasn't clear. i currently don't have the drive on me if I try mounting the image without the -o loop option it says its not a block device. this is the output from the dmesg | tail
root@arumator--net:/home/arumator# dmesg | tail
[26873.008861] sd 8:0:0:0: [sdb] Mode Sense: 23 00 10 00
[26873.008864] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[26873.014885] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[26873.014896] sdb: sdb1
[26873.037861] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[26873.037868] sd 8:0:0:0: [sdb] Attached SCSI disk
[26873.557114] UDF-fs: Partition marked readonly; forcing readonly mount
[26873.559232] UDF-fs INFO UDF: Mounting volume 'WD SmartWare', timestamp 2009/11/13 20:34 (1f10)
[37695.928682] FAT: invalid media value (0xb9)
[37695.928687] VFS: Can't find a valid FAT filesystem on dev loop0.
8 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
could anyone give me a general idea of how i may clone a 2 Gig disk running Solaris 7 on it to another disk of the same size?
currently, this system only has one disk in it though. i do have the ability to hook up another disk via SCSI.
i have been told i need to boot to "miniroot" to run... (9 Replies)
Discussion started by: obosha
9 Replies
2. Solaris
Hai ......... my name Rio,
I want to clone my harddisk at Sun Balade 2000 server with Solaris 8 OS, my question is :
a. what kind method for making backup or clonning disk ?
b. what method more easier , quick but still reliable ?
c. how to proceed it ?
Thanks (1 Reply)
Discussion started by: rioria
1 Replies
3. Filesystems, Disks and Memory
Disk cloning
I had an external SCSI master disk that I used to clone to an identical external SCSI disk because the other SCSI disk would become corrupted. My original Master became corrupted so I used one of the other to good disk to copy back to the master. Unfortunately the new master needs... (1 Reply)
Discussion started by: stamperr
1 Replies
4. SCO
Hi.
We tried cloning a SCO Unix hard disk using Norton Ghost.
However, the new cloned hard disk encounter booting problem.
What possibly go wrong? (1 Reply)
Discussion started by: Mizan
1 Replies
5. SCO
Continuing saga of working on making a retail store more robust by creating a backup clone of the main server, a 1995 era :eek: PC running SCO OpenServer 5.0.0b and a discontinued Point of Sales (POS) software system.
I have a PC of the same make and model. The CPU runs faster and it has a... (5 Replies)
Discussion started by: jgt10
5 Replies
6. AIX
hello folks,
I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space
Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Discussion started by: filosophizer
9 Replies
7. UNIX for Advanced & Expert Users
Guys can anyone tell how can we do faster disk cloning
Below i found in google
1. dd if=/dev/sda of=/dev/sdb bs=4096 conv=noerror,sync
So adding "conv=noerror,sync " makes it faster looks against not adding it
2. Enable write cache activated (hdparm -W1 /dev/sda) then run dd ..
... (2 Replies)
Discussion started by: heman96
2 Replies
8. Solaris
Hi,
I am trying to clone the hard disk image of Solaris OS on one disk to another disk. After some googling I found that there is a command "dd" to achieve this.
However there is a condition to use the dd command, that the disk geometry of both the disks (source and target disks) should... (5 Replies)
Discussion started by: rajujayanthy
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