Welcome to our community
Be a part of something great, join today!
Anyone using LTFS with LTO-5?
- Thread starter Kenn Michael
- Start date
The GUI is running the command line scripts for you. If you tab over to the Diagnostics page (the last tab on the right in the GUI) you'll see a window that echoes the command line. If there are any error messages being returned, you'll see them here.
Have you tried multiple LTO cartridges? And have you formatted them prior to attempting to mount them?
Tim Jones
Well-known member
- Joined
- Dec 16, 2008
- Messages
- 316
- Reaction score
- 0
- Points
- 0
- Location
- Huntsville, AL, USA
- Website
- www.productionbackup.com
ltfsck may work here
ltfsck may work here
Sorry to be late to this thread -
The message that you're seeing - LTFS11027E Cannot mount volume: medium consistency check failed - is an error that a number of users have reported and it seems to be related to the last write on the tape in question. Apparently, if the tape was unmounted before the index is updated (power is lost during a write, drive is reset during the write, tape is "force ejected" from your desktop, LTFS layer crashes during a write) this can happen leaving the tape is a bad state (something that generally doesn't happen with normal tape software that doesn't try to treat tape as a random access medium :frown2
. You generally won't see this if these things happen while simply reading the tape.
Try this command if you have HP's tools installed:
the "0" is the first drive. If you have more than one drive, you'll need to experiment to determine which number is which drive.
If this does not recover the tape, you can try changing the --full-recovery to --deep-recovery.
Oh, and get a cup of coffee or tea (which ever your preference) and a Netflix movie, because this can take quite a while.
ltfsck may work here
Sorry to be late to this thread -
The message that you're seeing - LTFS11027E Cannot mount volume: medium consistency check failed - is an error that a number of users have reported and it seems to be related to the last write on the tape in question. Apparently, if the tape was unmounted before the index is updated (power is lost during a write, drive is reset during the write, tape is "force ejected" from your desktop, LTFS layer crashes during a write) this can happen leaving the tape is a bad state (something that generally doesn't happen with normal tape software that doesn't try to treat tape as a random access medium :frown2
. You generally won't see this if these things happen while simply reading the tape.Try this command if you have HP's tools installed:
/usr/local/bin/ltfsck 0 --full-recovery
the "0" is the first drive. If you have more than one drive, you'll need to experiment to determine which number is which drive.
If this does not recover the tape, you can try changing the --full-recovery to --deep-recovery.
Oh, and get a cup of coffee or tea (which ever your preference) and a Netflix movie, because this can take quite a while.
Thanks very much for your responses guys! Tim, I'll give that a go tomorrow. I think this is what happened but the odd thing is that it just threw the error while in the middle of writing, no force eject or power cut. And then after that it refused to mount. Sounds like a full recovery could be a winner.
M Most, the errors that the GUI displays do not give you any means with which to deal with them, hence the need for the command line.
M Most, the errors that the GUI displays do not give you any means with which to deal with them, hence the need for the command line.
Tim Jones
Well-known member
- Joined
- Dec 16, 2008
- Messages
- 316
- Reaction score
- 0
- Points
- 0
- Location
- Huntsville, AL, USA
- Website
- www.productionbackup.com
Hmmm, that sounds like it could be interference from OS X's Spotlight (mdimporter) or possibly the fsevents monitor. Also, is your drive connected via direct SAS or Thunderbolt to SAS?
Tim
It's connected direct via SAS. Ok, so now the tape drive won't mount any tape so I think I may have done something wrong in the Terminal! I've spoken to HP and they seem to think it might be a Firmware issue so they're sending me a new drive as there is no Firmware updater for Macs (every other OS except Macs).
This is bizarre.
This is bizarre.
Tim Jones
Well-known member
- Joined
- Dec 16, 2008
- Messages
- 316
- Reaction score
- 0
- Points
- 0
- Location
- Huntsville, AL, USA
- Website
- www.productionbackup.com
You can update firmware on a Mac
You can update firmware on a Mac
What software are you using besides LTFS with that drive? Do you have BRU PE, by chance? I'm curious about the firmware version.
As to what the HP rep told you
, there is a version of L&TT for Mac. I can't link you directly, but this page will get you there:
HP L&TT Info Page
In the gray box in the upper right of that page, click the "Link to free download" link and you'll see the OS X versions at the top of the list. You use this with the .frm files that you can download (I use the Linux files since OS X can extract the zip file) for your drive and you can flash the latest firmware.
With that aside, we've not had any issues with LTFS and firmware versions going all the way back to the original public release version (3 years ago???).
One last piece that I don't see mentioned - are you using an ATTO ExpressSAS or RAID card? The other vendors' cards (Highpoiint, Areca, Adaptec, etc.) don't work properly with tape on a Mac system.
You can update firmware on a Mac
What software are you using besides LTFS with that drive? Do you have BRU PE, by chance? I'm curious about the firmware version.
As to what the HP rep told you
, there is a version of L&TT for Mac. I can't link you directly, but this page will get you there:HP L&TT Info Page
In the gray box in the upper right of that page, click the "Link to free download" link and you'll see the OS X versions at the top of the list. You use this with the .frm files that you can download (I use the Linux files since OS X can extract the zip file) for your drive and you can flash the latest firmware.
With that aside, we've not had any issues with LTFS and firmware versions going all the way back to the original public release version (3 years ago???).
One last piece that I don't see mentioned - are you using an ATTO ExpressSAS or RAID card? The other vendors' cards (Highpoiint, Areca, Adaptec, etc.) don't work properly with tape on a Mac system.
Hi Tim,
Thanks so much for taking the time to respond to this. To be honest the HP guys don't seem to know too much although they are trying to help. I now have new tape drive and exactly the same issue. It's connected with an ATTO card. Really bizarre...
Thanks so much for taking the time to respond to this. To be honest the HP guys don't seem to know too much although they are trying to help. I now have new tape drive and exactly the same issue. It's connected with an ATTO card. Really bizarre...
Are you running OS X 10.8.3? I've run into some permissions errors, but if you use the command line to mount the tape, and invoke it using sudo, it should work. The command line to mount an LTFS volume is very simple as long as you've already created the mount point (i.e., "sudo ltfs /ltfsmount").
Tim Jones
Well-known member
- Joined
- Dec 16, 2008
- Messages
- 316
- Reaction score
- 0
- Points
- 0
- Location
- Huntsville, AL, USA
- Website
- www.productionbackup.com
I wish that you were an isolated case, but LTFS is giving a lot of people problems.
Here's how I would further test your environment:
Use the command line "unltfs" command to clear a tape:
sudo /usr/local/bin/unltfs -d 0 -y
Then, format and mount that tape as LTFS with either BRU PE or HP's OpenStore Manager
Copy a few GBs of clips to the tape
Unmount the tape from your desktop
Remove the tape
Power cycle the drive
Reload and mount the tape
Access the files on the tape volume
Does that work? If so, it simply means tha the tapes you had been using have somehow had the LTFS index partition scrambled beyond recovery. If it doesn't work, I'm with HP in that there doesn't seem to be a valid reason for the failure. If you would like me to take a look at one of your failing tapes with our lab tools, send me a PM and I'll set something up for you.
This is why being able to verify your tapes before you need them for recovery is so important (and unbelievably a feature missing form LTFS).
Tim
Here's how I would further test your environment:
Use the command line "unltfs" command to clear a tape:
sudo /usr/local/bin/unltfs -d 0 -y
Then, format and mount that tape as LTFS with either BRU PE or HP's OpenStore Manager
Copy a few GBs of clips to the tape
Unmount the tape from your desktop
Remove the tape
Power cycle the drive
Reload and mount the tape
Access the files on the tape volume
Does that work? If so, it simply means tha the tapes you had been using have somehow had the LTFS index partition scrambled beyond recovery. If it doesn't work, I'm with HP in that there doesn't seem to be a valid reason for the failure. If you would like me to take a look at one of your failing tapes with our lab tools, send me a PM and I'll set something up for you.
This is why being able to verify your tapes before you need them for recovery is so important (and unbelievably a feature missing form LTFS).
Tim
When you say "Use the command line "unltfs" command to clear a tape:" you don't mean on one of my good tapes with all my data surely? Do you mean with a blank tape?
I tried the command with a blank tape and it throws back this message:
dyld: Symbol not found: _UCNV_TO_U_CALLBACK_STOP_4_0
Referenced from: /Library/Frameworks/LTFS.framework/Versions/Current/usr/lib/libltfs.2.0.0.dylib
Expected in: /Library/Frameworks/ICU.framework/Versions/Current/usr/lib/libicu.40.1.dylib
in /Library/Frameworks/LTFS.framework/Versions/Current/usr/lib/libltfs.2.0.0.dylib
Trace/BPT trap
Is there something missing from my Library?
I tried the command with a blank tape and it throws back this message:
dyld: Symbol not found: _UCNV_TO_U_CALLBACK_STOP_4_0
Referenced from: /Library/Frameworks/LTFS.framework/Versions/Current/usr/lib/libltfs.2.0.0.dylib
Expected in: /Library/Frameworks/ICU.framework/Versions/Current/usr/lib/libicu.40.1.dylib
in /Library/Frameworks/LTFS.framework/Versions/Current/usr/lib/libltfs.2.0.0.dylib
Trace/BPT trap
Is there something missing from my Library?
Tim Jones
Well-known member
- Joined
- Dec 16, 2008
- Messages
- 316
- Reaction score
- 0
- Points
- 0
- Location
- Huntsville, AL, USA
- Website
- www.productionbackup.com
No - I meant to do that with one of your questionable / bad tapes.
However ...
That is indicative of a bad LTFS driver installation. The specific error indicates that the ICU package hasn't been properly installed (why it's needed, no one can tell me other than it was part of IBM's original source files). Check your DMG that you installed LTFS from and make sure that you install the ICU package.
Tim
However ...
That is indicative of a bad LTFS driver installation. The specific error indicates that the ICU package hasn't been properly installed (why it's needed, no one can tell me other than it was part of IBM's original source files). Check your DMG that you installed LTFS from and make sure that you install the ICU package.
Tim
Tim Jones
Well-known member
- Joined
- Dec 16, 2008
- Messages
- 316
- Reaction score
- 0
- Points
- 0
- Location
- Huntsville, AL, USA
- Website
- www.productionbackup.com
You'll need to download the package from the HP site. I can't direct link because of the way their servers do links, but this is the top page that you'll use to get to the downloads:
HP LTFS Downloads
HP LTFS Downloads
Tim Jones
Well-known member
- Joined
- Dec 16, 2008
- Messages
- 316
- Reaction score
- 0
- Points
- 0
- Location
- Huntsville, AL, USA
- Website
- www.productionbackup.com
Correct. The "open source" file is the source code and even I have problems compiling that hodge-podge of source (and I've been at this stuff since 1978 :bored: ).
Tim Jones
Well-known member
- Joined
- Dec 16, 2008
- Messages
- 316
- Reaction score
- 0
- Points
- 0
- Location
- Huntsville, AL, USA
- Website
- www.productionbackup.com
Also, I forgot to mention that it also means that your existing tapes are probably okay and will be recoverable using ltfsck after you get the drivers restabilized.
Excellent, you were absolutely right! So it seems I can now mount all my old tapes fine (except the latest) and the StoreOpen app works as it should. That's one HUGE relief. Now it's back to the issue that triggered all of this to begin with, because my last tape won't mount. StoreOpen says this in the logs:
Mount volume
LTFS9015W Setting the locale to 'en_US.UTF-8'. If this is wrong, please set the LANG environment variable before starting ltfs.
LTFS14000I LTFS starting, LTFS version 2.0.0, log level 2
LTFS14058I LTFS Format Specification version 2.0.0
LTFS14063I Sync type is "time", Sync time is 300 sec
LTFS20013I Drive type is HP LTO5, serial number is XXXXXXXXX
LTFS17160I Maximum device block size is 524288
LTFS11005I Mounting the volume
LTFS12015I Attempting to load the medium
LTFS11026I Performing a full medium consistency check
Entity: line 1: parser error : Document is empty
13780100925805C14E56080046020226
^
LTFS17037E XML parser: failed to read from XML stream
LTFS17016E Cannot parse Index (direct from medium)
LTFS11194W Cannot read Index: failed to read and parse XML data (-1014)
LTFS11220E Medium check failed: extra blocks were detected on the medium. Please run ltfsck.
LTFS11027E Cannot mount volume: medium consistency check failed
LTFS14013E Cannot mount the volume
LTFS20076I Triggering drive diagnostic dump
LTFS20096I Diagnostic dump complete
LTFS session finished
This is what happened initially: I successfully wrote two Mac Finder folders to the tape, checked them back, all good, deleted originals from the Mac. In another session, I started writing another batch of folders when it threw up some kind of error, something about write failed. So I went through the usual procedure of un-mounting and ejecting. It was after this that the tape stopped mounting. The first batch of data is not backed up anywhere else, so it's critical that I retrieve them, I'm not bothered about the rest.
So I've just tried typing the command usr/local/bin/ltfsck 0 --full recovery but I got this:
Ces:~ ces$ /usr/local/bin/ltfsck 0 --full-recovery
LTFS16000I ltfsck starting, LTFS version 2.0.0, log level 2
LTFS20013I Drive type is HP LTO5, serial number is XXXXXXXX
LTFS17160I Maximum device block size is 524288
LTFS12015I Attempting to load the medium
LTFS16014I Checking LTFS file system on '0'
LTFS12015I Attempting to load the medium
LTFS16023I LTFS volume information:
LTFS16024I Volser(Barcode) :
LTFS16025I Volume UUID : 93c8865c-d116-432f-a0cd-1ae1d6efa815
LTFS16026I Format Time : 2013-03-15 17:25:43.397929000 GMT
LTFS16027I Block Size : 524288
LTFS16028I Compression : Enabled
LTFS16029I Index Partition : ID = a, SCSI Partition = 0
LTFS16030I Data Partition : ID = b, SCSI Partition = 1
LTFS11005I Mounting the volume
LTFS12015I Attempting to load the medium
LTFS11026I Performing a full medium consistency check
Entity: line 1: parser error : Document is empty
13780100925805C14E56080046020226
^
LTFS17037E XML parser: failed to read from XML stream
LTFS17016E Cannot parse Index (direct from medium)
LTFS11194W Cannot read Index: failed to read and parse XML data (-1014)
LTFS11223I Generating lost and found directory
LTFS11230I Writing Index(es) to restore consistency
LTFS12047E Cannot write file marks: backend call failed (-1). Dropping to read-only mode.
LTFS11082E Cannot write Index: write file mark failed (-1)
LTFS11031I Volume mounted successfully
LTFS11032I Unmounting the volume
LTFS11033E Cannot unmount: failed to write an Index
LTFS16022I Volume is consistent
Ces:~ ces$
Mount volume
LTFS9015W Setting the locale to 'en_US.UTF-8'. If this is wrong, please set the LANG environment variable before starting ltfs.
LTFS14000I LTFS starting, LTFS version 2.0.0, log level 2
LTFS14058I LTFS Format Specification version 2.0.0
LTFS14063I Sync type is "time", Sync time is 300 sec
LTFS20013I Drive type is HP LTO5, serial number is XXXXXXXXX
LTFS17160I Maximum device block size is 524288
LTFS11005I Mounting the volume
LTFS12015I Attempting to load the medium
LTFS11026I Performing a full medium consistency check
Entity: line 1: parser error : Document is empty
13780100925805C14E56080046020226
^
LTFS17037E XML parser: failed to read from XML stream
LTFS17016E Cannot parse Index (direct from medium)
LTFS11194W Cannot read Index: failed to read and parse XML data (-1014)
LTFS11220E Medium check failed: extra blocks were detected on the medium. Please run ltfsck.
LTFS11027E Cannot mount volume: medium consistency check failed
LTFS14013E Cannot mount the volume
LTFS20076I Triggering drive diagnostic dump
LTFS20096I Diagnostic dump complete
LTFS session finished
This is what happened initially: I successfully wrote two Mac Finder folders to the tape, checked them back, all good, deleted originals from the Mac. In another session, I started writing another batch of folders when it threw up some kind of error, something about write failed. So I went through the usual procedure of un-mounting and ejecting. It was after this that the tape stopped mounting. The first batch of data is not backed up anywhere else, so it's critical that I retrieve them, I'm not bothered about the rest.
So I've just tried typing the command usr/local/bin/ltfsck 0 --full recovery but I got this:
Ces:~ ces$ /usr/local/bin/ltfsck 0 --full-recovery
LTFS16000I ltfsck starting, LTFS version 2.0.0, log level 2
LTFS20013I Drive type is HP LTO5, serial number is XXXXXXXX
LTFS17160I Maximum device block size is 524288
LTFS12015I Attempting to load the medium
LTFS16014I Checking LTFS file system on '0'
LTFS12015I Attempting to load the medium
LTFS16023I LTFS volume information:
LTFS16024I Volser(Barcode) :
LTFS16025I Volume UUID : 93c8865c-d116-432f-a0cd-1ae1d6efa815
LTFS16026I Format Time : 2013-03-15 17:25:43.397929000 GMT
LTFS16027I Block Size : 524288
LTFS16028I Compression : Enabled
LTFS16029I Index Partition : ID = a, SCSI Partition = 0
LTFS16030I Data Partition : ID = b, SCSI Partition = 1
LTFS11005I Mounting the volume
LTFS12015I Attempting to load the medium
LTFS11026I Performing a full medium consistency check
Entity: line 1: parser error : Document is empty
13780100925805C14E56080046020226
^
LTFS17037E XML parser: failed to read from XML stream
LTFS17016E Cannot parse Index (direct from medium)
LTFS11194W Cannot read Index: failed to read and parse XML data (-1014)
LTFS11223I Generating lost and found directory
LTFS11230I Writing Index(es) to restore consistency
LTFS12047E Cannot write file marks: backend call failed (-1). Dropping to read-only mode.
LTFS11082E Cannot write Index: write file mark failed (-1)
LTFS11031I Volume mounted successfully
LTFS11032I Unmounting the volume
LTFS11033E Cannot unmount: failed to write an Index
LTFS16022I Volume is consistent
Ces:~ ces$