How to access disk information in Tech Support mode or Telnet, or get to a T3 support tech

Oh, and the other scheme I am thinking of trying since the USB SATA dock can apparently read the drives just fine is to find a "cloner" and clone the 2 supposedly-bad drives to new ones.  

---

mtmazzitello wrote:

I did find start_raid.sh over the weekend, when I type that in all it does is delays a second or so and then comes back with a # prompt and does nothing; no errors or returned messages or anything.  So I am guessing of that doesn't work then the other subsequent commands won't do anything or be of any use?  

I haven't needed to do this on my own NV+, but I wouldn't assume it is failing just because it is silent.  I'd expect that it would generate an error if it fails.

---

mtmazzitello wrote:

I got a suggestion from someone else to try these commands to see what errors the system thinks are occurring, but I am also wondering whether these will be useless if the RAID cannot be started.  I am going to try this tonight, along with your suggestions:  

# get_ata_errors /dev/hdc
# get_ata_errors /dev/hde
# get_ata_errors /dev/hdg
# get_ata_errors /dev/hdi

 

---

get_ata_errors should still work.  Whether that will give you useful information to troubleshoot is another question - not sure about that.

Here's what I got:  

# start_raid.sh
Killed

# get_ata_errors /dev/hdc
0
# get_ata_errors /dev/hde
0
# get_ata_errors /dev/hdg
246
# get_ata_errors /dev/hdi
0

I think I might be getting somewhere!  With the last set of commands, I made it to the last one, and I suspect it is maybe just a typo?  

root@000da2019d08:/# vgscan
Reading all physical volumes. This may take a while...
Found volume group "c" using metadata type lvm2
root@000da2019d08:/# vgchange -ay
1 logical volume(s) in volume group "c" now active
root@000da2019d08:/# mount -o ro /dev/c/c /c
mount: mount point /c does not exist
root@000da2019d08:/#

---

mtmazzitello wrote:

Oh, and the other scheme I am thinking of trying since the USB SATA dock can apparently read the drives just fine is to find a "cloner" and clone the 2 supposedly-bad drives to new ones.  

---

You can clone in windows, as long as you use a sector by sector copy mode.  Clonezilla can do it.

We have one of these in my company's IT department: 
https://www.startech.com/HDD/Duplicators/usb-3-esata-6-bay-hard-drive-duplicator-dock~SATDOCK5U3ER 

Unfortunately it does not seem to be able to do the clone, it gets stuck somewhere along the way and just stops processing.  No errors or indications of failure, just stops copying.  :-|   

I think I got lucky once with the NAS using PuTTY to get the raid started and mount the C volume, although I had some syntax error or something on that very last command, and not knowing what I am doing didn't help to troubleshoot it.  I have not been able to get the start_raid.sh command to succeed since then.  

Since my USB SATA dock on my Windows PC seems to be able to read at least the partitions and pass trhe SeaTools tests, I guess I'll try using that as the source location and doing a clone using my Windows PC.  
Boy this is getting tedious, but might be my last hope.  

No luck with cloning :-(  

Looking for any more help/guidance I can get for using the PuTTY connection & console to try to mount & access whatever volumes or parts of volumes I might be able to get at.  I think that's my last chance.  I am not well-versed in unix commands for volumes & file copies etc., I would need an interactive conversation/chat with someone who does.  I have been waiting over 4 days for a reply from my paid support incident with Netgear.