Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Cant Assign 14TB Drives to my array

Featured Replies

Hi everyone.  I'm brand new to Unraid (seriously, I just got a supermicro CSE-846 and got it running unraid 20 minutes ago).  I also have 3 14TB Seagate Exos drives,  4-4TB drives and an SSD I want to use for cache.

 

The strange thing is, when i try to mount any of the 14TB drives as a parity drive or as drives in the array, the page refreshes like it was successful, but then the drive disappears.  If i reboot the system it shows back up.

 

I did some searching in this forum and it seems like i'm having the same problem as this post,  only I (am ashamed to admit) i dont really how to hook these up to onboard stata ports when I want to put them in the hot-swappable bays.  Is there another path to troubleshoot this that lets me take advantage of these drives?

 

I did see in other posts that tools --> Diagnostics are helpful, so attaching mine.

 

Thanks everyone for help in advance. 

odyssey-diagnostics-20221126-2122.zip

Solved by SimonF

  • Author

I was trying this once more and checking logs as it happened.  This section seems to be the error:

 

Nov 26 19:26:42 odyssey kernel: protection error, dev sdf, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
Nov 26 19:26:42 odyssey kernel: mpt3sas_cm0: log_info(0x3112043b): originator(PL), code(0x12), sub_code(0x043b)
Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 UNKNOWN(0x2003) Result: hostbyte=0x05 driverbyte=DRIVER_OK cmd_age=0s
Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 Sense Key : 0x5 [current] 
Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 ASC=0x10 ASCQ=0x3 
Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 CDB: opcode=0x7f, sa=0x9
Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 CDB[00]: 7f 00 00 00 00 00 00 18 00 09 20 00 00 00 00 00
Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 CDB[10]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01
Nov 26 19:26:42 odyssey kernel: protection error, dev sdf, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Nov 26 19:26:42 odyssey kernel: Buffer I/O error on dev sdf, logical block 0, async page read
Nov 26 19:26:42 odyssey  emhttpd: error: ckmbr, 2291: Input/output error (5): read: /dev/sdf
Nov 26 19:26:42 odyssey  emhttpd: ckmbr error: -1

Pls note on error message

 

Nov 26 19:26:42 odyssey kernel: protection error, dev sdf, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

 

And check the SMART, those SAS disk seems format in 4Kn, pls found post for reformat SAS disk to 512e ( I haven't any SAS disk )

 

=== START OF INFORMATION SECTION ===
Vendor:               IBM-ESXS
Product:              ST14000NM0288 E
Revision:             ECH8
Compliance:           SPC-5
User Capacity:        13,902,809,137,152 bytes [13.9 TB]
Logical block size:   4096 bytes
Formatted with type 2 protection
8 bytes of protection information per logical block

Edited by Vr2Io

  • Community Expert
  • Solution
5 hours ago, mew0717 said:

I was trying this once more and checking logs as it happened.  This section seems to be the error:

 

Nov 26 19:26:42 odyssey kernel: protection error, dev sdf, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
Nov 26 19:26:42 odyssey kernel: mpt3sas_cm0: log_info(0x3112043b): originator(PL), code(0x12), sub_code(0x043b)
Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 UNKNOWN(0x2003) Result: hostbyte=0x05 driverbyte=DRIVER_OK cmd_age=0s
Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 Sense Key : 0x5 [current] 
Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 ASC=0x10 ASCQ=0x3 
Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 CDB: opcode=0x7f, sa=0x9
Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 CDB[00]: 7f 00 00 00 00 00 00 18 00 09 20 00 00 00 00 00
Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 CDB[10]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01
Nov 26 19:26:42 odyssey kernel: protection error, dev sdf, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Nov 26 19:26:42 odyssey kernel: Buffer I/O error on dev sdf, logical block 0, async page read
Nov 26 19:26:42 odyssey  emhttpd: error: ckmbr, 2291: Input/output error (5): read: /dev/sdf
Nov 26 19:26:42 odyssey  emhttpd: ckmbr error: -1

as per smart posted by Vr2lo you need to remove type 2 protection 

 

Edited by SimonF

  • 2 weeks later...
  • Author

The Solution to this is above, but it will require a little digging.  For those who want the digging done for them, here's the TL'DR.

- This thread is what I used to find the answer (it's a link to another thread which you can get to in the thread posted above)

- This page with the actual solution.

 

Ultimately once I confirmed there was protection,  this was the only thing i needed to do... 

sg_format --format --fmtpinfo=0 /dev/sda

 

where /sda is the name of the disk you want to format.  

 

There was a lot of talk about sg3 tools etc, but i didnt need those in the end. 

 

One tip ... Formatting these drives takes a long, long time.  Im not familiar enough to know how to see the status of the format if you start it in an Unraid terminal from the web interface and then close that terminal, so i'd recommend doing the format on the actual bare metal linux terminal when you start the machine.

Edited by mew0717

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.