Sponsored Content
Homework and Emergencies Emergency UNIX and Linux Support mdadm unable to fail a resyncing drive? Post 302546279 by Bashingaway on Wednesday 10th of August 2011 11:24:43 PM
Old 08-11-2011
I'd already tried with the --force option....no go I'm afraid.

I should get the replacement disks today so will be physically pulling the drive and crossing my fingers.
 

10 More Discussions You Might Find Interesting

1. Solaris

Resyncing Progress of hardware mirror

Hi, I've recently mirrored the 4 disks in a V440. Disks 0 + 1 have been mirrored with hardware mirroring using the command raidctl -c c1t0d0 c1t2d0, the other 2 disks have been mirrored using Soltisce Disk Suite. I know how to check the progress for the SDS mirroring but how can I find the... (2 Replies)
Discussion started by: Chains
2 Replies

2. Solaris

Unable to mount USB Pen drive on my Server

Hello Gurus!! Very recently i tried to mount a USB pen drive onto my solaris 10 (X4170 model) server. As i understand, in ideal scenarios it should get mounted automatically, but it did not happen. Neither anything is shown in "iostat -En" output or "rmformat -l" about the pen drive. I also... (10 Replies)
Discussion started by: EmbedUX
10 Replies

3. UNIX for Advanced & Expert Users

mdadm question

Hello, I have 4 drives (500G each) in a raid 10, I got a power failior and this is the result? cat /proc/mdstat Personalities : md126 : inactive sdb sdc sdd sde 1953536528 blocks super external:-md127/0 md127 : inactive sdd(S) sde(S) sdb(S) sdc(S) 9028 blocks super... (3 Replies)
Discussion started by: rmokros
3 Replies

4. UNIX for Advanced & Expert Users

mdadm container! How does it work

Hi everyone, I am not sure if I understand how mdadm --create /dev/md0 --level=container works? A device called /dev/md0 appears in /proc/mdstat but I am not sure how to use that device? I have 2 blank drives with 1 500GB partition on each. I would like to setup mirroring, but not in the... (0 Replies)
Discussion started by: hytron
0 Replies

5. Debian

Unable to mount external drive

Trying to mount an external 160GB Toshiba drive but.... this is my dmesg tail output: usb 2-2: new high speed USB device using ehci_hcd and address 3 usb 2-2: New USB device found, idVendor=13fd, idProduct=1618 usb 2-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 usb 2-2:... (4 Replies)
Discussion started by: Ridson
4 Replies

6. Red Hat

mdadm for / and /boot

had this RHEL 5 installation with /dev/sda1 and /dev/sda2 running.. created two more partitions /dev/sdj1 and /dev/sdj2 , the same sized partition as /dev/sda trying to use mdadm to create RAID1 .. I cannot even do it in "rescue" mode, I wonder if it can be done.. it kept... (2 Replies)
Discussion started by: ppchu99
2 Replies

7. UNIX for Dummies Questions & Answers

unable to automount a cifs drive in linux

Hi I am using SUSE 11 linux I have couple of "nfs" entries in /etc/fstab which are automatically loaded after system restart. One of the entry is windows drive mounted using cifs as shown below //IP-Address/Partition /mnt/x cifs credentials=/creds/.creds,rw,uid=<name> 0 0 I want to... (1 Reply)
Discussion started by: rakeshkumar
1 Replies

8. Filesystems, Disks and Memory

MDADM Failure - where it came from?

Hello, i have a system with 6 sata3 seagate st3000dm01 disks running on stable Debian with software raid mdadm. i have md0 for root and md1 for swap and md2 for the files. i now want to add one more disk = sdh4 for md2 but i got this errors: The new disk is connected to an 4 port sata... (7 Replies)
Discussion started by: Sunghost
7 Replies

9. Solaris

Unable to send SCSI commands to USB Drive

I am connecting a USB mass storage removeable drive to Solaris 10 x86 machine. The device is detected and i am able to perform standard read and write functions. But i want to use a code to send IOCTL based SCSI commands to the same device to read and write the data. Which i am unable to do so.... (17 Replies)
Discussion started by: danish2012
17 Replies

10. Solaris

Maint, resyncing and last-erred notifications

Hi fellow members! I have a oracle solaris server with two internal disks, that acts as an authentication server only, and for now the server seems to be doing its job, but when typing metastat -c I get some notifications. I am not familiar with SVM, I wonder if someone can help me on this:... (3 Replies)
Discussion started by: fretagi
3 Replies
fdmount(1)                                                    General Commands Manual                                                   fdmount(1)

Name
       fdmount - Floppy disk mount utility

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
          fdmount [-l] [--list] [-d] [--daemon] [--detach]
          [-i interval] [--interval interval] [-o mount-options]
          [-r] [-readonly] [-s] [--sync] [--nosync] [--nodev]
          [--nosuid] [--noexec] [-f] [--force] [-h] [--help]
          [drivename] [mountpoint]

          fdumount [-f] [--force] [drivename]

          fdlist

          fdmountd [-i interval] [--interval interval] [-r]
          [-readonly] [-s] [--sync] [--nosync] [--nodev]
          [--nosuid] [--noexec] [--help] [drivename] [mountpoint]]

       The  fdmount  program  mounts a floppy disk in the specified drive. It tries to figure out the exact format and filesystem type of the disk
       from data in the disk's boot sector or super block and the auto-detected track layout.

       Currently, fdmount supports the filesystems minix, ext, ext2, xia, and msdos, and includes special support for disks formatted  by  the  2M
       utility for MS-DOS.

       It also checks whether the disk is write protected, in which case it is mounted read-only.

       The symbolic drivename is (currently) one of `fd[0-7]', corresponding to the special device files `/dev/fd[0-7]'. If drivename is not spec-
       ified, `fd0' is assumed.

       The disk is mounted on the directory mountpoint, if specified, or on `/fd[0-7]'.  In either case, the mount  point  must  be  an  existing,
       writable directory.

       Due  to  a  bug  in the floppy driver (?), the polling interval (-i flag) must be longer than the spindown offset. Thus you need to do (for
       example) floppycontrol --spindown 99 before starting fdmountd in daemon mode

Options
       -l --list
              List all known drives with their symbolic name, type, and mount status.

       -d --daemon
              Run in daemon mode (see below).

       --detach
              Runs daemon in background, and detaches it from its tty. Messages produced after the fork are logged to syslog.

       -p file
       --pidfile file

              Dumps the process id of the daemon to file. This makes killing the daemon easier: kill -9 `cat file`

       -i interval
       --interval interval
              Set the polling interval for daemon mode. The unit for interval is 0.1 seconds, the default value is 10 (i.e. 1 second).

       -o options
       --options options
              Sets filesystem-specific options. So far, these are only available for DOS and Ext2 disks. The following DOS options are  supported:
              check, conv, dotsOK, debug, fat, quiet, blocksize.  The following Ext2 options are supported: check, errors, grpid, bsdgroups, nogr-
              pid, sysvgroups, bsddf, minixdf, resgid, debug, nocheck.  When running as a daemon,  options  not  applying  to  the  disk  that  is
              inserted (because of its filesystem type) are not passed to mount.

       -r --readonly
              Mount the disk read-only. This is automatically assumed if the disk is write protected.

       -s --sync
              Mount with the SYNC option.

       --nosync
              Mounts without the SYNC option, even when running as daemon.

       --nodev
              Mount with the NODEV option. Ignored for msdos filesystems, otherwise always set for non-root users.

       --nosuid
              Mount with the NOSUID option. Ignored for msdos filesystems, otherwise always set for non-root users.

       --noexec
              Mount with the NOEXEC option.

       -f --force
              Attempt  a  mount  or unmount operation even `/etc/mtab' says that the drive is already mounted, or not mounted, respectively.  This
              option is useful if `/etc/mtab' got out of sync with the actual state for some reason.

       -h --help
              Show short parameter description

Security
       When mounting on the default mount point, the mount points' owner is set to the current user, and the access flags according to the  user's
       umask.  For a specified mountpoint, owner and permissions are left unchanged. Default mount points are called /fd0, /fd1, ... , /fd7.

       The user running fdmount must have read access to the floppy device for read only mounts, and read/write access for read/write mounts.

       Fdmount can be run suid root, allowing users to mount floppy disks. The following restrictions are placed upon non-root users:

       *      If a mountpoint is specified explicitly, it must be owned by the user.

       *      A user may only unmount a disk if the mount point is owned by the user, or if it the disk has been mounted by the same user.

       *      Non-msdos disks are automatically mounted with the nodev and nosuid flags set.

       However, do not rely on fdmount being secure at the moment.

Daemon mode
       In daemon mode, the specified drive is periodically checked and if a disk is inserted, it is automatically mounted.

       When  the  disk  is removed, it is automatically unmounted.  However, it is recommended to unmount the disk manually before removing it. In
       order to limit corruption, disks are mounted with the SYNC option when running in daemon mode, unless the --nosync flag is given.

       Note that this mode has some potential drawbacks:

       *      Some floppy drives have to move the drive head physically in order to reset the disk change signal. It is strongly  recommended  not
              to use daemon mode with these drives.  See section floppycontrol, for details.

       *      If a disk does not contain a filesystem (e.g. a tar archive), the mount attempt may slow down initial access.

       *      As  fdmount cannot identify the user trying to use the disk drive, there is no way to protect privacy. Disks are always mounted with
              public access permissions set.

Diagnostics
       error opening device name

       error reading boot/super block
              fdmount failed to read the first 1K of the disk. The disk might be damaged, unformatted, or it may have a  format  which  is  unsup-
              ported by the FDC or the Linux kernel.

       unknown filesystem type
              No magic number of any of the supported filesystems (see above) could be identified.

       sorry, can't figure out format (fs filesystem)
              The size of the filesystem on the disk is incompatible with the track layout detected by the kernel and an integer number of tracks.
              This may occur if the filesystem uses only part of the disk, or the track layout was detected incorrectly by the kernel.

       failed to mount fs> <sizeK-disk
              The actual mount system call failed.

       failed to unmount
              The actual unmount system call failed.

       cannot create lock file /etc/mtab~
              If `/etc/mtab~' exists, you should probably delete it. Otherwise, check permissions.

       Can't access mountpoint
              Most probably, the default or specified mount point does not exist.  Use mkdir.

       mountpoint is not a directory
              The mountpoint is not a directory.

       not owner of mountpoint
              Non-root users must own the directory specified as mount point.  (This does not apply for the default mount points, /fd[0-3].)

       No write permission to mountpoint
              Non-root users must have write permission on the mount point directory.

       Not owner of mounted directory: UID=uid
              Non-root users cannot unmount if the mount point is owned (i.e. the disk was mounted) by another user.

       invalid drive name
              Valid drive names are `fd0', `fd1', etc.

       drive name does not exist
              The drive does not exist physically, is unknown to the Linux kernel, or is an unknown type.

       Drive name is mounted already
              Trying to mount a drive which appears to be mounted already.  Use the --force option if you think this is wrong.

       Drive name is not mounted
              Trying to unmount a drive which does not appear to be mounted.  Use the --force option if you think this is wrong.

       ioctl(...) failed
              If this occurs with the FDGETDRVTYP or FDGETDRVSTAT, ioctl's you should probably update your Linux kernel.

       mounted fs size-disk (options)
              Success message.

Bugs
       *      Fdmount should be more flexible about drive names and default mount points (currently hard coded).

       *      Probably not very secure yet (when running suid root).  Untested with ext and xia filesystems.

       *      Can't specify filesystem type and disk layout explicitly.

       *      In daemon mode, the drive light stays on all the time.

       *      Some newer filesystem types, such as vfat are not yet supported.

See Also
       Fdutils' texinfo doc

fdutils-5.5                                                           03Mar05                                                           fdmount(1)
All times are GMT -4. The time now is 09:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy