- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: LTO6 media assessment test fails
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-10-2013 10:13 AM
06-10-2013 10:13 AM
LTO6 media assessment test fails
Hi there,
Could someone take a look at the following and let me know why this test is failing:?
- Test 'LTO Drive Assessment test' started on device 'HP Ultrium 6-SCSI' at address '20.0.0[2-/dev/sg11]'
- Operations Log
- LTO Drive Assessment Test Options
- Test Coverage : Default
- Allow Overwrite : True
- executing LTO Drive Assessment Test...
- checking tape load ...
- analyzing device data...
- updating device writeback data...
-
- erasing ...
- soft unload ...
- loading ...
- writing wrap 102 (2.4 m/sec.)
- writing wrap 102 (3.0 m/sec.)
- writing wrap 102 (3.7 m/sec.)
- writing wrap 102 (4.4 m/sec.)
- writing wrap 102 (5.1 m/sec.)
- writing wrap 102 (5.8 m/sec.)
- writing wrap 102 (6.4 m/sec.)
- writing wrap 102 (7.1 m/sec.)
- writing wrap 102 (2.4 m/sec.)
- writing wrap 102 (3.0 m/sec.)
- writing wrap 102 (3.7 m/sec.)
- writing wrap 102 (4.4 m/sec.)
- writing wrap 102 (5.1 m/sec.)
- writing wrap 102 (5.8 m/sec.)
- writing wrap 102 (6.4 m/sec.)
- writing wrap 102 (7.1 m/sec.)
- writing wrap 102 (2.4 m/sec.)
- writing wrap 102 (3.0 m/sec.)
- writing wrap 102 (3.7 m/sec.)
- writing wrap 102 (4.4 m/sec.)
- writing wrap 102 (5.1 m/sec.)
- writing wrap 102 (5.8 m/sec.)
- writing wrap 102 (6.4 m/sec.)
- writing wrap 102 (7.1 m/sec.)
- writing wrap 102 (2.4 m/sec.)
- writing wrap 102 (3.0 m/sec.)
- writing wrap 69 (2.4 m/sec.)
- writing wrap 69 (3.0 m/sec.)
- writing wrap 69 (3.7 m/sec.)
- writing wrap 69 (4.4 m/sec.)
- writing wrap 69 (5.1 m/sec.)
- writing wrap 69 (5.8 m/sec.)
- writing wrap 69 (6.4 m/sec.)
- writing wrap 69 (7.1 m/sec.)
- writing wrap 69 (2.4 m/sec.)
- writing wrap 69 (3.0 m/sec.)
- writing wrap 69 (3.7 m/sec.)
- writing wrap 69 (4.4 m/sec.)
- writing wrap 69 (5.1 m/sec.)
- writing wrap 69 (5.1 m/sec.)
- writing wrap 69 (5.8 m/sec.)
- writing wrap 69 (6.4 m/sec.)
- writing wrap 69 (7.1 m/sec.)
- writing wrap 69 (2.4 m/sec.)
- writing wrap 69 (3.0 m/sec.)
- writing wrap 69 (3.7 m/sec.)
- writing wrap 69 (4.4 m/sec.)
- writing wrap 69 (5.1 m/sec.)
- writing wrap 69 (5.8 m/sec.)
- writing wrap 69 (6.4 m/sec.)
- writing wrap 69 (7.1 m/sec.)
- writing wrap 69 (2.4 m/sec.)
- writing wrap 69 (3.0 m/sec.)
- soft unload ...
- loading ...
- erasing ...
- Test Passed.
- Analysis Results
- LTO Drive Assessment Test, version V19.09.2012
- Test run: Mon Jun 10 18:22:00 2013
- Drive serial number: F0A34xxxxx
- Data Cartridge Information:
- Vendor: FUJIFILM
- Format: LTO-6
- Serial Number: AE0HTxxxxx
- Barcode: XL1075L6
- ANALYSIS OF HISTORICAL INFORMATION (from drive logs):
- version: V05.11.2012
- There were 19 rules and 131 subrules checked.
- Device Analysis has checked the historical information and no problems were found.
- 2.4 m/sec. tape speed:
- Good margin (Data written: 4808.8 MB)
- 3.0 m/sec. tape speed:
- Great margin (Data written: 4808.8 MB)
- 3.7 m/sec. tape speed:
- Great margin (Data written: 3604.2 MB)
- 4.4 m/sec. tape speed:
- Great margin (Data written: 3606.6 MB)
- 5.1 m/sec. tape speed:
- Great margin (Data written: 3606.6 MB)
- 5.8 m/sec. tape speed:
- Great margin (Data written: 3606.6 MB)
- 6.4 m/sec. tape speed:
- Great margin (Data written: 3606.6 MB)
- 7.1 m/sec. tape speed:
- Great margin (Data written: 3606.6 MB)
- forward direction:
- Great margin (Data written: 15626.2 MB)
- reverse direction:
- Great margin (Data written: 15628.6 MB)
- The LTO Drive Assessment Test has checked the history and operation of the selected drive, and
- The test has PASSED and the drive is GOOD.
- Test time: 13:21
Main > Drive Information > Test > Viewer >
--------------------------------------------------------------------------------------------------------------------------------------------
- Test 'LTO Media Assessment test' started on device 'HP Ultrium 6-SCSI' at address '20.0.0[2-/dev/sg11]'
- Operations Log
- LTO Media Assessment Test Options
- Enable Passive Test : True
- Allow Overwrite : True
- Check WORM Integrity : True
- Ignore Cleaning Requests : False
- Allow Suspect Drive : False
- Amount of Media to Test : Default
- Number of Iterations : 1
- executing LTO Media Assessment Test...
- checking tape load ...
- LTO Media Assessment Test Finished...
- Test failed
- Analysis Results
- LTO Media Assessment Test, version V20.08.2012
- Test run: Mon Jun 10 18:41:06 2013
- Drive SN: F0A34xxxxx Firmware Revision: J36Z
- ~RAllow suspect drive~R test option: FALSE
- Drive Assessment Test result: Recently passed, but insufficient margin
- Drive margin reported was 100.0% margin with 0.0% channel variation margin.
- Minimum requirements are >95.0% margin with >95.0% channel variation margin.
- Please run the LTO Drive Assessment Test with new or known good media.
- If the drive is unable to pass the LTO Drive Assessment Test with sufficient
- margin, then it is possible to run the LTO Media Assessment Test with the
- ~QAllow suspect drive~R test option set, but the accuracy of the results cannot be guaranteed.
- Testing has completed and some problems were found.
Main > Drive Information > Test > Viewer >
--------------------------------------------------------------------------------------------------------------------------------------------
- Test 'LTO Media Assessment test' started on device 'HP Ultrium 6-SCSI' at address '20.0.0[2-/dev/sg11]'
- Operations Log
- LTO Media Assessment Test Options
- Enable Passive Test : True
- Allow Overwrite : True
- Check WORM Integrity : True
- Ignore Cleaning Requests : False
- Allow Suspect Drive : True
- Amount of Media to Test : Default
- Number of Iterations : 1
- executing LTO Media Assessment Test...
- checking tape load ...
- erasing ...
- soft unload ...
- loading ...
- writing wrap 4 ...
- writing top wrap ...
- writing bottom wrap ...
- soft unload ...
- loading ...
- erasing ...
- rewinding ...
- LTO Media Assessment Test Finished...
- Test failed
- Analysis Results
- LTO Media Assessment Test, version V20.08.2012
- Test run: Mon Jun 10 18:54:26 2013
- Drive SN: F0A34xxxxx Firmware Revision: J36Z
- ~RAllow suspect drive~R test option: TRUE
- Drive Assessment Test result: Recently passed, but insufficient margin
- Drive margin reported was 100.0% margin with 0.0% channel variation margin.
- Minimum requirements are >95.0% margin with >95.0% channel variation margin.
- MEDIA IDENTITY/CONFIGURATION:
- Vendor: FUJIFILM
- Format: LTO-6
- Capacity: 2.5 TB (native) 4 TB (assuming 2:1 compression)
- Last drive that wrote this tape: F0A34xxxxx (wrote 2.5 MB)
- Serial Number: AE0HTxxxxx
- Barcode: XL1075L6
- Manufactured: Jan 16 2013
- ANALYSIS OF HISTORICAL INFORMATION (from drive logs)
- [Please check the Support Ticket for full details.]
- Media Health
- Data on tape: Not enough data
- Drive measurements: Great margin
- Write/read life: Great margin
- Load/unload life: Great margin
- Media Environment
- Maximum temperature has not been exceeded in the last 3 drives.
- RESULTS OF TESTS ON THIS MEDIA
- [Please note: the operations performed by this overwrite test will NOT be
- reflected in the Support Ticket usage/health information.]
- Amount of data required~R test option : Default
- Iteration number: 1 of 1
- The drive could not write data to the data cartridge with sufficient margin.
- Overall Margin: Warning (0 KB written)
- The default test options were not used for the test, so the results cannot be guaranteed.
- Testing has completed and some problems were found.
What are these "rules" and "subrules"?
What is the "channel variation margin"?
Anywhere to read up on that?
Any help is greatly appreciated.
Bye,
Marki
- Tags:
- LTT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2013 08:56 AM - edited 06-11-2013 09:04 AM
06-11-2013 08:56 AM - edited 06-11-2013 09:04 AM
Re: LTO6 media assessment test fails
What LTT version was used? Could you attach the support ticket?
Version 4.16 is here:
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2013 04:32 AM
06-12-2013 04:32 AM
Re: LTO6 media assessment test fails
LOL
Ok 4.16 (out 2 days ago) seems to fix the problem:
4.15:
- Minimum requirements are >95.0% margin with >95.0% channel variation margin.
4.16:
- Minimum requirements are >95.0% margin with <5.0% channel variation.
So, the check was just implemented wrong.