Support Bulletins
This is the place to find all support bulletins.
All Products
-
Product Bulletin #110 Quantum products which utilize Adobe Flash will encounter issues when Flash EOL’s on January 12th, 2021.Jan 2021
-
Product Bulletin #107 Recommended Cleaning Instructions for Quantum ProductsApr 2020
ActiveScale Products
-
Product Bulletin #55 Data unavailability (DU) might occur as storage column(s) approach full.Jan 2022
Disk Based Products
-
Product Alert #54 DXi systems using software version 4.1.0 might be at risk of data corruption when using Synthetic backup operations.Sep 2020
F-Series and H-Series
-
Product Alert #60 An upgrade a H-Series (H20xx or H40xx) from version 1.x to version 2.0.1, the system does not properly update its NVD timeout valuesAug 2022
-
Product Bulletin #111 Statement on Red Hat Changes to CentOS Programs (F2000)Jan 2021
-
Product Bulletin #108 Fibre Channel hosts do not reconnect after an F2000 note fails backApr 2020
StorNext Product
-
StorNext Product Alert #175 Customer advisory for M-Series with Toshiba SSD that will fail after reaching approx. 70,000 power on hours.Dec 2023
-
StorNext Product Alert #52 The Disk Scrub Interval setting might cause undue wear on drives and impact performance.Jul 2020
-
StorNext Product Bulletin #109 Required Upgrade CheckJuly 2020
-
StorNext Product Alert #51 sgoffload and sgdefrag can corrupt files containing resource forks residing in named streamsJan 2020
-
StorNext Product Alert #50 Potential data missing on tape deviceJan 2020
-
StorNext Product Bulletin #106 Quantum StorNext® Gen 2 Appliances using Appliance Controller (NAS) 2.3.0 or lower with QXS- 484 12G attached storage arraysOct 2019
-
StorNext Product Bulletin #105 Affected systems experience out of memory condition when running Cloud Based Analytics (CBA).Aug 2019
-
StorNext Product Bulletin #104 SSL certificates required for appliances to upload data to the Cloud-Based Analytics portal will expire on July 19, 2019. A new cert.pem certificate file must be applied to each appliance prior to July 19, 2019 for report data uploads and system monitoring to continue.Jul 2019
-
StorNext Product Bulletin #103 Use of the File Per Table Conversion script can cause database inconsistenciesApr 2019
-
StorNext Product Bulletin #102 Renames of files or directories from one directory into another may corrupt the Metadata Archive and make it unusable for a subsequent metadata restore.Jan 2019
-
StorNext Product Bulletin #101 Metadata conversion process may cause StorNext 5x upgrades to StorNext 6.0.5 to panicNov 2017
-
StorNext Product Bulletin #100 Multi-Part uploads are not handling all error conditions.Nov 2017
-
StorNext Product Alert #49 The scheduled removal of inactive instances of files from a managed file system may remove more instances than configured to be removed.Apr 2018
-
StorNext Product Alert #48 Problem: Data within a managed file system may not be protected when using StorNext 5.4.0.3Jun 2017
-
StorNext Product Alert #47 Problem: After upgrading from StorNext 4.x to StorNext 5.x the metadump should be rebuilt.Aug 2016
-
StorNext Product Bulletin #98 Problem: A configuration file is removed when upgrading to StorNext 5.3.2 using the StorNext GUI.Jul 2016
-
StorNext Product Bulletin #97 End of product support dates and support levelsApr 2016
-
StorNext Product Alert #46 Incomplete restore and/or corrupt metadumpSep 2015
-
StorNext Product Bulletin #87 Announcing the extension of Limited Support phase by 12 monthsJul 2015
-
StorNext Product Bulletin #94 Announcing End of Support for StorNext® 4.2Dec 2014
-
StorNext Product Bulletin #93 2014-7169 (aka Shellshock) may cause compatibility issues with StorNext Perl scripts that could result in an inability to run StorNext features and commands.Dec 2014
-
StorNext Product Alert #45 In rare cases, StorNext Storage Manager customers may encounter a Linux problem that can cause a duplicate data block. The problem is isolated to instances where a pse_snapshot is collected during a store to tape. No data is lost, but intervention is required to correctly retrieve the entire file and remove the duplicate block.Mar 2014
-
StorNext Product Bulletin #92 Firmware bundle version CF100R38-02 may encounter a PCIe MTO error resulting in multiple controller hangs and performance degradation.Oct 2013
-
StorNext Product Bulletin #91 An MDC which is dedicated to StorNext with no other applications present encounters a persistent reservation placed on a tape drive by a non-StorNext application thus preventing StorNext from using the drive.Oct 2013
-
StorNext Product Bulletin #90 StorNext Storage Manager problem after upgrade to 4.7.0.Oct 2013
-
StorNext Product Bulletin #89 Announcing Availability of StorNext FX 4.7 and End of Support for StorNext FX 2.x.Oct 2013
-
StorNext Product Bulletin #88 When modifying the “File Age Before Truncation” value for a policy class, the default value for file copies is unexpectedly changed.Aug 2013
-
StorNext Product Alert #44 Before upgrading from a StorNext release prior to 4.2.2 to 4.2.2 or later, the file system may need a special cvfsck binary executed to repair some of the inodes.Aug 2013
-
StorNext Product Alert #43 cvcp does not verify the number of command line arguments, which can cause it to overwrite files if not used correctly.Aug 2013
-
StorNext Product Bulletin #86 Checksum information for a file is dropped during tape consolidation.Apr 2013
-
StorNext Product Alert #42 After upgrading from Linter to MySQL, primary keys in database tables are missing.Mar 2013
-
StorNext Product Bulletin #85 StorNext-created user and group IDs must be identical on both nodes of a high availability pair.Oct 2012
-
StorNext Product Bulletin #84 When installing an Operating System the installation program may prompt the User to initialize the StorNext disks. If the wrong selection is made the installation program could initialize the labels of the disk and the clients will not be able to mount the StorNext file system.Nov 2012
-
StorNext Product Bulletin #83 StorNext Management Suite database records may be missing or incorrectNov 2012
-
StorNext Product Bulletin #82 StorNext Partial File Retrieval product not supported in VM (Virtual Machine) mode.Jun 2012
-
StorNext Product Alert #39 Potential data integrity issues when defragmenting or migrating stub filesApr 2012
-
StorNext Product Bulletin #81 The Windows Operating System can re-allocate a port number that was granted to the StorNext fsmpm port to another application.May 2012
-
StorNext Product Bulletin #80 Edit of filesystem via GUI loses custom changes in fstab.Jul 2012
-
StorNext Product Bulletin #79 Windows Client deleting/renaming file permissions issuesMar 2012
-
StorNext Product Bulletin #78 Announcing end of support for StorNext 3.5.xJun 2012
-
StorNext Product Bulletin #75 StorNext file system CIFS Server may leak memoryJan 2012
-
StorNext Product Bulletin #72 Using EMC PowerPath or other third-party multipath drivers may require configuring cvpathsApr 2012
-
StorNext Product Alert #41 Do not change or remove source replication policies in Storage Manager environments while files are being stored.May 2011
-
StorNext Product Bulletin #71 Support for enabling ACLs for Apple Xsan clientsMay 2011
-
StorNext Product Bulletin #70 Kernel or complete memory dumps need to be enabled for Quantum to provide complete problem analysisApr 2011
-
StorNext Product Bulletin #64 Recommendation for saving StorNext logsFeb 2011
-
StorNext Product Bulletin #73 Xsan 2.3 must be configured case-sensitive for StorNext FX compatibilityAug 2011
-
StorNext Product Bulletin #76 StorNext customers using the Data Movement Integrity Check Option can receive false checksum errors for correctly recoverable files.Oct 2011
-
StorNext Product Bulletin #50 Performance for Linux systems on kernel 2.6.10 and higher can be optimized by changing the default I/O schedulerDec 2011
-
StorNext Product Bulletin #56 Backup failures are possible when Xsan clients utilize managed file systems using Stornext MDCsJun 2010
-
StorNext Product Bulletin #55 StorNext MDC may fail when running on WindowsMay 2010
-
StorNext Product Bulletin #54 Announcing the general availability of StorNext version 3.5.2.Mar 2010
-
StorNext Product Bulletin #53 EFI label limitations for Solaris users.May 2010
-
StorNext Product Bulletin #52 A StorNext client may cause a blue screen error when running on Windows Vista, Windows Server 2008 (including R2), Windows 7, or subsequent Windows releasesMay 2010
-
StorNext Product Bulletin #51 Do not use the NFS subtree_check optionApr 2010
-
StorNext FX Product Bulletin #52 A StorNext client may cause a blue screen error when running on Windows Vista, Windows Server 2008 (including R2), Windows 7, or subsequent Windows releasesMay 2010
-
StorNext FX Product Bulletin #44 Validation Announcement - StorNext FX 2.0 client software and Apple Xsan version 2.2Nov 2009
-
StorNext FX Product Bulletin #15 Inability to mount more than one SNFS file system on a Windows serverJun 2006
-
StorNext FX Product Alert #12 Possible data corruption when multiple data writes target a single fileJun 2006
-
StorNext FX Product Alert #9 Expanding Stripe Group Bandwidth Using the Windows Configuration Administrator GUI will product incorrect file system configuration files causing data corruptionMay 2006
-
StorNext FX Product Alert #7 Possible data corruption if raw devices are configured incorrectlyFeb 2006
-
StorNext FX Product Bulletin #12 StorNext is now certified with AIX 5.3 and IRIX 6.5.27 and 6.5.28Nov 2005
-
StorNext FX Product Bulletin #11 Possible Data Corruption when Modifying File AttributesJul 2005
-
StorNext FX Product Bulletin #10 ADIC will end support of Windows NT 4.0Jun 2005
-
StorNext FX Product Bulletin #9 StorNext versions 2.4.x and 2.5 have experienced miscounts of approved licenses when implemented with Xsan clientsMay 2005
Tape Products
-
Product Alert 59 Install the mandatory Scalar i6000 firmware update 798Q or higherJuly 2022