mostlybroken

@dlandon - it is connected via SATA

@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"

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?

ah - can I move the post, or?

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:

Bump Sent from my SM-G975F using Tapatalk

Hi all, since upgrading to 6.9.0 - I've noticed that my CPU was constantly spiking cores to 100% every few seconds. in the logs, I could see the following being logged every few seconds, tying up with CPU spikes....: Mar 8 14:22:07 Concorde kernel: sdf: sdf1 Mar 8 14:22:07 Concorde kernel: sdg: sdg1 Mar 8 14:22:07 Concorde kernel: sdc: sdc1 Mar 8 14:22:07 Concorde kernel: sdd: sdd1 Mar 8 14:22:07 Concorde kernel: sde: sde1 Mar 8 14:22:07 Concorde kernel: sdh: sdh1 I run a HP DL380P Gen 8 server (RAID/HBA controller is a P420i in HBA mode), and therefore was using the HP cciss SMART controller type. I disabled this (changed disk index's so nothing would be seen) and just like that, the CPU was back to idling at 1% like normal. Is this behaviour expected? - is there anything I could do to reduce CPU usage, reduce polling rate perhaps? Many Thanks

Have been following this with interest. I primarily use SAS disks in my system due to a very affordable source! *touchingwood* also the long term 24/7 reliability of these drives to date has been fantastic - I've got drives which have been in constant operation for 5 years in a production environment before I put them into my unraid server and ran them for another 2 years so far - however with the age of them and the massive waste of power, I am very keen to find a solution to spinning them down!