mostlybroken Posted February 9, 2022 Share Posted February 9, 2022 Afternoon, I have a bit of an unusal one: Alongside the main array, I have had one SATA SSD (/dev/sdj) mounted as an anassigned device. This has been fine for well over a year. Today, I added a second SSD (/dev/sdi), identical to the first. In unassigned devices however, the new SSD did not initally show up. So, I manually created a partition using fdisk. - right away, the new SSD (/dev/sdi) showed up as dev1 in unassigned devices. - however the original SSD (/sdj) has disapeared, being listed as a 'Historical Device'. - weird! Now, I have a game of ping pong on my hands, resync the disks in fdisk - old SSD returns as dev1, sync again, back to new SSD as dev1 - however no matter what I try, I cannot get both to show up at the same time! I assume that unraid is parsing the Serial number / names incorrectly and thinking they're the same device? However: they have different IDs (/sdi, /sdj) lshw shows (correct) and different S/N's for both drives lshw also gives a different hardware address for each drive (2:0:7:0 and 2:0:8:0) This being the case... what is going on here? Both SSDs obviously have the same model name, although I can't see that being an issue (all my main array disks are identical too). At the end of my (limited) knowleage on what to try now - any help is much appreciated! Some disk logs, pick up in-between syncing disks in fdisk, and them swapping place as dev1 (note the error getting id in the log - this is when I sync'd the disks and they swapped place: Spoiler Bay 11 - New SSD - /dev/sdi - 1946E3D72DD0 ErrorWarningSystemArray Feb 9 14:47:45 Concorde kernel: sd 2:0:7:0: [sdi] 234441648 512-byte logical blocks: (120 GB/112 GiB) Feb 9 14:47:45 Concorde kernel: sd 2:0:7:0: [sdi] Write Protect is off Feb 9 14:47:45 Concorde kernel: sd 2:0:7:0: [sdi] Mode Sense: 46 00 10 08 Feb 9 14:47:45 Concorde kernel: sd 2:0:7:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Feb 9 14:47:45 Concorde kernel: sdi: Feb 9 14:47:45 Concorde kernel: sd 2:0:7:0: [sdi] Attached SCSI disk Feb 9 14:51:42 Concorde emhttpd: device /dev/sdi problem getting id Feb 9 15:00:20 Concorde emhttpd: device /dev/sdi problem getting id Feb 9 15:01:15 Concorde emhttpd: device /dev/sdi problem getting id Feb 9 15:08:37 Concorde kernel: sdi: Feb 9 15:08:40 Concorde kernel: sdi: Feb 9 15:14:21 Concorde emhttpd: device /dev/sdi problem getting id Feb 9 15:14:31 Concorde kernel: sdi: Feb 9 15:14:34 Concorde kernel: sdi: Feb 9 15:16:46 Concorde emhttpd: device /dev/sdi problem getting id Feb 9 15:17:17 Concorde kernel: sdi: Feb 9 15:17:18 Concorde kernel: sdi: Spoiler Bay 12 - Old SSD - /dev/sdj - 2006E3EB38FA Feb 9 14:47:45 Concorde kernel: sd 2:0:8:0: [sdj] 234441648 512-byte logical blocks: (120 GB/112 GiB) Feb 9 14:47:45 Concorde kernel: sd 2:0:8:0: [sdj] Write Protect is off Feb 9 14:47:45 Concorde kernel: sd 2:0:8:0: [sdj] Mode Sense: 46 00 10 08 Feb 9 14:47:45 Concorde kernel: sd 2:0:8:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Feb 9 14:47:45 Concorde kernel: sdj: Feb 9 14:47:45 Concorde kernel: sd 2:0:8:0: [sdj] Attached SCSI disk Feb 9 14:51:42 Concorde emhttpd: CT120BX500SSD1_2006E3EB38FA_30000000000000000 (sdj) 512 234441648 Feb 9 14:51:42 Concorde emhttpd: read SMART /dev/sdj Feb 9 15:01:12 Concorde kernel: sdj: Feb 9 15:14:17 Concorde kernel: sdj: Feb 9 15:16:43 Concorde kernel: sdj: Feb 9 15:22:30 Concorde kernel: sdj: Quote Link to comment
Squid Posted February 9, 2022 Share Posted February 9, 2022 You would probably want to post in the Unassigned devices thread so that @dlandon can see what's going on and advise accordingly... Also include your diagnostics Quote Link to comment
mostlybroken Posted February 9, 2022 Author Share Posted February 9, 2022 1 minute ago, Squid said: You would probably want to post in the Unassigned devices thread so that @dlandon can see what's going on and advise accordingly... Also include your diagnostics ah - can I move the post, or? Quote Link to comment
dlandon Posted February 9, 2022 Share Posted February 9, 2022 Update to the latest version of UD. Quote Link to comment
mostlybroken Posted February 9, 2022 Author Share Posted February 9, 2022 (edited) 1 hour ago, dlandon said: Update to the latest version of UD. Thanks @dlandon - have just done so. This has changed the behaviour; now /dev/sdj persists despite disk syncs; however I'm still unable to get /dev/sdi to list? Edited February 9, 2022 by mostlybroken Quote Link to comment
dlandon Posted February 9, 2022 Share Posted February 9, 2022 56 minutes ago, mostlybroken said: Thanks @dlandon - have just done so. This has changed the behaviour; now /dev/sdj persists despite disk syncs; however I'm still unable to get /dev/sdi to list? Click the double arrows in the upper right on the UD page. Quote Link to comment
mostlybroken Posted February 9, 2022 Author Share Posted February 9, 2022 @dlandon - have refeshed disks, no change. On closer inspection; 'dev1' is perodically 'flickering' betweenn trying to mount /dev/sdi and /dev/sdj /sdi logs show an ID error: "emhttpd: device /dev/sdi problem getting id" Quote Link to comment
dlandon Posted February 9, 2022 Share Posted February 9, 2022 That disk has a problem and Linux is picking it up as different devices when it goes offline and back online. Is it connected usb or sata? Quote Link to comment
mostlybroken Posted February 9, 2022 Author Share Posted February 9, 2022 @dlandon - it is connected via SATA Quote Link to comment
dlandon Posted February 9, 2022 Share Posted February 9, 2022 Post your diagnostics zip and someone like @JorgeB may be able to help,. 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.