Activity › Forums › Storage & Archiving › Can’t access Tolis Support – Need to restore tape contents to RAID
-
Can’t access Tolis Support – Need to restore tape contents to RAID
Joel Brun replied 4 years, 10 months ago 11 Members · 50 Replies
-
Jim Curtis
September 3, 2020 at 1:03 amIf you mean tapectl c, I get this, the Help Menu:
JPC@2019-Mac-Pro ~ % tapectl c
tapectl [-V] [-v] [-f dev] arg [count]
Version 12.0
Devices are known by the names ntapeX where X is the device order number
starting with 0 and incrementing for each tape device found.
arg is one of:
display – displays available tape devices
status – display currrent drive status
header – read the first 4K of a tape and display on stdout
fsf [x] – forward space filemark (x = count; 1 is default)
Tape is positionready to write on the EOT side of
the filemark ready to read.
bsf [x] – back space filemark (like fsf, but backwards)
Tape is positioned on the EOT side of the previous
filemark ready to read
wfm [x] – write filemark (x = count; 1 is default)
seod – space to end of data for appends
erase – short erase a tape
lerase – long (secure) erase – takes hours!
load – load tape into drive
rewind – rewinds a tape
rewoff – rewind the tape and unload it
tell – report current logical tape block
seek x – seek to logical tape block ‘x’
setblk x – set drive block size to x (x is required, 0 = variable block)
alert – display TapeAlert information if available
unload – same as rewoff
unltfs – Unformat an LTFS volume returning it to use as a standard
data tape. Any LTFS data will be lost.
-f dev – device to access – (ntape0 is default)
-v – additional verbosity while working
-V – version and copyright information
JPC@2019-Mac-Pro ~ %I’m sorry to be wasting your time.
I don’t think anybody is at home at Tolis. Maybe they have gone under. I wish I knew, because it’s been days since I asked for support, and I haven’t heard a thing from them.
Jim Curtis
jamesphilipcurtis.comMacPro7,1 24-core – 256 GB RAM – AMD Radeon Pro Vega II 32 GB – 10.15.6
-
James Vorley
September 3, 2020 at 1:55 amJust to confirm you need to run these commands with the tape loaded in the drive.
Steps are: eject tape, power cycle drive, reboot Mac.
Open terminal, enter:
bru -xvvvf ntape0 “/Volumes/SAS RAID/ANTHEM restore from LTO"If the tape imports, rejoice. If not, read on…
If you then get this message:
bru: [W130] warning - read error on first block: errno = 5, Input/output error
bru: [A121] load volume 1 - press ENTER to continue on device 'ntape0'press enter.
Then without power cycling eject tape and insert a tape that you know works on your new Mac.
Hit C to continue.
Does it import the new known good tape?
-
James Vorley
September 3, 2020 at 2:09 amCorrection: Steps are: eject tape, power cycle drive, reboot Mac, insert tape
-
Jim Curtis
September 3, 2020 at 2:13 amI followed your steps, and the Terminal replies:
dquote>
Don’t I have to enter some form of tapectl first?
Jim Curtis
jamesphilipcurtis.comMacPro7,1 24-core – 256 GB RAM – AMD Radeon Pro Vega II 32 GB – 10.15.6
-
Jim Curtis
September 3, 2020 at 2:17 amSo, I tried:
tapectl bru -xvvvf ntape0 “/Volumes/SAS RAID/ANTHEM restore from LTO”
and this familiar text happened:
bru: [W130] warning – read error on first block: errno = 5, Input/output error
bru: [A121] load volume 1 – press ENTER to continue on device ‘ntape0’
bru: [Q120] (C)ontinue (N)ew device (Q)uit [default: C] >> C
bru: [W130] warning – read error on first block: errno = 5, Input/output error
bru: [A121] load volume 1 – press ENTER to continue on device ‘ntape0’
bru: [Q120] (C)ontinue (N)ew device (Q)uit [default: C] >>So, I put in a known good tape, pressed C then ENTER, and it repeated:
bru: [W130] warning – read error on first block: errno = 5, Input/output error
bru: [A121] load volume 1 – press ENTER to continue on device ‘ntape0’
bru: [Q120] (C)ontinue (N)ew device (Q)uit [default: C] >>Jim Curtis
jamesphilipcurtis.comMacPro7,1 24-core – 256 GB RAM – AMD Radeon Pro Vega II 32 GB – 10.15.6
-
James Vorley
September 3, 2020 at 6:26 amThat means there is only one “ and you’re missing one at the end of the path.
You do not need to use tapectl now.
-
James Vorley
September 8, 2020 at 9:49 amFor anyone who may be experiencing a similar issue…
Jim and I investigated further and the problem seemed to be that the Argest tape import tool would not recognise the 128K block size of the problem tape.
We were able to change the bufsize in bruxpat config to 128K and then use terminal to import the entirety of the data on the tape using sudo bru -xvvv
bufsize can also be set with the -b flag which will override bruxpat eg sudo bru -b=128K -xvvv
-
Jim Curtis
September 8, 2020 at 11:44 amA big shout out here to James who went to what I consider heroic efforts to find a solution that would allow me to import my tape contents. Thank you, James!
I still haven’t heard a peep from Tolis.
Might be helpful to others to add that the Terminal command that worked only worked because the tape & Terminal were looking for the original file path written to the tape. I had to mount an external drive and change the drive name to the name of the RAID partition that held the original archive media.
-
Robert Ober
September 14, 2020 at 4:39 pm -
Jim Curtis
September 21, 2020 at 11:16 pmRobert, I did write to Tolis at that email weeks ago, and I STILL haven’t heard back from them. Or him, whichever the case may be. I’m starting to think Tolis is one or three people.
Reply to this Discussion! Login or Sign Up