Framework Development Blocker

  • Ganossa
  • Topic Author
More
8 years 10 months ago #1 by Ganossa Development Blocker was created by Ganossa
I actually wanted to give an update on the development this week but did not expect it to be like this.

Unfortunately, yesterday I lost my two SSDs to their afterlife...

Please Log in or Create an account to join the conversation.

  • jas01
More
8 years 10 months ago #2 by jas01 Replied by jas01 on topic Development Blocker

LuciferHawk wrote: I actually wanted to give an update on the development this week but did not expect it to be like this.

Unfortunately, yesterday I lost my two SSDs to their afterlife...


That's sad. :( We can wait. ;)

Please Log in or Create an account to join the conversation.

  • SpinelessJelly
More
8 years 10 months ago #3 by SpinelessJelly Replied by SpinelessJelly on topic Development Blocker
Sorry to hear that, LH. But both, at the same time? Isn't that strange? Could it be a controller/MB issue?

Please Log in or Create an account to join the conversation.

  • Kleio420
More
8 years 10 months ago #4 by Kleio420 Replied by Kleio420 on topic Development Blocker

SpinelessJelly wrote: Sorry to hear that, LH. But both, at the same time? Isn't that strange? Could it be a controller/MB issue?

he could have them in raid if so that makes complete sense

Please Log in or Create an account to join the conversation.

  • Ganossa
  • Topic Author
More
8 years 10 months ago - 8 years 10 months ago #5 by Ganossa Replied by Ganossa on topic Development Blocker
They are not in raid but they have been both on windows 7's defragmentation schedule (though that should usually be disabled!!!!) reading seems fine still but writing crashes or diables the disks regulary now. I try to backup the system partition and try if formating helps.

Even on my win8.1 partition I see now that one of the SSDs is in the defragmentation loop ...wtf Microsoft :blink:
Last edit: 8 years 10 months ago by Ganossa.

Please Log in or Create an account to join the conversation.

  • Martigen
More
8 years 10 months ago #6 by Martigen Replied by Martigen on topic Development Blocker

LuciferHawk wrote: They are not in raid but they have been both on windows 7's defragmentation schedule (though that should usually be disabled!!!!) reading seems fine still but writing crashes or diables the disks regulary now. I try to backup the system partition and try if formating helps.

Even on my win8.1 partition I see now that one of the SSDs is in the defragmentation loop ...wtf Microsoft :blink:

I had this problem when updating from Windows 8 to Windows 8.1, and it was defragging my SSDs for an hour before I noticed... (the fuck microsoft!)

So, two things to do:
  • Install latest Intel drivers (presuming you're using on-board Intel controller for disk). I think my Win 8.1 install defaulted to the MS drivers, so this restored control via intel drivers, which you'd hope could properly identify disks.
  • Open a command prompt with Admin privs and run: winsat prepop

Not sure which one of these fixed it for me, but Win 8.1 saw them as SSDs after the above. The Windows Experience index was 'removed' from Win 8.1, as MS didn't like its Surface tablets performing so shabbily with its results, but it's still actually installed on Win 8.1 (the 'winsat' command above). Importantly, previous versions of Windows used the results from Winsat to determine if a drive is an SSD or HDD, and set certain features accordingly (like disabling defrag).

Also, it is definitely odd to 'lose' two at once and I'd say before you throw them out to give them both a secure erase, restoring them to factory default (minus whatever lifespan has been used already). Then re-install Windows. Bit of a pain, but you'll know for sure if the drives are ok this way. It will also restore some performance to you. Don't know if you're familiar with secure erase but there are different ways of doing this: a Linux boot disk can do it for eg, or in some cases the SSD vendor will have a tool to do it for you (Samsung includes this in their toolbox for eg, though you obviously can't boot from the drive you're going to erase... a WinPE may help here)
The following user(s) said Thank You: Ganossa, Aelius Maximus

Please Log in or Create an account to join the conversation.

  • Ganossa
  • Topic Author
More
8 years 10 months ago #7 by Ganossa Replied by Ganossa on topic Development Blocker
The SSDs are okay but the file system is/was corrupted. Spend yesterday and today with recovery and now fresh installation but about 10.000$ licenced dev software (including photoshop) is currently gone

Please Log in or Create an account to join the conversation.

  • BrandonHortman
More
8 years 10 months ago #8 by BrandonHortman Replied by BrandonHortman on topic Development Blocker
I'm sorry to hear that. Sounds like a nightmare.

Please Log in or Create an account to join the conversation.

  • Ganossa
  • Topic Author
More
8 years 10 months ago #9 by Ganossa Replied by Ganossa on topic Development Blocker
Well, Photoshop seems lost but VS13 Ultimate I could reactivate (which is the most expensive one) and with a fresh installation development can continue ;)

Therefore, here the promised progress shot:

re-ordering concept working in the mediator
The following user(s) said Thank You: BillyAlt, jas01, Aelius Maximus

Please Log in or Create an account to join the conversation.

  • aufkrawall
More
8 years 10 months ago #10 by aufkrawall Replied by aufkrawall on topic Development Blocker
Sorry to hear your trouble.
In modern bios/UEFI, one can define if a drive is a SSD or HDD. Did you check this? Then Windows Defragmenter should detect the device as a SSD and refuse to defragment it (at least that's what I conclude from my observations).

Please Log in or Create an account to join the conversation.

  • sajittarius
More
8 years 10 months ago #11 by sajittarius Replied by sajittarius on topic Development Blocker
man that sucks :(

at least you got your Visual Studio back. Since you are still using the drives, you should check if TRIM is enabled (automatic marking of bad sectors, pretty important for SSD), since it seemed like windows wasn't detecting the SSD right.. There is a command you can run in command prompt.

I used to have a link with the command, i can dig it up if you need it. Actually here is one: lifehacker.com/5640971/check-if-trim-is-...e-drive-in-windows-7

Please Log in or Create an account to join the conversation.

We use cookies
We use cookies on our website. Some of them are essential for the operation of the forum. You can decide for yourself whether you want to allow cookies or not. Please note that if you reject them, you may not be able to use all the functionalities of the site.