is it safe and reliable to make a complete long full scan on the SSD when it is OS running ?

[amiens80]

hi,

i want to make a full scan of my SSD samsung 870EVO 2TB but it takes time and my SSD is where my OS is (windows).
Can i run this long scan even when my os is running ? even when i still browsing/downloading/music (but i not playing at all).

Thank you for your advice.

Best regards & fun to you !

 

[GerKNG]

does it say anywhere that you should not?

 

[bonehead123]

Been there, done that, many times, with various apps, including the sammy one.... nottaproblemo.... HOWEVER, it is ALWAYS a good idea to create a backup of everything on the drive first, on the odd chance (rare IMHO) that anything goes foofoo

 

[amiens80]

i'm wondering how 'magical' it is to test a cell while the windows swapfile is on it in exclusive-write! Even a defrag too cannot perform such thing , so how can it be possible that this samsung software can perform that !? liar or uncomplete full-test ?

 

[Shrek]

Looks like it only needs to read

 

[SPDIF]

Why would you do it in first place when it's working good??? Only when you see errors in Smart i would do it. Now it's not needed and does nothing to know anything.

Don't seek problems where there are not... It's write an reading for very long time, so it also cause unnecessary wear on your SSD.

 

[amiens80]

well, i started the full scan.
it will be very long.
in the documentation, it said there will be a button 'RECOVERY' after. Do you know it i will can have it tomorrow when i will select the log, or is it only appear after a scan ?

i'm wondering why Samsung write "1-3 hour for 1TB" .... i have a 2TB drove, and 1TB already took 1hour, so it will take 2hour for 2TB.

Why should have it take 3hour for 1TB ? other ssd than my 870EVO ? older model are so slow than mine ?

 

[csendesmark]

If it is a read test, you should be safe.
But I would recommend to check it when you boot the system from some sort of USB based system, like clonezilla

If a sector is proven to be bad, might take longer time to check it.
It might try to check it multiple times before flagging it bad.
I have no direct experience with SSD, but running the good old badblocks on HDDs using linux was slow when the drive had issues.
Perfect drives with the simple read test, basically completed as you expected (like 1000GB drives in about 2.5 hours).

 

[Steevo]

i'm wondering how 'magical' it is to test a cell while the windows swapfile is on it in exclusive-write! Even a defrag too cannot perform such thing , so how can it be possible that this samsung software can perform that !? liar or uncomplete full-test ?

I’m sure if it’s interfacing with the controller it can tell the controller to move blocks without the OS knowing a remap occurred

 

[MarsM4N]

The Samsung Magician Diagnostics Scan is software based, so there is no other option than to run it within Windows. And no, it doesn't harm anything. If it finds errors it will repair them.

You can also run the Windows CHKDSK command tool which will be performed after a reboot. Windows will be unusable (if performed on the OS partition) for the time but on a SSD it's pretty fast.

 

[amiens80]

The Samsung Magician Diagnostics Scan is software based, so there is no other option than to run it within Windows. And no, it doesn't harm anything. If it finds errors it will repair them.

You can also run the Windows CHKDSK command tool which will be performed after a reboot. Windows will be unusable (if performed on the OS partition) for the time but on a SSD it's pretty fast.

"If it finds errors it will repair them"
not at all. it found error but it did not repair them. after the test, i had the button "recovery" but it dit not work. Recovery stopped once i clicked it.


After the full scan, i see 3 red box :

"magicien has found an error on the drive , it is recommanded to recover "

what does it mean ? 3 files ? 3 cells ? if it is cell, what is the size i lost in capacity ? 3 clusters of my format size (ntfs 4096).
is there a way to detect all the files on this box without running a full scandisk ? i tried to click on the box, but nothing is happening .



Maybe recovery does not star on OS boot drive when it's running. i understand the test is about "reading" but i guess the "recovering" is about writing...

"Recovery failed. Check the disk connection and perform a diagnostic scan again"

The physical connection (i mean plugs, sata port, material...etc) are fine, my OS is running with it, before, during the test and even after it ! So i guess Samsung Magician cannot recovery a SSD with error when it is the OS running. Seriously, Samsung coding team is naïve, they did not think i can hit the "recovery" button on my os drive ?

 

[delshay]

This thread has triggered me to check my 3 external backup drive. Giving OP a like for the heads-up.

 

[amiens80]

This thread has triggered me to check my 3 external backup drive. Giving OP a like for the heads-up.

you have dedicated external SSd!? what, you're a lucky one !
i have only hard drive for backup, not ssd one;

 

[delshay]

you have dedicated external SSd!? what, you're a lucky one !
i have only hard drive for backup, not ssd one;

They are external USB drives but they are actually inside the PC case always connected via a tiny USB hub that sits in-between the PCI slots. The USB hub itself plugs into the back of the Wi-Fi card.

Anyway all drives passed. If you look at the top of the screenshot you can see three drives connected, but there is a total of four Samsung SSD connected

EDIT UPDATE: Why is your drives taking such a long time to scan? Look at my drive, under 1 min for each 2TB drive.

 

[Shrek]

Why is your drives taking such a long time to scan? Look at my drive, under 1 min for each 2TB drive.

A full scan takes longer than a short scan (1GB only).

 

[delshay]

A full scan takes longer than a short scan (1GB only).

Thanks for the heads-up, did not see the drop down menu. Now I have to do a new scan.


EDIT: It's 1 hour 18 mins per 2TB SSD "full scan".

 

[SuperConker]

I would backup your data right away as that drive is no longer safe to use.

I lost 250 GB of important data on an 870 EVO 4TB because I thought it was safe to use it
(since it only had a couple of bad blocks on it at first).

Well, that was a huge mistake and I warn others not to make the same mistake

You can read more about it here:

Samsung 870 EVO - Beware, certain batches prone to failure!

Hello. From what I was able to read here, this EVO 870 is cursed. No series new or old is usable. In crystaldiskinfo, I got on 870 reallocated sector count 1159. I also have a Samsung 850EVO 256GB and 860EVO 1TB and in them no problems, reallocated sector count 0. Initially, I wanted to ask...

www.techpowerup.com

 

[Shrek]

Recovery failed...

Is it on the latest firmware?

 

[amiens80]

Recovery failed...

Is it on the latest firmware?

firmware is not yet updated because i can't find a way to clone my disk (OS + software drive).
Once i find a way to clone it, i will try the firware update. i can't take the risk to lost the OS+software configuration . To many hours of reinstallation whereas all my system is fine (except that dead red cell). my drive is 50% used of its capacity. i can't find which files are "bad".

 

[Shrek]

With the 980 Pro (don't know about the 870 EVO) a firmware update restores bad blocks... unless left too late when the whole disk goes read only and the update is no longer possible.
Samsung 980 Pro NVMe Failure and how to stop it from happening! - Bing video

Unfortunately the 870 EVO problem seems different from the Pro, so a firmware update will probably not bring it back.
Samsung 870 EVO - Beware, certain batches prone to failure! | TechPowerUp Forums
(I see you are aware of this thread)

Cloning may not be a good idea as things are probably already corrupted.

 

[SuperConker]

Cloning may not be a good idea as things are probably already corrupted.

Cloning might be the only option as once the 870 EVO decides to not let you have your files back
you're not getting them back (i learned that the hard way).

The corruption is due to bad sectors/blocks in the NAND flash so there is nothing that can really be done to repair files located on those blocks,
so the choice here is between cloning corrupted files or no files at all.

Cloning the corrupted files "as-is" is most likely the only option to get them back before the drive gets any worse (and it will).

 

[Shrek]

I meant for the OS; the other files should be copied across right away, no cloning needed.

Which leads me to a thought; I run an SSD with the files backed up by Windows to a seperate (spinning) disk, but if the originals get corrupted, I now wonder if the copies will also.

 

[Steevo]

I meant for the OS; the other files should be copied across right away, no cloning needed.

Which leads me to a thought; I run an SSD with the files backed up by Windows to a seperate (spinning) disk, but if the originals get corrupted, I now wonder if the copies will also.

I’m my experience only if they are complete replacement backups instead of incremental, and why anything but incremental back ups are a thing to and from the same physical media is a thing…… not a clue why that even is a option still. Even command line copy batch files can use incremental and skip files.

 

[MarsM4N]

I’m my experience only if they are complete replacement backups instead of incremental, and why anything but incremental back ups are a thing to and from the same physical media is a thing…… not a clue why that even is a option still. Even command line copy batch files can use incremental and skip files.

But there is still the problem that with incremental/version chain backups you'll run out of store space at one point and you have to create a new full backup. So in the end you'll still end up with a corrupted file you didn't know about, and you'll only find out if you stumble over it by accident because Windows NTFS didn't sent you a memo about a corrupted file.

To my knowledge the only protection from corrupted files is a proper multi bay NAS drive. Or maybe a more reliable file system for a single drive.

 

[amiens80]

To my knowledge the only protection from corrupted files is a proper multi bay NAS drive. Or maybe a more reliable file system for a single drive.

sorry to argument you, but a NAS without multiversion archive mode (versionning) is useless with corrupt files.

Today we have tool (and virus and tweak power tool) to alter a file without change the date or the file size.
NAS is good for protection again physical damages but it is useless again software damages....