ISCI connected but drive is not accessible the volume repair was not successful

iSCSI related applications
Post Reply
Robivee
New here
Posts: 3
Joined: Mon Dec 28, 2015 5:02 am

ISCI connected but drive is not accessible the volume repair was not successful

Post by Robivee »

I had a dual power supply failure on my legacy TS-859u+ unit. I was using ISCSI connected to a Server to hold my archival projects. RAID 6 Configuration with 6.24 TB in use and 4.2 TB free. I have spare parts from two other TS-859u+ units and was able to insert (2) working power supplies. The unit comes online recognizes all the information. I can get into the QNAP via gui interface. The ISCI Initiator sees the Qnap and connects to the LUN. Correct name target IP ADDRESS. Server Computer Management sees the drive brings it up online and states that its healthy. But when I attempt to access it, it states the drive is not accessible. The volume repair was not successful.
Looking for guidance direction help....Is there a way to access the data via putty on the back end and slowly move it off?
User avatar
OneCD
Guru
Posts: 12790
Joined: Sun Aug 21, 2016 10:48 am
Location: "... there, behind that sofa!"

Re: ISCI connected but drive is not accessible the volume repair was not successful

Post by OneCD »

Robivee wrote: Fri Jun 21, 2024 9:30 pm Server Computer Management sees the drive brings it up online and states that its healthy. But when I attempt to access it, it states the drive is not accessible. The volume repair was not successful.
Not-good. It appears everything is OK on the QNAP side, and the initiator confirms the virtual drive is OK, but the filesystem (volume) contained within your LUN is corrupt. :(
Robivee wrote: Fri Jun 21, 2024 9:30 pm Looking for guidance direction help....Is there a way to access the data via putty on the back end and slowly move it off?
No, can't be done. You're limited to the abilities of the initiator OS (I think you're using Windows). On the QNAP-end, your NAS knows absolutely nothing about the virtual drive format and filesystem(s) inside the LUN. Even if you initiate a loopback connection within the NAS, you'd be in the same position you're in now: dealing with the same corrupted virtual filesystem.

This is something only the initiator can fix. If it can't repair the virtual filesystem contained inside the LUN, then you'll need to restore the entire LUN from your iSCSI backups, or else reformat the LUN (via the initiator) and restore your data files from backup the hard-way.

ImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImage
Post Reply

Return to “iSCSI – Target & Virtual Disk”