emusonacid! legacy

Just applied the 4.62 Firmware update to my EIV classic, and I now can't access any of the data that was on the internal SCSI drive. Immediately after the update, the sampler restarted itself, then hung for several minutes at the point where it was attempting to mount the SCSI drive. I power-cycled it, assuming it had crashed, after about 5 minutes of apparent inactivity, and now it boots. I'm able to see the drive when I hit the DISK button, but it appears now to contain no data. Fortunately, I hadn't got round to saving any of my own material on there, but there were a number of nice instrument sample banks in there before. Is there any way of retrieving these, at this point, or do I have to reformat the drive to use it, now? The sampler appears to think it's now unformatted, or at least in an unknown format. I was previously running firmware version 4.10b, if this is relevant.

Cheers,

a|x

Anyone?

Hard to say...

If the HD is not recognized as EOSFAT-drive then I would try to restore the drive with a trick. This only works if the boot-block is damaged.
1. Make two backups of the drive with DisK2File to your PC.
- The first backup should just contain sector 0.
- The second backup-file should start at sector 1 and contain the rest of the HD. Note down the total amount of sectors.
2. Format the drive with EOSFAT again.
3. Transfer the second backup back to the SCSI-HD, starting at sector 1.

Hi mosrob,

thanks for the tips. Unfortunately, I don't have a PC (I'm a Mac user), and haven't owned a computer with a SCSI interface for more than 10 years. I will ask around at work and see if we still have a PC with a SCSI card of some kind.

Cheers,

a|x

In the beginning when the E4 classic line came out, I had an issue with my e64 after connecting it to my Win98-PC.
Windows wrote some kind of timestamp to the first sector of the SCSI-HD and EOS could not read/identify the HD because the checksum of the first sector was incorrect. After reporting this issue to E-mu Systems, they fixed it with the next EOS-update.
If you have a similar issue with a corrupted sector 0, then my recommended procedure might fix the issue.

Maybe there is also an application for MacOS for making a sector-wise backup of the SCSI-HD.
I recommend making a backup of sector 0 seperately and another backup of the rest of the SCSI-HD.
Then format the SCSI-HD to restore the filesystem.