According to the log the problem occured since December when the server crashed a restarted,
72504 12/26/2014 04:08:14 PM 2 0 0 4152330944 15992 0 nwsrv1 nsrd rd=sidi-rezig-sn2:/stagingDisks/disk04/_AF_readonly mount operation failed: cannot open /stagingDisks/disk04/_AF_readonly/volhdr file: No such file or directory
72504 12/27/2014 12:04:46 AM 2 0 0 4152330944 15992 0 nwsrv1 nsrd rd=sidi-rezig-sn2:/stagingDisks/disk04/_AF_readonly Recover space operation failed: nsr server 'nwsrv1' cannot request from mmd 28
72504 12/27/2014 08:04:46 AM 2 0 0 4152330944 15992 0 nwsrv1 nsrd rd=sidi-rezig-sn2:/stagingDisks/disk05/_AF_readonly Recover space operation failed: nsr server 'nwsrv1' cannot request from mmd 46
38752 12/28/2014 01:02:25 AM 2 0 0 4152330944 15992 0 nwsrv1 nsrd rd=sidi-rezig-sn2:/stagingDisks/disk05 Verify label operation in progress
38752 12/28/2014 01:02:26 AM 2 0 0 4152330944 15992 0 nwsrv1 nsrd rd=sidi-rezig-sn2:/stagingDisks/disk05 Label operation in progress
72504 12/28/2014 01:02:57 AM 2 0 0 4152330944 15992 0 nwsrv1 nsrd rd=sidi-rezig-sn2:/stagingDisks/disk05 label operation failed: adv_file disk nwsrv1.orascomtunisie.com.035.RO is currently mounted, unmount it first
Is there something to remove or clean in NetWorker indexes database or should I remove the LUNs totally or should I run the labeling of command from the Storage nodes?
Don't you have any valid backup data on the AFTD ? because if you label it again all that data will be lost. If you are tryingto get the AFTD back with the relevant inforamtion just re-create the device and mount the AFTD.
Assuming that you know that you are doing the issue here is that the RO part of the AFTD is still mounted and thus is not allowing you to label the data again. First fo to devices -> View -> select "Display Read only Devices and Volumes". Once done you will be able to see the AFTD and its respective .RO device in the device list. Right click on the RO device and unmount it and retry the label operation.
bingo.1
2.4K Posts
0
February 6th, 2015 06:00
The screenshots are talking a straight story - you must change the device properties as follows:
Device Properties > General tab > Status area: Uncheck 'Read only'
Most likely you must unmount the volume first.
CAREFUL: Lbaleing will overwrite your media deleting all data!
Sorry, but you are mixing terms which does make it hard to understand the rest.
Hope it's not relevant.
SLIMGRIRI
2 Posts
0
February 9th, 2015 02:00
Hi,
Actually the 'read only' were never checked.
According to the log the problem occured since December when the server crashed a restarted,
72504 12/26/2014 04:08:14 PM 2 0 0 4152330944 15992 0 nwsrv1 nsrd rd=sidi-rezig-sn2:/stagingDisks/disk04/_AF_readonly mount operation failed: cannot open /stagingDisks/disk04/_AF_readonly/volhdr file: No such file or directory
72504 12/27/2014 12:04:46 AM 2 0 0 4152330944 15992 0 nwsrv1 nsrd rd=sidi-rezig-sn2:/stagingDisks/disk04/_AF_readonly Recover space operation failed: nsr server 'nwsrv1' cannot request from mmd 28
72504 12/27/2014 08:04:46 AM 2 0 0 4152330944 15992 0 nwsrv1 nsrd rd=sidi-rezig-sn2:/stagingDisks/disk05/_AF_readonly Recover space operation failed: nsr server 'nwsrv1' cannot request from mmd 46
38752 12/28/2014 01:02:25 AM 2 0 0 4152330944 15992 0 nwsrv1 nsrd rd=sidi-rezig-sn2:/stagingDisks/disk05 Verify label operation in progress
38752 12/28/2014 01:02:26 AM 2 0 0 4152330944 15992 0 nwsrv1 nsrd rd=sidi-rezig-sn2:/stagingDisks/disk05 Label operation in progress
72504 12/28/2014 01:02:57 AM 2 0 0 4152330944 15992 0 nwsrv1 nsrd rd=sidi-rezig-sn2:/stagingDisks/disk05 label operation failed: adv_file disk nwsrv1.orascomtunisie.com.035.RO is currently mounted, unmount it first
Is there something to remove or clean in NetWorker indexes database or should I remove the LUNs totally or should I run the labeling of command from the Storage nodes?
crazyrov
4 Operator
•
1.3K Posts
0
February 9th, 2015 03:00
Don't you have any valid backup data on the AFTD ? because if you label it again all that data will be lost. If you are tryingto get the AFTD back with the relevant inforamtion just re-create the device and mount the AFTD.
Assuming that you know that you are doing the issue here is that the RO part of the AFTD is still mounted and thus is not allowing you to label the data again. First fo to devices -> View -> select "Display Read only Devices and Volumes". Once done you will be able to see the AFTD and its respective .RO device in the device list. Right click on the RO device and unmount it and retry the label operation.