Black Hole
May contain traces of nut
So? If the HDD really isn't spinning up, what else are you going to blame? It seems to me there are only those two possibilities.True but how many faulty SATA interfaces have been reported on the HDR-FOX T2?
So? If the HDD really isn't spinning up, what else are you going to blame? It seems to me there are only those two possibilities.True but how many faulty SATA interfaces have been reported on the HDR-FOX T2?
I want to connect the two boxes particularly if the problem box has not recorded a programme because of it's faults but it has been recorded on the other box. I don't mind if this messes up the drive space calculations and I thought foxlink was the way to do it. So, just to be sure, are you saying foxlink is the way to link two boxes but ignore the drive space calculations?That might not be caused by a filesystem error. If you mount the folder '/mnt/hd2' from a second HDR-FOX as an NFS share or connect two HDR-FOX units with the foxlink package it messes up the onscreen drive space calculations in the way that you have described. The values return to normal when you put the second unit into standby. To avoid this don't use foxlink to link two HDR-FOX units, or mount the video folder of the remote unit only as '/media/My Video/' rather than mounting the entire '/mnt/hd2' folder.
I can't recall any reports of faulty SATA ports on an HDR-FOX T2 so I think it is far more likely to be the hard drive.So? If the HDD really isn't spinning up, what else are you going to blame? It seems to me there are only those two possibilities.
Did I suggest anything else?I can't recall any reports of faulty SATA ports on an HDR-FOX T2 so I think it is far more likely to be the hard drive.
You sat on the fenceDid I suggest anything else?
If the drive fails to spin up there is either a problem with the drive or a problem with the interface - impossible to tell which except by trial and error.
Once you have both boxes up and running, foxlink is an easy way of networking them. As stated above, recordings need to be decrypted for this to work. Although the drive space values presented on screen are affected this won't cause you any problems. The drive space totals in webif are unaffected and will be correct.MontysEvilTwin - You are correct. I did have foxlink installed and now I have uninstalled it disk capacities are shown correctly. Thank you for your time..
It will if you run out of space thinking you have some left.Although the drive space values presented on screen are affected this won't cause you any problems.
If you have two foxlinked units the available and used values are sums of those values from both units, the reserved size is a nonsense value and the drive size is correct for the unit in question. So you could think you have more space than you do have, and a recording may fail because of it but I doubt this would be a common occurrence, unless the disk were kept almost full most of the time. The drive space values are correct when the linked unit is in full standby and are always correct on webif so it is easy to keep an eye it.It will if you run out of space thinking you have some left.
Still no joy. One wrinkle is that the laptop is connected to the ethernet cable via a USB-C to RJ45 adapter. I'd think it eminently possible that is the fly in the ointment.Yes it's possible;
No you don't need a crossover cable;
If you are trying to do this in Windows you are onto a hiding. The easiest way is to find out the PC's settings (ipconfig on the command line) and match the HDR-FOX network settings to those (same subnet mask, different last byte of the IP address).