-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to mount previous written tape #446
Comments
This comment was marked as abuse.
This comment was marked as abuse.
Just an update... it seems to work with tapes created with the LTFS version currently running... |
It is not a compatibility issue at all. It looks LTFS found inconsistency of the tape (logical inconsistency). A typical scenario is stop machine without unmouting LTFS. |
OK, but is there a way to fix it? If I remove the write-protection on the take, will it fix the issue while mounting, or do we need to run ltfsck ? |
I don't think so. I have never saw such kind of problems at all.
I'm little bit confused. Because you stated you never remember which version was used for write. Send a pair of log, write side and read side if you can recreate the problem. I would like to have log which is out under |
I cannot find any ltfs related logfiles in /var/log ? |
Well we managed to mount a few tapes by just removing the write-protection... but we have one which seems to have other issues...
|
LTFS calls syslog with default ( Sample is available under |
I don't think this is not similar to the original problem at all. In this case, the first block in the partition 0 seems to be overwritten by a FM. Someone must overwrite it, LTFS never write a FM at the beginning of a partition at all! It looks this is similar to #431. Did you check the drive condition by |
We might not have been aware of the dangers of the st driver. I did read the #431 post and have blocked the st driver. |
Need to inspect all data on tape first. I strongly recommends to rewrite it if you have another copy on disk or another tape. |
We have the data on disk as well, but "non-spinning" disks, so it's a bit of an effort to get them setup again :-) |
This kind of corruption is out-of-scope of Indeed, you could fix the tapes if you have a strong confidence that the label is simply just overwritten. But you need to do it yourself by issuing low level SCSI command with tape drive's specification documents. (I don't think I can spent my time to help you in this area for free.) Finally, I will give you a couple of suggestions.
|
Close because of no activity for a long time. |
Unable to mount previously written tape from older version of LTFS. (written about 1 year ago, cannot remember ltfs version)
Tried with different tapes with same result...
(The tapes are set at read-only, can that be the issue?)
Ubuntu 22.04LTS, blacklisted the "st" driver.
LTFS version 2.5.0.0 (Prelim).
LTFS Format Specification version 2.4.0.
IBM ULTRIUM-HH8
This is how I mount...
The text was updated successfully, but these errors were encountered: