Plunky Posted July 31, 2020 Share Posted July 31, 2020 Hi All, Amateur here, so bare with me: Recently swapped all my drives to a DELL R510 with a H200 in IT Mode. Everything booted up as expected. After some time I couldnt access Plex, so off I went to check what was wrong: For some reason, my SSD Cache was showing under cache + Unassigned devices, both with different IDs (sdc and sdl) A reboot or stop start of the array resolves the problem, but only for a few hours. I had a play around (changing file system from btrfs to xfs) so logs are full of me playing around. TIA! unraidnas-syslog-20200731-2215.zip Quote Link to comment
JorgeB Posted August 1, 2020 Share Posted August 1, 2020 Please post the diagnostics: Tools -> Diagnostics Quote Link to comment
Plunky Posted August 1, 2020 Author Share Posted August 1, 2020 Hi Jonnie, Diag attached. It hasn't happened since last reboot so not sure if it will show anything? Thank you. unraidnas-diagnostics-20200801-1917.zip Quote Link to comment
JorgeB Posted August 1, 2020 Share Posted August 1, 2020 46 minutes ago, Plunky said: It hasn't happened since last reboot so not sure if it will show anything? No, but still good to have them to look at all the hardware, looking at the earlier syslog the cache dropped offline, then reconnected with a different letter, h200 is not the best option for SSDs since trim won't work, if you can use a SATA port instead, if you don't have one swap/replace cables, if it keeps happening best bet is to try a different model SSD. Quote Link to comment
Plunky Posted August 2, 2020 Author Share Posted August 2, 2020 Hi Again, Not sure whats going on. Still no ssd cache drop, but logs are being spammed with the below. Is this because of the h200? I think the dell r510 has sata headers but no sata power, to power the drives. Should I uses a mechanical drive foe cache instead? Aug 2 17:39:23 unRAIDNAS ntfs-3g[11017]: Record 108627 has wrong SeqNo (12 <> 13) Aug 2 17:39:23 unRAIDNAS ntfs-3g[11017]: Could not decode the type of inode 108627 Aug 2 17:39:23 unRAIDNAS ntfs-3g[11017]: Could not decode the type of inode 229698 Aug 2 17:39:23 unRAIDNAS ntfs-3g[11017]: Could not decode the type of inode 229698 Aug 2 17:39:45 unRAIDNAS ntfs-3g[11017]: Record 108627 has wrong SeqNo (12 <> 13) Aug 2 17:39:45 unRAIDNAS ntfs-3g[11017]: Could not decode the type of inode 108627 Aug 2 17:39:45 unRAIDNAS ntfs-3g[11017]: Could not decode the type of inode 229698 Aug 2 17:39:45 unRAIDNAS ntfs-3g[11017]: Could not decode the type of inode 229698 Aug 2 17:40:08 unRAIDNAS ntfs-3g[11017]: Record 108627 has wrong SeqNo (12 <> 13) Aug 2 17:40:08 unRAIDNAS ntfs-3g[11017]: Could not decode the type of inode 108627 Aug 2 17:40:08 unRAIDNAS ntfs-3g[11017]: Could not decode the type of inode 229698 Aug 2 17:40:08 unRAIDNAS ntfs-3g[11017]: Could not decode the type of inode 229698 Aug 2 17:40:29 unRAIDNAS ntfs-3g[11017]: Record 108627 has wrong SeqNo (12 <> 13) Aug 2 17:40:29 unRAIDNAS ntfs-3g[11017]: Could not decode the type of inode 108627 Aug 2 17:40:29 unRAIDNAS ntfs-3g[11017]: Could not decode the type of inode 229698 Aug 2 17:40:29 unRAIDNAS ntfs-3g[11017]: Could not decode the type of inode 229698 unraidnas-diagnostics-20200802-1753.zip unraidnas-syslog-20200802-0753.zip Quote Link to comment
JorgeB Posted August 2, 2020 Share Posted August 2, 2020 Those errors are from an unassigned NTFS device, note the the errors might persist until you reboot even the device was already removed/disconnected. Quote Link to comment
Plunky Posted August 11, 2020 Author Share Posted August 11, 2020 Hi Johnnie, Its back again. Had a solid week of no failures and now back to daily failures and reboots or array stop/start. I have the Dell R510 12 bay with 2 Internal Bays. The Sata Ports on the motherboard are permanently disabled so I can't use them and trying to get power to them is another challenge as well. I did come across another thread about downgrading the controller firmware to 16.00.00 (I think it was). But can't find again now. Otherwise I'll have to use a Mechanical HDD as a cache drive instead, which seems pointless. Quote Link to comment
JorgeB Posted August 12, 2020 Share Posted August 12, 2020 9 hours ago, Plunky said: I did come across another thread about downgrading the controller firmware to 16.00.00 (I think it was). But can't find again now. You can do that but note that LSI HBAs can only trim SSDs with read zeros after trim support. Quote Link to comment
Plunky Posted August 12, 2020 Author Share Posted August 12, 2020 Back again with Diags and logs from after the crash and no reboot. Do I have dodgy ssd? unraidnas-diagnostics-20200813-0811.zip unraidnas-syslog-20200812-2213.zip Quote Link to comment
JorgeB Posted August 13, 2020 Share Posted August 13, 2020 8 hours ago, Plunky said: Do I have dodgy ssd? Most likely just one that doesn't work well with an LSI, and IIRC I've seen it before with that model, if you can't use the Intel ports try a different model SSD if possible. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.