FizzPumpkin Posted April 18 Share Posted April 18 My drives aren't all detected when I start the array after moving to a new machine (new but same board). I took out the drives into a hard drive toaster and all of them boot normal and are detected on my normal laptop. I've provided diagnostics and an image of what the array looks like (apologies for quality). Would anyone be able to help me figure out what's going on? I have a backup of most of the data. Any input is greatly appreciated. starforge-diagnostics-20240411-0454.zip Quote Link to comment
JorgeB Posted April 18 Share Posted April 18 Check to see if they are being detected in the board BIOS. 1 Quote Link to comment
FizzPumpkin Posted April 20 Author Share Posted April 20 Thanks for your help. I checked and only see 4 of the HDD drives. I have a total of 6. I got this from some old logs I had: WDC_WD20PURZ-85GU6Y0_WD-WCC4M5UN4636 (sdh) 512 3907029168 WDC_WD100EMAZ-00WJTA0_1EGKSV7Z (sde) 512 19532873728 ST1000LM024_HN-M101MBB_S30CJ9DDC00672 (sdb) 512 1953525167 WDC_WD80EFAX-68KNBN0_VAHX169L (sdf) 512 15628053168 WDC_WD100EMAZ-00WJTA0_1EGAB99N (sdc) 512 19532873728 Here is a list of each drive's model numbers: WD120EDAZ-11F3RAO WD80EFZX-68UW8N0 WD100EMAZ-OOWJTAO WD100EMAZ-00WJTAO WD80EFAX-68KNBN0 ST8000VN004 [I was planning to use this IronWolf811d8eb460b23ddd79546314200bb51b55b28f3b.rtfd to replace either WD80EFAX-68KNBN0 or WD80EFZX-68UW8N0, can't remember which was having temp issues]. Quote Link to comment
JorgeB Posted April 20 Share Posted April 20 If the disks are not detected in the BIOS they also won't be detected by Unraid, swap both cables from a non working disk and see if it's detected. 1 Quote Link to comment
FizzPumpkin Posted April 20 Author Share Posted April 20 I tried that and was able to narrow the problem to two of the drives. WD100EMAZ-OOWJTAO WD120EDAZ-11F3RAO When I put them back in the drive toaster, they're still detected on my laptop, but not in BIOS when I put them in the board, even after swapping the sata data cables around. Quote Link to comment
Solution JorgeB Posted April 21 Solution Share Posted April 21 Could be 3.3v SATA issue: Quote Link to comment
FizzPumpkin Posted April 21 Author Share Posted April 21 OH RIGHT! I've heard of this issue but never experienced it. I'll review and report back. Quote Link to comment
FizzPumpkin Posted April 27 Author Share Posted April 27 It was in fact the 3.3v issue. I'm surprised it happened since I did not change anything other than re-buying the same motherboard. I followed the instructions in the video below to resolve it (using the tape). Everything now detects. Thank you! 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.