[ Hypnos Forum ]

MUSIC, AMBIENCE AND SOUND ART => Music Gearheads Tech Talk => Topic started by: APK on June 11, 2018, 05:44:03 PM

Title: C: Drive crash
Post by: APK on June 11, 2018, 05:44:03 PM
Recently had my music recording computer boot drive crash (Windows).
Very depressing. Had not backed up for quite some time.
Had all recent recordings / projects on it.

A reminder to BACK things up.
Clone your drives.

 :(
Title: Re: C: Drive crash
Post by: stargazer on June 11, 2018, 09:38:49 PM
I am so very sorry for you. This is the badest thing could happen.
Especially the lost of recordings for works in process and upcoming releases!

I mostly backup every project right in time.
Also I have several testrecordings on different computers in the house.

Try SSD Anthony.
Title: Re: C: Drive crash
Post by: Seren on June 12, 2018, 12:39:56 AM
Ouch, sorry to hear that.
Is there no way to get the stuff back?
Given the technology  - can't you take the disks out and take them somewhere?
Title: Re: C: Drive crash
Post by: petekelly on June 12, 2018, 01:57:39 AM
Yes, that sounds pretty grim.

I backup every week and have had no issues with using SSDs.  As Seren said, is there any way to try to recover your lost data ?
Title: Re: C: Drive crash
Post by: Julio Di Benedetto on June 12, 2018, 04:15:03 AM
Ouch.....sorry to hear that.

I use carbon copy cloning software on my Mac and have a 1T Glyph Drive just for backups. Actually I have only used Glyph Drives...https://www.glyphtech.com (https://www.glyphtech.com)...because Glyph are able to recover all data from their corrupted hard drives if you send them in.  Only used this service one time and it was just a firmware issue and not a drive failure.

Hope you can get the data off the drive.  There are some amazing computer Wizards out there that seem to be able to fix anything or remove spells if need be.
Title: Re: C: Drive crash
Post by: APK on June 12, 2018, 08:13:31 AM
Sad thing is that the drive is no longer registering in the BIOS. SO computer does not see it.
It spins, but no reading. So can't run a rescue program on it.
It has been in a repair shop to see if they can clone it using a hardware cloner. No luck.

I will get it back today and try a different route. I have an identical drive and will remove the controller board on the good drive and put it on the bad one. Might work ... could just as easily be an electronic component problem as a mechanical one.

Last option is to seal it in a bag and put it in the freezer for a couple of hours, then try it. This has been known to work.

Yes, should have a more reliable SSD instead of the old style drive. My other three computers are all SSD.
Stupid really because the music computer is by far the most important one.

Problem is that when you put in a new drive you have to re-register/licence so much of the music software. And I use a lot of VST plugins. So I was being lazy.   :-\
Title: Re: C: Drive crash
Post by: stargazer on June 12, 2018, 11:02:02 AM
Have you already tried an external harddisc adapter?

We already fixed a similiar problem where the repair shop said the disc was physically damaged.
Title: Re: C: Drive crash
Post by: chris23 on June 12, 2018, 02:17:49 PM
I'm sorry to hear that, Anthony. I hope something works out.

Just out of curiosity: What do most musicians do to manage downloads, plugins, and licenses? Are most of them easily transferable across machines? Or do some of them breakdown across OS updates and create a huge pain?
Title: Re: C: Drive crash
Post by: APK on June 12, 2018, 05:57:52 PM
Jana ... yes, first thing I tried.

Swapping the controller board from a good drive to the bad one was promising, the disk shows up, but still not readable ... still not sure if it will save me paying a $1000 to a data recovery company though. They will take the platters (disks) out of the old drive and put them in a blank one, in a dust free environment, and try to copy the drive using the good read head.

Chris ::  I'd say they are transferable across machines, but you do have to cancel them on one and register them on the other. I don't find them much of a pain, generally. But it is a LOT of software. Much of the software is from smaller companies, or individuals, who are there to help make things easy.
Title: Re: C: Drive crash
Post by: Julio Di Benedetto on June 13, 2018, 04:01:02 AM

Just out of curiosity: What do most musicians do to manage downloads, plugins, and licenses? Are most of them easily transferable across machines? Or do some of them breakdown across OS updates and create a huge pain?


Regarding software audio plugins and their licenses it is handled by iLok which is basically a small usb drive that holds the encrypted licenses.  You will hear lots of people complain about this system and its inconveniences but it has work well for me over the years.  I don't have a vast amount of plugins, just a choice selection of EQ's compressors and FX for recording.

I have an IT co-worker that has every plugin under the sun for Pro Tools and he had to upgrade / cross grade his OS and drives and said it took a good week to complete, though he had 100's of gigs of samples as well to port over....nearly drove him mad and computers are his occupation.   So yeah Chris it can be a huge pain.

Anyone using a Cloud for backups?
Title: Re: C: Drive crash
Post by: petekelly on June 13, 2018, 09:30:23 AM
I'm sorry to hear that, Anthony. I hope something works out.

Just out of curiosity: What do most musicians do to manage downloads, plugins, and licenses? Are most of them easily transferable across machines? Or do some of them breakdown across OS updates and create a huge pain?


Yeah, sample libraries are the most time consuming. Whenver I re-install windows or get a new PC, I install some 'core' programs (FL Studio / various NI stuff / Valhalla verbs etc.) and it's usually not too bad. The thing that really takes time is tweaking the system to get rid of the bloatware /crap 'features' that comes with (in my case) windows 10 !
Title: Re: C: Drive crash
Post by: APK on June 19, 2018, 02:08:03 PM
Update on that almost dead drive.

It is now off at a hard disk recovery place over here. Hopefully with useful results.
Will be expensive, but it was that or stop doing music altogether and maybe take up
another hobby (trout fishing, bitcoin mining ...) that I would not like half as much.  >:(
It was not only months of lost recordings, but also a lot of presets I have made for my
favorite soft synths and effects that would be lost.

Again ... clone that boot drive, regularly !  Don't just back things up.
Title: Re: C: Drive crash
Post by: APK on June 19, 2018, 02:17:31 PM
Meanwhile, this has been a good opportunity to play with hardware synths more than usual ...
especially sitting out in the sun with headphones on.

I am enamored by my little Roland System 1m (been on all my recent recordings, in small interesting ways).
Fed by the Arturia Keystep ... so very portable, yet capable.
Also enjoying the Korg Electribe 2.
Title: Re: C: Drive crash
Post by: APK on June 27, 2018, 10:31:41 AM
Crashed drive was recovered and cloned. Just got it back.
Files are readable -- possibly all of them.  8)
Right now copying all my music project files to SSD. Going well.
The drive might also be bootable, but Windows does report some errors on it.
Will copy first, run a check disk program later.
But positive results so far.
Title: Re: C: Drive crash
Post by: stargazer on June 27, 2018, 01:21:16 PM
Great to hear this, Anthony! Wow that is luck.
Now I am looking forward to your coming albums now.

:)
Title: Re: C: Drive crash
Post by: phobos on June 28, 2018, 12:09:21 AM
 8)
Title: Re: C: Drive crash
Post by: Julio Di Benedetto on June 28, 2018, 04:47:06 AM
I can hear the exhale......happy for you and the music.
Title: Re: C: Drive crash
Post by: chris23 on June 28, 2018, 07:59:34 AM
 :) :)
Title: Re: C: Drive crash
Post by: petekelly on June 28, 2018, 12:37:28 PM
Good news !
Just wondering if a dead SSD could be recovered ? From what I've read, if they die, then that's pretty much everything gone (?) Whereas your HD (even if it didn't boot), could still be recovered.
Title: Re: C: Drive crash
Post by: APK on June 28, 2018, 04:19:03 PM
It boots !!!!!!!!!   ;D

Things work !!!!!!
Title: Re: C: Drive crash
Post by: APK on June 28, 2018, 04:19:42 PM
I'm putting away the basket weaving kit, and back into music !  8)

Thanks for all the comments.  :)
Title: Re: C: Drive crash
Post by: APK on June 28, 2018, 04:28:56 PM
Pete.

SSD can be recovered, depending on the problem.
Same with memory sticks.
What you have probably heard is that a SSD has a set number of read/write cycles before it dies.
That is in fact true. But it is one hell of a lot of read/writes. 20 years or much more in normal use.
Which is why you do not de-fragment Solid State Drives ... you gain little in efficiency, but lose a lot of cycles.

But a SSD still has controller chips and other electronics that can act up, or go bad. And important index information that can get messed up, as with a hard disk. The hard disk rescue places will also work on solid state drives.
Title: Re: C: Drive crash
Post by: petekelly on June 29, 2018, 05:36:52 AM
APK,

Cheers, not quite as simple as I thought. I have to say, it's the mechanical element to the HD that concerns me more than anything.

Pete.

SSD can be recovered, depending on the problem.
Same with memory sticks.
What you have probably heard is that a SSD has a set number of read/write cycles before it dies.
That is in fact true. But it is one hell of a lot of read/writes. 20 years or much more in normal use.
Which is why you do not de-fragment Solid State Drives ... you gain little in efficiency, but lose a lot of cycles.

But a SSD still has controller chips and other electronics that can act up, or go bad. And important index information that can get messed up, as with a hard disk. The hard disk rescue places will also work on solid state drives.
Title: Re: C: Drive crash
Post by: Julio Di Benedetto on July 07, 2018, 05:56:26 AM
My main storage drive failed yesterday.  It had been misbehaving for a bit by not being seen by my computer.  Would require me to manually switch it off and on again for the drive to show up on my desktop.  Back it goes to the manufacture for repairs and recovery if need be.

The drive was backed up though I may have lost yesterdays recordings as I did not save those before the drive failed.

What Ive been doing for a few years now is creating versions of a track as it progresses....so version 1, version 2, 3 etc, and I will create a version when I feel a fair amount of development with the music has occurred. On average about 6 to 8 versions of the track, 8 being the completed piece of music.  The main reason for this is because Logic X is known to create corrupted files that will not load up so the music arrangement is gone.  If the latest version of the track is corrupted then I can go back to the previous version and start from there again.  If there was just one arrangement of the track the only way to restore the track would be rebuild it from scratch with the original audio files...a bit of a pain because Ive done it.

As far as the failed drive is concerned....the last backed up version of the current piece of music Im working on is version 4,  yesterdays was at version 6, so if the drive was never to be restored again I can continue from V4.  Even if your Daw is solid this method of working can be a really blessing.  Its also interesting to go back through the different versions of a track a see / hear its evolution. 
Title: Re: C: Drive crash
Post by: Julio Di Benedetto on August 10, 2018, 04:09:30 AM
Thought I would post the email from Glyph Tech support that has a list of suggestions for a health drive.

I found your internal disk to be mildly corrupted and at 99% health.
The corruption was keeping it from mounting. Here are a few things you can do to prevent data corruption.

-Take the drive out of spotlight so it's not being indexed constantly.
- Run First Aid after sessions.
-Run Disk Warrior more frequently, like once a week.
-don't let the computer fall asleep with the drive attached
-Properly eject the drive every time, waiting 10 seconds after the ejection to let the computer close the disk out.
-Keep more backups! This is super important, as I'm sure you know.
Your data is intact an I am replacing the disk.