|
Breaking news:
As we could not cope with the Ossenstal pancake yesterday in Epe, we took it home in a doggybag.
Well not exactly a doggybag, the restaurant provided us with a quite luxurious box that looked a bit like a pizza delivery box.
We decided to warm it up in the airfryer, and to our surprise it tasted even better than the day before!
Nice and crispy, and we had some vanilla ice beside it 
|
|
|
|
|
Good to know  ... you made me curious, perhaps I will even drive once to Epe ...
|
|
|
|
|
If you like biking, you can find it near biking point 96.
A free biking planner that you can use is: Route.nl[^]
And an advice: don't order the full sized Ossenstal pancake, but only a half one
|
|
|
|
|
OK ... many thanks, I will keep it in mind
Checked at the source, the pancakes look delicious ...
|
|
|
|
|
From the website... "Al jaren is de Ossenstalpannenkoek een begrip in Nederland. [...] Erg machtig, wees gewaarschuwd!"
Never heard of them and I'm not driving over two hours just to check them out 
|
|
|
|
|
Had a look at the reviews on Google maps, and although most are very positive there were some negative reviews too.
A "local guide" said:
Quote: De specialiteit 'Ossenstalpannenkoek' is heel duur voor een bord mislukte oliebollen gruis
Quote: The specialty 'Ossenstal pancake' is very expensive for a plate of failed oliebollen grit
|
|
|
|
|
Knowing full well that if you continually beat on an ssd folder such as it can be when developing a software program and continually editing and compiling / running it that you can exceed the write count capability of your ssd device, I did it anyway cloning my spinner drive in my laptop to an ssd last October and beating the crap out of the project folder since.
Today I opened up vs to monkey around with a new feature and when I opened the view in question and put my cursor in a razor block and typed, instead of getting the if( I intended I got a vs crash dialog.
Experimenting, I found that if I tried to type anything in any razor block it would crash but I could edit the javascript and html without issue. Also if I opened a different mvc project and attempted to type in a razor block it would work.
The error was a CLR20r3 which seems is rather generic and affects many different packages according to googling the issue.
Not "getting" what was going on, I updated vs, I ran a malwarebytes scan 0 issues........
And was stumped. I have imaged the machine two days prior but hate bare metal restoring
over what might be trivial but what is it?
Then I thought, you don't suppose some blocks in the project folder have gone read only do ya?
So I copied the project folder to a new one, renamed the possible read only folder and the new copy to be what it should be, opened up the project and the problem was... gone!
So yeah, I leave this here on the internet as a breadcrumb for others.
Time to beat on some new blocks. 
And consider a fresh ssd. They're pretty cheap anymore.
modified 14-Aug-22 10:15am.
|
|
|
|
|
So was your SSD dead because of too many writes?
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
|
There aren't any fjords in Thailand, Korea, or China...
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Well, now we'll have to wait for a reaction like "what's this all about ?"
|
|
|
|
|
He said resting, not pining 
Paul Sanders.
If I had more time, I would have written a shorter letter - Blaise Pascal.
Some of my best work is in the undo buffer.
|
|
|
|
|
Or on strike.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
So - the Norwegian Blue SSD …
|
|
|
|
|
Ron Anders wrote: Then I thought, you don't suppose some blocks in the project folder have got read only do ya?
That's not how SSDs work. In order to prevent a single block being "pounded upon" too much (think of the FAT table), they use wear leveling. This means that a particular LBA doesn't map to a particular physical block.
Some physical blocks on the SSD are reserved as "spares", to handle the case of blocks that have gone read-only. This is handled transparently by the SSD's firmware. The SSD will typically go read-only only when all the spare blocks have been used.
Your description shows that this was not the case. I would look elsewhere for the cause of the error in VS.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
What Dan said. I have three laptops in front of me. They all have SSDs for many years. Thinking about it, the one I am typing on is almost 5 years old. The second one is nigh 9 years old (I'd have to do some historical research, but I tend to replace my equipment every 3-4 years). The last one is brand new, and I haven't had the time to stage all of the VMs I want to use.
I've never had an SSD failure. And these are dev laptops that grind through compile processing, etc. At first I was concerned about infant death of an SSD, but it's more likely you'll be in a car accident.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
Agreed.
I've had only 1 "set" of SSDs from Crucial screw me over. They had a firmware bug, and after X hours of being ON, they would start powering off!
BTW, we don't use Crucial SSDs anymore. We had 3 computers (laptops) with this issue. I Found it first.
Then another developer. The third developer was able to clone his drive and spare himself a lot of heart burn.
The Second Developer was stuck in a conundrum. The time the SSD would stay alive << the time required to clone!
Thankfully we have spare drives, clones, and backups. But it was REALLY hard to figure out at first. The machine would boot, then just crash with the drive going offline.
In general, I've tested an SSD on a TiVo for years. Wear leveling works.
And if your SSD is so old, it doesn't have wear leveling... Then you
A) Should have FAILED already!
B) Should have cloned it and upgraded about 2-3 years ago!
|
|
|
|
|
I've had only 1 "set" of SSDs from Crucial screw me over.
I can one-up that. I've only lost 1 ssd (mushkin), and I maintain it was not the ssd's fault. Stay with me. Back around 2017, after about 3 years of not changing any significant hardware, one day I get an IO error when trying to boot. Booted a live dvd and confirmed the disk was visible but simply refused to mount. So I shut it down and switch off the psu (normally I leave them plugged in but hardware switch off at the psu so it can stay grounded). I go to remove the ssd and I notice the hdd next to it was vibrating like it's still on. So I figure the rocker is dead/shorted and unplug the pc and take my chances with the static. It's still vibrating. Thinking I'm hearing things, I take a multimeter to the nearest open molex and find the 5v and 12v pins both read as 5v. So I start unplugging everything. Turns out it was my powered usb hub. Whenever the machine was off, the little 5V 2A wall wart was holding the whole system 12v line at 5v, apparently too low for any fans or cpu or any indicators of something being powered other than the half-speed hdd spinning. So the ssd was routinely subjected to a 12v and 5v rail pair that had no difference in voltage. Now I'm suprised the ssd was the only thing to break after 3 years. I still use the hub by the way, just with the usb cable between it and the pc modified to no longer connect the red wire.
|
|
|
|
|
Wow... That wins! Thanks for sharing...
FWIW, I am always concerned with device power issues.
And I cannot stand the new "feature" whereby my laptop powers the USB ports when it is off!
It just doesn't seem "right"...
|
|
|
|
|
100% with you there. My laptop has the ability to switch that off in bios. Too bad bios resets itself every time it is turned off and not connected to its power cable (replacing the cr2032 did not fix that). As for usb charging my phone, well that's half the reason I had a powered usb hub in the first place . Though now I mostly use the usb port on my ups.
|
|
|
|
|
It doesn't seem right because it's wrong. First rule of UI- never lie to the user. Ever.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
Thanks for adding the explanation I was thinking of writing. 
Software Zen: delete this;
|
|
|
|
|
Thanx for this clarity on SSD. My SSD quotes
"Global wear-leveling evens program/erase counts across data blocks to extend lifespan"
which is what I think you were referring to. Never saw this spec until you brought it up.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
I had one of my early USB memory sticks (not an SSD disk intended to replace a magnetic disk) more or less permanently sitting in the USB socket. This was in the days of Win XP, which wasn't very much aware of the special nature of Flash. I noticed that the LED on the stick lit up regularly (and quite frequently), but thought nothing of it until the stick started failing. I did a full formatting, ending up with a lot of bad pages, and used it for some more time, but soon more pages went bad.
That is when I first heard about wear leveling, and of the new Win 7 being "Flash aware", doing more extensive buffering to reduce the number of writes of OS data to the Flash device.
So: Once upon a time, Flash wear-out was a problem - probably more so on USB sticks. It might have been a problem even on SATA SSDs in their very earliest days, before wear leveling became standard. (That is a number of years ago!)
Note: Wear leveling is only applied to writing of pages that are being written/modified. Unmodified pages are not moved around to reduce wear. So it is no good idea to fill up your SSD to 99.9% of read-only files, and keep up heavy write/modify traffic on the last 0.1%. Keeping a fair share of the disc unused will spread the wear over more physical blocks, with less wear on a each of them. (This is of course of minimal concern if you do not make lots of writes to the remaining 0.1%!)
|
|
|
|
|
The fact that you can edit in other tools tells me the problem is with the VS project and not your SSD. The error you received also occurs on spinning rust drives, so it's not a drive error.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
