Topic: USB Backup is not recognized

[bclayton]

Hi, Running 8.2 and my system crashed and won't reboot.  I do have a current USB Dar backup.  I have installed 8.2 on another machine and when I try to Restore, it can't find the USB device.

In a bit of a panic, so any help appreciated.

Brooks

[janet]

bclayton

Well do you want to troubleshoot your original server problem or do you want to troubleshoot restore ?
You seem to be going to a lot of effort, without us knowing whether you have tried fixing the original server.

By DAR backup do you mean a server manager Backup or Restore panel backup to locally connected USB drive ?
If so, then you need to reconfigure the backup exactly as it was configured on the original server.
Otherwise provide more exact details of your backup method.

On the new server connect the USB drive & check it is recognised with
fdisk -l

On the original server can you boot up to the SME server install CD/DVD/USB media ?
You can then do some troubleshooting & diagnostics.

You need to tell us much more info about your original server setup, number of disks, do you have a UPS connected, any error messages etc.
ie what happened to cause the problem ?

[bclayton]

Janet,
Thanks for your help. My original server had 2 HD and was on a UPS.  We had a power outage for a while and the server went down.  I did try to use a 8.2 DVD in rescue mode and could not get it going.

I have installed on a new machine and would rather work with that.  It has 2 HD also and has been updated.  This is my email server so I really need to restore.  I had a USB backup labeled USBdisk2
Here is the result of fdisk -l
[root@mail ~]# fdisk -l

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   fd  Linux raid autodetect
/dev/sda2              14       30401   244091610   fd  Linux raid autodetect

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          13      104391   fd  Linux raid autodetect
/dev/sdb2              14      121601   976655610   fd  Linux raid autodetect

Disk /dev/md2: 249.9 GB, 249949716480 bytes
2 heads, 4 sectors/track, 61022880 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md2 doesn't contain a valid partition table

Disk /dev/md1: 106 MB, 106823680 bytes
2 heads, 4 sectors/track, 26080 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

    Device Boot      Start         End      Blocks   Id  System

Disk /dev/dm-0: 247.8 GB, 247833034752 bytes
255 heads, 63 sectors/track, 30130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 2113 MB, 2113929216 bytes
255 heads, 63 sectors/track, 257 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           1          13      104384+  fd  Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/sdc2              13      121601   976655647   fd  Linux raid autodetect
[root@mail ~]#
[root@mail ~]#
[root@mail ~]#
[root@mail ~]#
[root@mail ~]#
[root@mail ~]# Last login: Sun Feb 28 19:02:49 2016 from pc-00002.mycompany.local

Before editing configuration files, familiarise
yourself with the automated events and templates
-bash: Last: command not found
systems.
[root@mail ~]# ************ Welcome to SME Server 8.2 *************

Remember that SME Server is free to download
-bash: anaconda-ks.cfg: command not found
and use, but it is not free to build
[root@mail ~]#
[root@mail ~]# Before editing configuration files, familiarise
http://wiki.contribs.org/Donate
-bash: Before: command not found
[root@mail ~]# yourself with the automated events and templates
[root@mail ~]# fdisk -l
-bash: yourself: command not found

[root@mail ~]# systems.
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

-bash: systems.: command not found
   Device Boot      Start         End      Blocks   Id  System
[root@mail ~]#
/dev/sda1   *           1          13      104391   fd  Linux raid autodetect
[root@mail ~]# Please take the time to read the documentation
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
-bash: Please: command not found
Units = cylinders of 16065 * 512 = 8225280 bytes
[root@mail ~]# http://wiki.contribs.org/Main_Page
   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          13      104391   fd  Linux raid autodetect
/dev/sdb2              14      121601   976655610   fd  Linux raid autodetect

Disk /dev/md2: 249.9 GB, 249949716480 bytes
2 heads, 4 sectors/track, 61022880 cylinders
-bash: http://wiki.contribs.org/Main_Page: No such file or directory
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md2 doesn't contain a valid partition table
[root@mail ~]#
[root@mail ~]# Remember that SME Server is free to download
2 heads, 4 sectors/track, 26080 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

    Device Boot      Start         End      Blocks   Id  System

-bash: Remember: command not found
Disk /dev/dm-0: 247.8 GB, 247833034752 bytes
255 heads, 63 sectors/track, 30130 cylinders
[root@mail ~]# and use, but it is not free to build
Disk /dev/dm-1: 2113 MB, 2113929216 bytes
255 heads, 63 sectors/track, 257 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
-bash: and: command not found
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
[root@mail ~]#

   Device Boot      Start         End      Blocks   Id  System
[root@mail ~]# Please help the project :
/dev/sdc2              13      121601   976655647   fd  Linux raid autodetect
[root@mail ~]#
[root@mail ~]#
-bash: Please: command not found
[root@mail ~]# http://wiki.contribs.org/Donate
[root@mail ~]#
[root@mail ~]#
-bash: http://wiki.contribs.org/Donate: No such file or directory
[root@mail ~]#
[root@mail ~]# ****************************************************
-bash: anaconda-ks.cfg: command not found
[root@mail ~]# [root@mail ~]# fdisk -l
-bash: [root@mail: command not found
[root@mail ~]#
[root@mail ~]# Disk /dev/sda: 250.0 GB, 250059350016 bytes
-bash: Disk: command not found
[root@mail ~]# 255 heads, 63 sectors/track, 30401 cylinders
-bash: 255: command not found
[root@mail ~]# Units = cylinders of 16065 * 512 = 8225280 bytes
-bash: Units: command not found
[root@mail ~]#
[root@mail ~]#    Device Boot      Start         End      Blocks   Id  System
-bash: Device: command not found
[root@mail ~]# /dev/sda1   *           1          13      104391   fd  Linux raid autodetect
-bash: /dev/sda1: Permission denied
[root@mail ~]# /dev/sda2              14       30401   244091610   fd  Linux raid autodetect
-bash: /dev/sda2: Permission denied
[root@mail ~]#
[root@mail ~]# Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
-bash: Disk: command not found
[root@mail ~]# 255 heads, 63 sectors/track, 121601 cylinders
-bash: 255: command not found
[root@mail ~]# Units = cylinders of 16065 * 512 = 8225280 bytes
-bash: Units: command not found
[root@mail ~]#
[root@mail ~]#    Device Boot      Start         End      Blocks   Id  System
-bash: Device: command not found
[root@mail ~]# /dev/sdb1   *           1          13      104391   fd  Linux raid autodetect
-bash: /dev/sdb1: Permission denied
[root@mail ~]# /dev/sdb2              14      121601   976655610   fd  Linux raid autodetect
-bash: /dev/sdb2: Permission denied
[root@mail ~]#
[root@mail ~]# Disk /dev/md2: 249.9 GB, 249949716480 bytes
-bash: Disk: command not found
[root@mail ~]# 2 heads, 4 sectors/track, 61022880 cylinders
-bash: 2: command not found
[root@mail ~]# Units = cylinders of 8 * 512 = 4096 bytes
-bash: Units: command not found
[root@mail ~]#
[root@mail ~]# Disk /dev/md2 doesn't contain a valid partition table
>
> Disk /dev/md1: 106 MB, 106823680 bytes
> 2 heads, 4 sectors/track, 26080 cylinders
> Units = cylinders of 8 * 512 = 4096 bytes
>
>     Device Boot      Start         End      Blocks   Id  System
>
> Disk /dev/dm-0: 247.8 GB, 247833034752 bytes
> 255 heads, 63 sectors/track, 30130 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Disk /dev/dm-0 doesn't contain a valid partition table
-bash: Disk: command not found
[root@mail ~]#
[root@mail ~]# Disk /dev/dm-1: 2113 MB, 2113929216 bytes
-bash: Disk: command not found
[root@mail ~]# 255 heads, 63 sectors/track, 257 cylinders
-bash: 255: command not found
[root@mail ~]# Units = cylinders of 16065 * 512 = 8225280 bytes
-bash: Units: command not found
[root@mail ~]#
[root@mail ~]# Disk /dev/dm-1 doesn't contain a valid partition table
>
> Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sdc1   *           1          13      104384+  fd  Linux raid autodetect
> Partition 1 does not end on cylinder boundary.
> /dev/sdc2              13      121601   976655647   fd  Linux raid autodetect
> [root@mail ~]#

[bclayton]

Janet,

I failed to mention that I was using the Backup and Restore in Server Manager.  Thanks.

[janet]

bclayton

.....I was using the Backup and Restore in Server Manager

So have you configured the backup job in the server manager, identical to original server ?
It must be indentical (including domain names etc) for the Restore to identify the backup data

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           1          13      104384+  fd  Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/sdc2              13      121601   976655647   fd  Linux raid autodetect

There appears to be another problem though that will prevent you configuring the backup job.
It looks like your USB drive sdc is now part of the RAID array.
Did you have the USB backup drive connected when you installed the new OS ?
If so it has been added to the RAID array & any backup data that was on it has been erased.

I would expect to see something more like this (from my sme8.2)
Disk /dev/sdc: 2000.3 GB, 2000365289472 bytes
255 heads, 63 sectors/track, 243197 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1      243197  1953479871   83  Linux


On the new server show us output of

cat /proc/mdstat

also show
df -h

then mount the USB drive (if you can) with something like
mount /dev/sdc1 /media/USBdisk2
& show again
df -h

remember to unmount the drive
umount /dev/sdc1

(you may have to change the mount & umount command parameters depending on your setup,
& whether you created a mount point folder at /media/USBdisk2)

[bclayton]

Janet,
The USB drive was not connected when I installed on a different machine.
[root@mail ~]# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdb1[1] sda1[0]
      104320 blocks [2/2] [UU]

md2 : active raid1 sdb2[1] sda2[0]
      244091520 blocks [2/2] [UU]

unused devices: <none>
[root@mail ~]#

[bclayton]

Janet,

Sorry, I failed to see all of your instructions.  I think I have done all you asked, below:

[root@mail ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/main-root
                      224G  2.0G  211G   1% /
/dev/md1               99M   17M   77M  18% /boot
tmpfs                 501M     0  501M   0% /dev/shm
[root@mail ~]#

Then

[root@mail ~]# mount /dev/sdc1 /media/USBdisk2
mount: mount point /media/USBdisk2 does not exist
[root@mail ~]#

Then

[root@mail ~]#
[root@mail ~]# umount /dev/sdc1
umount: /dev/sdc1: not mounted
[root@mail ~]#

Thanks

[janet]

bclayton

The USB drive was not connected when I installed on a different machine.

Well that's good, but why does it show as (ie with Linux RAID autodetect) ?
This is on the second server with the new OS installed & with the backup USB drive connected (& no other USB drives connected), is that correct ?

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           1          13      104384+  fd  Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/sdc2              13      121601   976655647   fd  Linux raid autodetect


I suggest you create a mount point eg
mkdir -p /media/USBdisk2

then attach the USB disk that has the backup on it
then do
mount /dev/sdc1 /media/USBdisk2

If that does not work then try
mount /dev/sdc2 /media/USBdisk2

then do & show us output of:
fdisk -l

df -h

ls -al /media/USBdisk2

cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdb1[1] sda1[0]
      104320 blocks [2/2] [UU]

md2 : active raid1 sdb2[1] sda2[0]
      244091520 blocks [2/2] [UU]

unused devices: <none>

That looks OK

[bclayton]

Janet,

Yes, This is on the second server with the new OS installed & with the backup USB drive connected (& no other USB drives connected), is that correct ?

Is this looking better?

[root@mail ~]#
[root@mail ~]# mkdir -p /media/USBdisk2
[root@mail ~]# mount /dev/sdc1 /media/USBdisk2


[root@mail ~]# fdisk -l

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   fd  Linux raid autodetect
/dev/sda2              14       30401   244091610   fd  Linux raid autodetect

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          13      104391   fd  Linux raid autodetect
/dev/sdb2              14      121601   976655610   fd  Linux raid autodetect

Disk /dev/md2: 249.9 GB, 249949716480 bytes
2 heads, 4 sectors/track, 61022880 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md2 doesn't contain a valid partition table

Disk /dev/md1: 106 MB, 106823680 bytes
2 heads, 4 sectors/track, 26080 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

    Device Boot      Start         End      Blocks   Id  System

Disk /dev/dm-0: 247.8 GB, 247833034752 bytes
255 heads, 63 sectors/track, 30130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 2113 MB, 2113929216 bytes
255 heads, 63 sectors/track, 257 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           1          13      104384+  fd  Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/sdc2              13      121601   976655647   fd  Linux raid autodetect

[root@mail ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/main-root
                      224G  2.0G  211G   1% /
/dev/md1               99M   17M   77M  18% /boot
tmpfs                 501M     0  501M   0% /dev/shm
/dev/sdc1              99M   44M   51M  47% /media/USBdisk2

[root@mail ~]# ls -al /media/USBdisk2
total 38698
drwxr-xr-x 4 root root     5120 Jan 20 07:40 .
drwxr-xr-x 3 root root     4096 Feb 28 21:03 ..
-rw-r--r-- 1 root root    70400 Jun  2  2015 config-2.6.18-406.el5
-rw-r--r-- 1 root root    70353 Jun  2  2015 config-2.6.18-406.el5PAE
-rw-r--r-- 1 root root    70400 Nov 11 07:40 config-2.6.18-407.el5
-rw-r--r-- 1 root root    70353 Nov 11 08:20 config-2.6.18-407.el5PAE
-rw-r--r-- 1 root root    70400 Jan 19 08:44 config-2.6.18-408.el5
-rw-r--r-- 1 root root    70353 Jan 19 09:28 config-2.6.18-408.el5PAE
drwxr-xr-x 2 root root     1024 Feb 27 16:42 grub
-rw------- 1 root admin 3469985 Jun  3  2015 initrd-2.6.18-406.el5.img
-rw------- 1 root admin 3472037 Jun  3  2015 initrd-2.6.18-406.el5PAE.img
-rw------- 1 root admin 3469934 Nov 13 07:27 initrd-2.6.18-407.el5.img
-rw------- 1 root admin 3472116 Nov 13 07:27 initrd-2.6.18-407.el5PAE.img
-rw------- 1 root admin 3470001 Jan 20 07:40 initrd-2.6.18-408.el5.img
-rw------- 1 root admin 3472136 Jan 20 07:40 initrd-2.6.18-408.el5PAE.img
drwx------ 2 root root    12288 May 28  2012 lost+found
-rw-r--r-- 1 root root   117544 Jun  2  2015 symvers-2.6.18-406.el5.gz
-rw-r--r-- 1 root root   117561 Jun  2  2015 symvers-2.6.18-406.el5PAE.gz
-rw-r--r-- 1 root root   117544 Nov 11 07:40 symvers-2.6.18-407.el5.gz
-rw-r--r-- 1 root root   117561 Nov 11 08:21 symvers-2.6.18-407.el5PAE.gz
-rw-r--r-- 1 root root   117544 Jan 19 08:44 symvers-2.6.18-408.el5.gz
-rw-r--r-- 1 root root   117561 Jan 19 09:29 symvers-2.6.18-408.el5PAE.gz
-rw-r--r-- 1 root root   996729 Jun  2  2015 System.map-2.6.18-406.el5
-rw-r--r-- 1 root root   994213 Jun  2  2015 System.map-2.6.18-406.el5PAE
-rw-r--r-- 1 root root   996755 Nov 11 07:40 System.map-2.6.18-407.el5
-rw-r--r-- 1 root root   994239 Nov 11 08:20 System.map-2.6.18-407.el5PAE
-rw-r--r-- 1 root root   996755 Jan 19 08:44 System.map-2.6.18-408.el5
-rw-r--r-- 1 root root   994239 Jan 19 09:28 System.map-2.6.18-408.el5PAE
-rw-r--r-- 1 root root  1913332 Jun  2  2015 vmlinuz-2.6.18-406.el5
-rw-r--r-- 1 root root      158 Jun  2  2015 .vmlinuz-2.6.18-406.el5.hmac
-rw-r--r-- 1 root root  1910004 Jun  2  2015 vmlinuz-2.6.18-406.el5PAE
-rw-r--r-- 1 root root      161 Jun  2  2015 .vmlinuz-2.6.18-406.el5PAE.hmac
-rw-r--r-- 1 root root  1912852 Nov 11 07:40 vmlinuz-2.6.18-407.el5
-rw-r--r-- 1 root root      158 Nov 11 07:40 .vmlinuz-2.6.18-407.el5.hmac
-rw-r--r-- 1 root root  1910612 Nov 11 08:20 vmlinuz-2.6.18-407.el5PAE
-rw-r--r-- 1 root root      161 Nov 11 08:20 .vmlinuz-2.6.18-407.el5PAE.hmac
-rw-r--r-- 1 root root  1912852 Jan 19 08:44 vmlinuz-2.6.18-408.el5
-rw-r--r-- 1 root root      158 Jan 19 08:44 .vmlinuz-2.6.18-408.el5.hmac
-rw-r--r-- 1 root root  1910644 Jan 19 09:28 vmlinuz-2.6.18-408.el5PAE
-rw-r--r-- 1 root root      161 Jan 19 09:28 .vmlinuz-2.6.18-408.el5PAE.hmac
[root@mail ~]#

[janet]

bclayton

/dev/sdc1              99M   44M   51M  47% /media/USBdisk2

Well the backup USB disk is partitioned as a RAID device, I am not sure why or how come you did this.
sdc1 is a very small partition, typically a boot partition size of 100M.

Maybe you have backup data on sdc2


Do
umount /dev/sdc1

then do
mount /dev/sdc2 /media/USBdisk2

then do
df -h

then do
ls -al /media/USBdisk2

& show us all the outputs

[bclayton]

Janet,

Not too sure, now.  Here is the output:

[root@mail ~]# umount /dev/sdc1
[root@mail ~]# mount /dev/sdc2 /media/USBdisk2
mount: you must specify the filesystem type
[root@mail ~]# s -al /media/USBdisk2
-bash: s: command not found
[root@mail ~]#
[root@mail ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/main-root
                      224G  2.0G  211G   1% /
/dev/md1               99M   17M   77M  18% /boot
tmpfs                 501M     0  501M   0

[bclayton]

Janet,

I'll be I know what happened.  When the power came back on, I got an email that a RAID had failed.  I assumed that it had kicked out one of the drives because it showed a spare.  Without thinking about the USB backup attached, I added back that drive.  Now, I'll be that action over wrote the USB.  If that is true, is all lost in terms of restoration?

Thanks,
Brooks

[janet]

bclayton

Here is my message, written but as I went to post it, I saw your message.

Yes that is a highly likely scenario, sorry.
Do you have other backups ?


Anyway ....

mount /dev/sdc2 /media/USBdisk2
mount: you must specify the filesystem type

Something seems to be not right with your USB drive.

Read here for some info/tips (first google result I found)
http://askubuntu.com/questions/143718/mount-you-must-specify-the-filesystem-type

and another post here (second google result)
https://www.centos.org/forums/viewtopic.php?t=4092


The mount command should auto mount the partition/file system, so maybe you did not setup the USB drive correctly (no filesystem).

eg this part in the first link:
"There is more to the story here. Usually if you mount a partition with a common filesystem type using mount, it will auto-detect the partition type.
The fact that it isn't auto-detecting it in this case could signal a few possibilities.
    You haven't installed filesystem tools for the chosen filesystem. If you did a standard desktop install of Ubuntu, this shouldn't normally be a problem.
    For example, to mount ntfs drives in recent versions of Ubuntu you need the ntfs-3g package.
    You selected the wrong partition.
    The partition is corrupt or unformatted. In this case, you should probably do a filesystem check (fsck) on it before mounting it. You may then want to proceed to mount it manually, specifying the filesystem type, as read-only. If all else fails you may need special recovery software such as testdisk photorec."


and this part in the second link:

"The message tells you everything you need to know. You have to specify the filesystem type:
Code: Select all
    mount -t ext4 /dev/sdc1 /backup
OR:
Code: Select all
    mount -t ext3 /dev/sdc1 /backup
"


Are you sure you have been running successful backups to this USB drive ?
Do you have email messages indicating a success on backup ?
Please show us one.

It looks like your USB drive was not setup correctly or maybe it is faulty, or ???
Did you ever run the make file system command mkfs
See
https://wiki.contribs.org/USBDisks
in partticular Formatting your USB drive

I am not sure what to tell you now, as you expect that there is a backup on the disk that you want to use to Restore from.

Do you have another USB backup ?

You could try either
mount -t ext4 /dev/sdc2 /media/USBdisk2
or
mount -t ext3 /dev/sdc2 /media/USBdisk2

[bclayton]

Janet,

I afraid the backup is toast.  No, that was the only backup.  I think I have seen post where your recommended more than one.  I think I have learned my lesson the hard way.

Thanks so much for your help!

Brooks

[janet]

Janet,

I'll be I know what happened.  When the power came back on, I got an email that a RAID had failed.  I assumed that it had kicked out one of the drives because it showed a spare.  Without thinking about the USB backup attached, I added back that drive.  Now, I'll be that action over wrote the USB.  If that is true, is all lost in terms of restoration?

Thanks,
Brooks

OK then maybe your only approach now is to troubleshoot the original server.

Physically disconnect the USB drive from the original server.
Then check the RAID failure email (show us) & determine which drive failed, & physically disconnect that also.

Try rebooting the server with only one drive attached in RAID1 degraded mode.
The server will happily run, just give email warnings.

Let us know.