vsonerud Posted September 30, 2022 Share Posted September 30, 2022 (edited) Hi! I have recently bought a new Western Digital UltraStar 18 TB drive and connected it to my unRAID server. The drive is detected and succesfully assigned the /dev/sdi device - and I have succesfully run both short and extended SMART self tests as well as 1 successful preclear cycle using the docker-based binhex preclear plugin. However, when attempting to add it as my new parity drive (instead of my current 8 TB drive) something strange happens. I stop the array - and immediately after I have selected the new 18 TB drive in the drop-down list for the first parity drive slot - the drop down list refreshes / resets - and nothing ends up being selected. Thereafter the new 18 TB drive is gone from the drop down list of available drives to select (the old parity drive is the only one available). If i then select the old parity drive and restarts the array and repeat the process above, the new 18 TB parity drive is available for selection but after selecting it the drop-down list resets and nothing is selected and the drive disappears once again from the drop-down list. I have also tried the Tools | New config route - both with selecting that I want to preserve all previous assignments, but also selecting preserving only 'Data drives and Cache drives' from previous assignments. In both cases the same as above happens - I am able to select the new 18 TB drive but the drop-down resets to nothing after selecting the drive. The following excerpt from the syslog happens when attempting to select the new 18 TB drive as parity: Sep 30 17:27:17 Tower emhttpd: req (25): changeDevice=apply&csrf_token=****************&slotId.0=WDC_WUH721818ALE6L4_2MJ9EKDG Sep 30 17:27:17 Tower emhttpd: shcmd (26821): rmmod md-mod Sep 30 17:27:17 Tower kernel: md: unRAID driver removed Sep 30 17:27:17 Tower emhttpd: shcmd (26822): modprobe md-mod super=/boot/config/super.dat Sep 30 17:27:17 Tower kernel: md: unRAID driver 2.9.3 installed Sep 30 17:27:17 Tower emhttpd: Device inventory: Sep 30 17:27:17 Tower emhttpd: ST8000VN0022-2EL112_ZA1E12T7 (sdj) 512 15628053168 Sep 30 17:27:17 Tower emhttpd: ST8000VN0022-2EL112_ZA15RXGL (sdg) 512 15628053168 Sep 30 17:27:17 Tower emhttpd: HGST_HDN724040ALE640_PK1334PCJWU0JS (sdh) 512 7814037168 Sep 30 17:27:17 Tower emhttpd: HGST_HDN724040ALE640_PK2334PEJ7YKST (sdd) 512 7814037168 Sep 30 17:27:17 Tower emhttpd: HGST_HDN724040ALE640_PK1334PBKDE35S (sde) 512 7814037168 Sep 30 17:27:17 Tower emhttpd: Hitachi_HDS723020BLA642_MN1220F30E225D (sdb) 512 3907029168 Sep 30 17:27:17 Tower emhttpd: HGST_HDN724040ALE640_PK1381PCJZ0VLS (sdf) 512 7814037168 Sep 30 17:27:17 Tower emhttpd: HGST_HDN724040ALE640_PK1381PCKY343S (sdc) 512 7814037168 Sep 30 17:27:17 Tower emhttpd: WDC_WUH721818ALE6L4_2MJ9EKDG (sdi) 512 35156656128 Sep 30 17:27:17 Tower emhttpd: Sony_Storage_Media_1A08012384785-0:0 (sda) 512 3962880 Sep 30 17:27:17 Tower kernel: mdcmd (1): import 0 sdi 64 17578328012 0 WDC_WUH721818ALE6L4_2MJ9EKDG Sep 30 17:27:17 Tower kernel: md: import disk0: lock_bdev error: -13 Sep 30 17:27:17 Tower kernel: mdcmd (2): import 1 sdf 64 3907018532 0 HGST_HDN724040ALE640_PK1381PCJZ0VLS Sep 30 17:27:17 Tower kernel: md: import disk1: (sdf) HGST_HDN724040ALE640_PK1381PCJZ0VLS size: 3907018532 Sep 30 17:27:17 Tower kernel: md: disk1 new disk The 2 highlighted lines above is for the problematic new 18 TB drive. Anyone who has seen anything like this before, or have any good advice what could be the problem or what I should attempt to do to resolve the matter? The unRAID server is running version 6.5.3 and should work for this drive I think. But I am in the process of attempting to upgrade to 6.10.3 The 18 TB drive is connected to a HBA card which originally was a IBM M1015 card - flashed many years ago with LSI SAS 9211-8i IT-mode firmware (version 15.0.0.0 ) and BIOS. And as mentioned above I have successfully precleared the drive.... It might also be worth mentioning that the server has currently 7 array devices (1 * 8TB drive for parity, 1 * 8TB data drive and 5 * 4 TB data drives) as well as a 2 TB cache drive - and the new unassigned 18 TB drive. The 5 * 4 TB data drives and the 2 TB cache drive is still using ReiserFS - and I was planning to convert these drives to XFS after having added the new 18 TB drive for parity, and then using the old 8TB parity drive for data. ReiserFS apparently has a 16 TB hard limit, but could that affect the attempt to assign a brand new 18 TB unformatted drive as a parity drive ? (I have also configured the server to have XFS as default file system ) Edited September 30, 2022 by vsonerud Quote Link to comment
JorgeB Posted September 30, 2022 Share Posted September 30, 2022 15 minutes ago, vsonerud said: ReiserFS apparently has a 16 TB hard limit, but could that affect the attempt to assign a brand new 18 TB unformatted drive as a parity drive ? Nope. 15 minutes ago, vsonerud said: (version 15.0.0.0 This is old, update to latest or try connecting that disk on an onboard SATA port if available, you can swap with another one, if it still fails post the complete diagnostics please. Quote Link to comment
vsonerud Posted September 30, 2022 Author Share Posted September 30, 2022 1 hour ago, JorgeB said: Nope. This is old, update to latest or try connecting that disk on an onboard SATA port if available, you can swap with another one, if it still fails post the complete diagnostics please. Just tried to connect the 18 TB disk to an onboard SATA port - voila, now it worked like a charm to add as a parity drive and parity rebuild is in progress after starting the array 😃 1 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.