"mount: wrong fs type, bad option, bad superblock...

All documents from the original Software Support Library (SSL)

Moderators: Leon van Heerden, Luanda_Junzi, Belinda Frick, Lee Hendricks

"mount: wrong fs type, bad option, bad superblock...

Postby John Richard Procter » Mon May 30, 2011 1:16 pm

Please try the following steps to resolve the error logged:

  1. Run the "DriveInfo".

    Explanation of DriveInfo output sample below:
    **********************************************
    * Amethyst drive information *
    **********************************************
    Code: Select all
    Physical drives found: 4
    sda: SATA/SCSI drive 1
    sdb: SATA/SCSI drive 2
    sdc: SATA/SCSI drive 3
    hdb: IDE Primary slave
    Main drive is sda: SATA/SCSI drive 1
    ERROR: System / Amethyst archive drive mismatch
    System is configured with archive drive hda: IDE Primary master
    Amethyst is configured with archive drive hdb: IDE Primary slave

    **********************************************

    There are 3 things that must match. PHYSICAL, SYSTEM and AMETHYST:
    *** hdb: IDE Primary slave:
    is the PHYSICAL configuration, detected when the machine started up.
    *** System is configured ... hda:
    IDE Primary master is the SYSTEM configuration (i.e. Linux).
    *** Amethyst is configured ... hdb:
    IDE Primary slave is the AMETHYST configuration.

    Al 3 must match. If not, you can only change the PHYSICAL configuration
    (dip switches). The SYSTEM and AMETHYST configuration must always match,
    if not please contact support by e-mail, support@datatex.co.za, with
    the log entry.
  2. Shut the server down from AMETHYST webadmin. Power the server down.
  3. If the DriveInfo indicated that the PHYSICAL configuration is
    incorrect, please adjust according to diagram on harddrive. If the SYSTEM
    and AMETHYST configuration is a mismatch, get the fix from
    support@datatex.co.za before proceeding.

    Shut the AMETHYST server down via Webadmin. You need to power the
    server down. Insert the archive drive into the tray and lock it
    (must be locked). When the lock is switched to "ON", boot the server
    for the BIOS to detect the drive. Please note that the server must be
    powered down when you insert the drive and switch the lock to on.
  4. Re-start the server.
  5. Check if all the drives is picked up in the BIOS.
  6. When the server boots up it will show all the drives on the main screen.
  7. Do a test connection.
    Please use the 'Test Connection' button in AMETHYST webadmin under the
    'Configure Archive Settings' link. Make sure that 'Archive Type' is set
    to 'NFS' or 'DUAL' (depending on which option you use with your backup).
  8. If successfull, it will display:

    Results from testing archive connection

    Code: Select all
    Checking backup type ... hard drive only
    Mounting archive drive(s) ... OK
    /dev/hda1 on /opt/amethyst/backup/hdd type vfat(rw)
    Writing to hard drive ... OK
    Unmounting archive driv(s)... OK
    Do a check available disk space.

    If all of this checks out OK, you can try the archive again.

    • If unsuccessfull:
    a) Check/test the cradle that the drive is placed in and the bracket in
    the server.

    b) If it is not the cradle, the only option is that we need access to
    the AMETHYST server. If we cannot get remote access to at the client,
    the server needs to be shipped to Datatex. Please provide us with logs
    and screenshots of all test done.
John Richard Procter
 
Posts: 552
Joined: Tue May 03, 2011 2:02 pm

Return to Support Archive's (Amethyst)

Who is online

Users browsing this forum: No registered users and 1 guest