BOFH
15th Mar 2008, 00:12
It's humiliating to have to ask, but a problem shared is a problem doubled.
My venerable filesewer has snuffed it. I've tried it with both CPUs (it's a VP6), memory modules swapped in and out, checked for blown caps, you name it. It has a SCSI card but that was swapped out (i.e., chucked on the floor), so a goat sacrifice is not required.
This was a Windows machine running XP Pro with a few partitions running from a 300 on the IDE side and two 160s set up as JBOD on the Highpoint circuits. The 300 is fine, and I can mount it.
The 160s will not mount (in a USB enclosure)l. They were not set to stripe (in which case I'd expect to be stuffed), but in JBOD, wouldn't they have kept each file on each discrete disk?
Were this the case, which software can I use to grab the data? I can remember one from years ago which would trawl through and reveal the start and endpoints of files on a Windows system, but I have disremembered it. ISTR that they were NTFS.
I am grateful for any suggestions.
BOFH
My venerable filesewer has snuffed it. I've tried it with both CPUs (it's a VP6), memory modules swapped in and out, checked for blown caps, you name it. It has a SCSI card but that was swapped out (i.e., chucked on the floor), so a goat sacrifice is not required.
This was a Windows machine running XP Pro with a few partitions running from a 300 on the IDE side and two 160s set up as JBOD on the Highpoint circuits. The 300 is fine, and I can mount it.
The 160s will not mount (in a USB enclosure)l. They were not set to stripe (in which case I'd expect to be stuffed), but in JBOD, wouldn't they have kept each file on each discrete disk?
Were this the case, which software can I use to grab the data? I can remember one from years ago which would trawl through and reveal the start and endpoints of files on a Windows system, but I have disremembered it. ISTR that they were NTFS.
I am grateful for any suggestions.
BOFH