Detailed Instructions: Given an Amazon review, indicate whether it is a 'Positive Review' or 'Negative Review'.
Problem:Immediately after setting up my 5N I had issues where the SMB share used for a surveillance camera looked strange.  I activated SSH login and started looking around the share while logged into the Drobo.  I got &#34;Input/output error&#34; for a large number of files on the share.  Rebooting the Drobo didn't fix it and the Dashboard said everything was fine.  I was able to delete these files on the command line after a few tries but it's very likely that volume corruption persists.  Drobo tech support agreed when I contacted them and said I could press Control-Shift-P in the Dashboard to initiate a filesystem check.  It doesn't do anything.  A quick check on Google verifies that nobody found it to work.  Drobo tech support's recommendation now is to BUY A SECOND DROBO and copy everything to it, then back.  Seriously?  The Drobo 5N has defective software and the solution is to buy two of them?  Other than that it's decently fast.  UPDATE: I figured out how unmount the RAID and run e2fsck while logged into the 5N's Linux system.  The volume was definitely corrupted despite everything in the Dashboard saying it was fine.  Don't trust your Drobo.  UPDATE 2: Lots more file corruption even though the Dashboard says everything is healthy.  Systems logs in the Drobo look like: Dec  3 15:19:28 shockwave user.info kernel: [ 1580.977417] dri_dnas_abort: called to abort cmnd: cdb=5a b1f71220, b181ad48 Dec  3 15:29:36 shockwave user.info kernel: [ 2189.267245] dri_dnas_abort: called to abort cmnd: cdb=93 b2242940,   (null) Dec  3 15:29:36 shockwave user.info kernel: [ 2189.274825] dri_dnas_abort: called to abort cmnd: cdb=93 a621f9e0,   (null) Dec  3 15:29:36 shockwave user.info kernel: [ 2189.282210] dri_dnas_abort: called to abort cmnd: cdb=93 b2242080,   (null) Dec  3 15:29:36 shockwave user.info kernel: [ 2189.289499] dri_dnas_abort: called to abort cmnd: cdb=93 b2242800,   (null) Dec  3 15:29:36 shockwave user.info kernel: [ 2189.296969] sd 0:0:0:0: [sda] Unhandled error code Dec  3 15:29:36 shockwave user.info kernel: [ 2189.302041] sd 0:0:0:0: [sda]  Result: hostbyte=0x00 driverbyte=0x06 Dec  3 15:29:36 shockwave user.info kernel: [ 2189.308753] sd 0:0:0:0: [sda] CDB: cdb[0]=0x93: 93 08 00 00 00 05 41 dd c8 00 00 00 10 00 00 00 Dec  3 15:29:36 shockwave user.err kernel: [ 2189.318698] end_request: I/O error, dev sda, sector 22579890176 Dec  3 15:29:36 shockwave user.info kernel: [ 2189.324908] sd 0:0:0:0: [sda] Unhandled error code Dec  3 15:29:36 shockwave user.info kernel: [ 2189.329965] sd 0:0:0:0: [sda]  Result: hostbyte=0x00 driverbyte=0x06 Dec  3 15:29:36 shockwave user.info kernel: [ 2189.336646] sd 0:0:0:0: [sda] CDB: cdb[0]=0x93: 93 08 00 00 00 05 41 dd d8 00 00 00 10 00 00 00 Dec  3 15:29:36 shockwave user.err kernel: [ 2189.346549] end_request: I/O error, dev sda, sector 22579894272 Dec  3 15:29:36 shockwave user.info kernel: [ 2189.352778] sd 0:0:0:0: [sda] Unhandled error code Dec  3 15:29:36 shockwave user.info kernel: [ 2189.357887] sd 0:0:0:0: [sda]  Result: hostbyte=0x00 driverbyte=0x06 Dec  3 15:29:36 shockwave user.info kernel: [ 2189.364527] sd 0:0:0:0: [sda] CDB: cdb[0]=0x93: 93 08 00 00 00 05 41 dd e8 00 00 00 10 00 00 00 Dec  3 15:29:36 shockwave user.err kernel: [ 2189.374470] end_request: I/O error, dev sda, sector 22579898368 Dec  3 15:29:36 shockwave user.info kernel: [ 2189.380697] sd 0:0:0:0: [sda] Unhandled error code Dec  3 15:29:36 shockwave user.info kernel: [ 2189.385755] sd 0:0:0:0: [sda]  Result: hostbyte=0x00 driverbyte=0x06 Dec  3 15:29:36 shockwave user.info kernel: [ 2189.392562] sd 0:0:0:0: [sda] CDB: cdb[0]=0x93: 93 08 00 00 00 05 41 dd f8 00 00 00 10 00 00 00 Dec  3 15:29:36 shockwave user.err kernel: [ 2189.402425] end_request: I/O error, dev sda, sector 22579902464 Dec  3 15:33:08 shockwave user.err kernel: [ 2400.707442] INFO: task cnid_dbd:14061 blocked for more than 120 seconds. Dec  3 15:33:08 shockwave user.err kernel: [ 2400.714173] &#34;echo 0 &#62; /proc/sys/kernel/hung_task_timeout_secs&#34; disables this message. Dec  3 15:33:08 shockwave user.info kernel: [ 2400.722047] cnid_dbd        D 804ad758     0 14061   1450 0x00000000 Dec  3 15:33:08 shockwave user.warn kernel: [ 2400.728474] Backtrace:  Dec  3 15:33:08 shockwave user.warn kernel: [ 2400.730960] [&#60;804ad264&#62;] (__schedule+0x0/0x5d4) from [&#60;804ad97c&#62;] (schedule+0x78/0x7c) Dec  3 15:33:08 shockwave user.warn kernel: [ 2400.738926] [&#60;804ad904&#62;] (schedule+0x0/0x7c) from [&#60;8017ab24&#62;] (jbd2_log_wait_commit+0xf0/0x16c) Dec  3 15:33:08 shockwave user.warn kernel: [ 2400.747767] [&#60;8017aa34&#62;] (jbd2_log_wait_commit+0x0/0x16c) from [&#60;8013d0a8&#62;] (ext4_sync_file+0x1d0/0x20c) Dec  3 15:33:08 shockwave user.warn kernel: [ 2400.757292] [&#60;8013ced8&#62;] (ext4_sync_file+0x0/0x20c) from [&#60;800ed90c&#62;] (vfs_fsync_range+0x3c/0x4c) Dec  3 15:33:08 shockwave user.warn kernel: [ 2400.766207]  r8:8000dc88 r7:00000094 r6:2ae710c8 r5:7fffffff r4:ffffffff Dec  3 15:33:08 shockwave user.warn kernel: [ 2400.773019] [&#60;800ed8d0&#62;] (vfs_fsync_range+0x0/0x4c) from [&#60;800ed948&#62;] (vfs_fsync+0x2c/0x34) Dec  3 15:33:08 shockwave user.warn kernel: [ 2400.781413]  r5:7fffffff r4:ffffffff Dec  3 15:33:08 shockwave user.warn kernel: [ 2400.785072] [&#60;800ed91c&#62;] (vfs_fsync+0x0/0x34) from [&#60;800edb98&#62;] (do_fsync+0x28/0x3c) Dec  3 15:33:08 shockwave user.warn kernel: [ 2400.792859]  r5:00000001 r4:b1fa8a20 Dec  3 15:33:08 shockwave user.warn kernel: [ 2400.796505] [&#60;800edb70&#62;] (do_fsync+0x0/0x3c) from [&#60;800edbc0&#62;] (sys_fdatasync+0x14/0x18) Dec  3 15:33:08 shockwave user.warn kernel: [ 2400.804654]  r5:0005aaa0 r4:00000000 Dec  3 15:33:08 shockwave user.warn kernel: [ 2400.808308] [&#60;800edbac&#62;] (sys_fdatasync+0x0/0x18) from [&#60;8000dae0&#62;] (ret_fast_syscall+0x0/0x30)
Solution:
Negative Review