denywinarto

Okay, i'm not expecting a fix in 3 days or something like that, Just a word acknowledging this issue and a confirmation of future version with fix would be nice. In my opinion this should be regarded as critical issue because its affecting OS stability. About storage spaces, Well, I need 12tb with ssd-like read speed, with the current price of SSD i can't find any other alternative which offers similar performance to size ratio, and i'd rather stick with what i have now. Maybe once SSD price goes down i'll reconsider it. I plan to make OS backup and run scanner and turn the scanner off for the storage spaces drives. If anything goes wrong i can just revert to the backup, but hopefully i wont need to do that.

Did you read my post about the chronological order of BSOD? windows server 2019 + corrupted Storage spaces MBR= no BSOD, windows simply gives warning "this drive needs to be scanned blablabla" windows server 2019 + corrupted Storage spaces MBR + stablebit scanner running = BSOD, right after inserting license code and scanner starts running. As you can see on the reliability pic on my last post. The fix is for scanner is quite simple, the trigger is bad MBR sector from Storage spaces harddisk, so simply prevent it from scanning once it detects corrupted SS drive. I know this is stablebit forum, but without customer critics a product won't get any better. the 3 drives are now fine in SS after chkdsk, without stablebit scanner of course.

3 days and not a single response? Not even my ticket gets responded Scanner is an abandoned product then, Anyone know a decent alternative?

Update : thankfully CHKDSK saves the day. it says the MBR was corrupted but it was able to repair it So now i can probably use my storage spaces again But should i use scanner or not now? Any words from Chris / Alex or the devs? Can't risk another BSOD

Well got another case now with stablebit scanner. This time its worse, its 3x4 tb wd black in storage spaces. It became RAW after BSOD I'm pretty sure its scanner cause as soon as it starts scanning after installation BSOD occurs. And the reliability windows page back this up. (I installed scanner on 6.36 and input the serial about half an hour later.) Its not drivepool cause the drives arent in the pool. This is on newly installed Server 2019, i just reinstalled it yesterday I immediately uninstall scanner. What should i do now? I need scanner to warn me of bad drives so i can replace them before they go bad. But i have 2 dozens of drives if a single bad drive + scanner = BSOD then that means 2 dozens reliability holes. Edit : I should have add, The reason i reinstalled my machine was because i'm having multiple BSOD's everyday. Now i suspect my recent midnight BSOD's were caused by scanner scanning at midnight. 1. A new installation BSOD'ed right after i install scanner and it's scaning 2. The BSOD always happens at midnight, i check task scheduler and nothing is run at midnight. Seeing scanner's description of "always scans at midnight" reminds me of this. While i know the bad drives are the fault, i think scanner could do a better job preventing windows BSOD trigger

You dont need to disable any service if that's what you mean

1. Manually move all files to the outside of the poolpart.xxx folder on the bad disk so that drivepool can't see them any more. 2. Remove the old disk from DrivePool (it will be instantly complete since the poolpart folder is empty). 3. Insert new disk (new different PoolPart.xxx is created). 4. Manually copy the files from the old disk to the new poolpart folder on the new disk. I found out by doing this i didn't get BSOD compared to moving the disk using DP Above is why i think the BSOD is related to drivepool, what i'm worried about if one my drives go bad then it would just throw random BSOD and screw up my OS

So you're saying its more like OS issue? Hmm i'm using server 2019 and LSI 9300 8e.. Any possible workaround that is recommended? I mean eventually all my drives are gonna go bad someday, just wondering if there's a way to prevent it from screwing up my OS installation

About 2 days ago i instaled 1tb hdd which i thought was still in good condition because HDD sentinel and stablebit scanner didnt report anything strange. Last night i think my server got rebooted couple of times and some drivers got corrupted. Thankfully i made daily backup, so i restored it. But then just few hours ago it rebooted again, and that 1tb HDD became "RAW" and offline. I also remember when moving bad drive from the pool last year i got BSOD once or twice. So Is this a known issue? I'm using the latest build.

Any links for this? Have you seen people achieve it? I could make windows detect them both in device manager, by still enabling the svga, but running gpu-z gives me svga as the detected gpu. I'm also using the igpu for blueiris so im forced to use windows

Yeah, strangely the machine script says my lsi-9300 8e cant be passthrough'ed So I tested with esxi as well. It worked but there is one issue that makes the setup not ideal, to passthrough the igpu, i have to disable svga, thus i lose console display and i have to rely on rdesktop alone. Not ideal for 24/ server IMO Are you by any chance also pasthru your gpu / igpu?

Ah i thought you were using hyper-v lol.. Thanks for the license tips will keep that in mind. I'm leaning towards hyper-v cause most of my environment is windows based..

Thanks chris, how long have you been doing it? Is it stable enough? Also there is something i forgot to ask, were you able to passhthrough the igpu as well? I will need it for emby and blue iris i think

Hi Philmatic, sorry for bumping an old thread, I thought controller passthrough is possible already on server 2019? https://www.reddit.com/r/HyperV/comments/bc3vvc/pcie_passthrough_possible_with_a_hba/ Have you tried it? If it does passthrough the SMART status as well then it's probably the better method

Anyone ? Chris? Have you seen this implemented without issue?