gcoupe 63 Posted May 7, 2016 Posted May 7, 2016 My Windows 10 Pro (headless server) has a Samsung 850 EVO SSD (250GB) for the C: drive. My media is held on HDDs in the server. Twice in the past month, I've discovered that Windows is reporting errors on the C: drive. Running CHKDSK during startup has repaired the issue. Both times, CHKDSK has reported that the problems were found in Emby files. That may just be coincidence, or it may be a clue to the cause. I see errors such as: Stage 1: Examining basic file system structure ... Found 0xd clusters allocated to file "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\38\38694321430f97fd8fa9094562764aef\folder.png <0x9,0xfa78>" at offset "0x34f" marked as free ... repaired online. Found 0x4 clusters allocated to file "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\38\38694321430f97fd8fa9094562764aef\landscape.png <0x58,0xfa82>" at offset "0" marked as free ... repaired online. Found 0x96 clusters allocated to file "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\38\38694321430f97fd8fa9094562764aef\landscape.png <0x58,0xfa82>" at offset "0x2c6" marked as free ... repaired online.Attribute record of type 0x80 and instance tag 0x3 is cross linkedstarting at 0x73fc22 for possibly 0xfc clusters. Found corrupt basic file structure for "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\0d\0d1c8e64d562e1d2494c0b325bbcb2d0\folder.png <0x2c,0xfa96>" ... repaired online. Found 0x29 clusters allocated to file "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\07\0762ef154ffdc38825d31aa6eb6a8ab5\landscape.png <0x9,0xff98>" at offset "0x37c" marked as free ... repaired online. Found 0x1 clusters allocated to file "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\9f\9ff413f511c1da9586f9d970d19baaad\folder.png <0xb,0xff9c>" at offset "0" marked as free ... repaired online. Found 0x1 clusters allocated to file "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\9f\9ff413f511c1da9586f9d970d19baaad\landscape.png <0xd,0xff9f>" at offset "0" marked as free ... repaired online. Found 0x5 clusters allocated to file "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\9f\9ff413f511c1da9586f9d970d19baaad\landscape.png <0xd,0xff9f>" at offset "0x2d8" marked as free ... repaired online. Found 0xe clusters allocated to file "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\8b\8be5d152686cdf7948d0dcc7a670439b\landscape.png <0xb,0xffae>" at offset "0x153" marked as free ... repaired online.Attribute record of type 0x80 and instance tag 0x3 is cross linkedstarting at 0x5f6054 for possibly 0x2ed clusters. Found corrupt basic file structure for "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\3c\3c2d3377642118f565cbdd2c993fc1a6\folder.png <0x2c,0xffb4>" ... repaired online.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x148515 for possibly 0x2ed clusters. Found corrupt basic file structure for "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\3c\3c2d3377642118f565cbdd2c993fc1a6\landscape.png <0x21,0xffb8>" ... repaired online. Found 0x12 clusters allocated to file "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\62\62559638ae34eb7826b12355913e025c\folder.png <0xc,0xffcc>" at offset "0x131" marked as free ... repaired online.Attribute record of type 0x80 and instance tag 0x3 is cross linkedstarting at 0xa86837 for possibly 0x131 clusters. Found corrupt basic file structure for "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\7d\7d768be9a39d62452d2b622ef888e890\folder.png <0x13,0x101f1>" ... repaired online.Attribute record of type 0x80 and instance tag 0x3 is cross linkedstarting at 0x6ecb02 for possibly 0x12d clusters. Found corrupt basic file structure for "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\c0\c02e2f7044d255999fd1428f2621aad6\folder.png <0x53,0x101fe>" ... repaired online. Found 0x4 clusters allocated to file "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\0e\0e23db8267d157d4525f984eaf7ae078\folder.png <0x25,0x1126d>" at offset "0" marked as free ... repaired online.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x314d2a for possibly 0x1ce clusters. Found corrupt basic file structure for "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\ed\edc55e7c23b9b0b0ecb582cac22097b5\landscape.png <0x23,0x1134b>" ... repaired online.Attribute record of type 0x80 and instance tag 0x3 is cross linkedstarting at 0x2f5c8c for possibly 0x2d7 clusters. Found corrupt basic file structure for "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\c5\c5cb6c628cff1da39cc36286a2fc35f8\folder.png <0x12f,0x11f4b>" ... repaired online.Attribute record of type 0x80 and instance tag 0x3 is cross linkedstarting at 0x5be83a for possibly 0x279 clusters. Found corrupt basic file structure for "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\70\700426172105cdd0464ff0d400d6a38e\folder.png <0x5c,0x13d84>" ... repaired online.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x131d208 for possibly 0x394 clusters. Found corrupt basic file structure for "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\de\de8c0f82e948c59a6ec38b5959c572bd\landscape.png <0x11,0x14068>" ... repaired online. Found 0x2 clusters allocated to file "\Users\gcoup\AppData\Roaming\Emby-Server\metadata\library\0e\0eee8dbe2668d22d1802b5d3a105b7d3\landscape.png <0xc,0x140ad>" at offset "0" marked as free"Chkdsk /scan" is restarting due to stale information about crosslinks. ---------------------------------------------------------------------- Stage 1: Examining basic file system structure ...Some clusters occupied by attribute of type 0x80 and instance tag 0x3in file 0xfa96 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0xFA96.Some clusters occupied by attribute of type 0x80 and instance tag 0x3in file 0xffb4 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0xFFB4.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0xffb8 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0xFFB8.Some clusters occupied by attribute of type 0x80 and instance tag 0x3in file 0x101f1 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x101F1.Some clusters occupied by attribute of type 0x80 and instance tag 0x3in file 0x101fe is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x101FE.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0x1134b is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x1134B.Some clusters occupied by attribute of type 0x80 and instance tag 0x3in file 0x11f4b is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x11F4B.Some clusters occupied by attribute of type 0x80 and instance tag 0x3in file 0x13d84 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x13D84.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0x14068 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x14068."Chkdsk /scan" is restarting due to stale information about crosslinks.An unspecified error occurred (6672737374727563 542). Could these issues be caused by the SSD failing, or should I be looking elsewhere for the cause? TIA.
Luke 42085 Posted May 7, 2016 Posted May 7, 2016 Are there any other diagnostics you can run? I have a larger version of the same drive and it's been excellent.
Koleckai Silvestri 1154 Posted May 7, 2016 Posted May 7, 2016 (edited) You should install and run Samsung's Magician app. It will diagnose your SSD and let you know if you have any problems. It will even optimize your OS to use the SSD in the best possible way. I have two of the above drives. One in the server and one in my workstation. They have been great. Edited May 7, 2016 by Koleckai Silvestri
gcoupe 63 Posted May 7, 2016 Author Posted May 7, 2016 Thanks, I've installed Samsung Magician. I note that it has recommended a firmware update, which I've downloaded and applied. I'll keep an eye on the situation.
gcoupe 63 Posted May 13, 2016 Author Posted May 13, 2016 The SSD was still causing errors after the firmware upgrade. I replaced it with an HDD temporarily, and the errors went away, so I think that the issue lies with the SSD. I've initiated an RMA for it, as it's still within the warranty period of 3 years.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now