sexyj Posted October 6, 2022 Share Posted October 6, 2022 Whenver I'm starting a new array, the process is crashing and tells me the drive dev name changed Oct 6 06:14:26 FS1 emhttpd: error: hotplug_devices, 1730: No medium found (123): Error: tagged device WDC_WD40EZAZ-19SF3B0_WD-WX42D51N5035 was (sdi) is now (sdn) Anyway one know if there is some settings I can set? Using 2 x SAS2008 controller fs1-diagnostics-20221006-1032.zip Quote Link to comment
JorgeB Posted October 6, 2022 Share Posted October 6, 2022 Disk dropped and reconnected again with a different identifier, could be power/connection problem, you should also update both HBAs firmware since it's quite old. Quote Link to comment
trurl Posted October 6, 2022 Share Posted October 6, 2022 In addition to dropping / disabling parity, disk3 is unmountable which you don't mention. 15 minutes ago, sexyj said: starting a new array Why is disk2 reiserfs? Quote Link to comment
sexyj Posted October 6, 2022 Author Share Posted October 6, 2022 (edited) 7 hours ago, JorgeB said: Disk dropped and reconnected again with a different identifier, could be power/connection problem, you should also update both HBAs firmware since it's quite old. So I updated both controller's fw. For some reason one controller is no longer detecting the drives. Doing some research on it, it indicate it's the cable (forward/reverse) breakout cable. But the cable was obviously working prior to the upgrade. The controller in question is a PIKE 2008, current status in the Controller BIOS https://prnt.sc/JlKC8xYdfiiL Is there anything you can think of? Edit: Problem solved with the controller not being found. Turns out the sas2flash -listall and the syslog order is reverse. Anyway. The problem with the drive changing name still persists after the FW upgrades. I actually have swapped the cable before... Very weird. Edit 2: Upload the latest diag after fixing the controllers fs1-diagnostics-20221006-1827.zip Edited October 6, 2022 by sexyj Quote Link to comment
JorgeB Posted October 7, 2022 Share Posted October 7, 2022 Other than being SMR disk looks OK, I would try swapping cables between that disk and another one and/or connecting it to the onboard SATA instead. Quote Link to comment
sexyj Posted October 7, 2022 Author Share Posted October 7, 2022 Perhaps there's some compatibility issue with the board when running on 2 x 2008 controller. Took the Pike 2008 out and plugged in another standalone LSI card, same issue. Ended up taking all the stand alone card out and just plugged in the Pike. No problem with it... Very strange issue. 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.