tistou77 Posted March 23, 2018 Share Posted March 23, 2018 Hello I have 2 Samsung NVMe SSDs (960 Pro and EVO)I noticed that it is the disc 1 (EVO) which is the 1st displayed in the list, and the disc 0 (Pro) in 2ndI have to reverse the disks and I have that Disk 0 : 960 Pro / Disk 1 : 960 EVO Disk 0 : 960 EVO / Disk 1 : 960 Pro It's not important, but it will be possible to have the disc 0 first, in the list Thanks Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 26, 2018 Share Posted March 26, 2018 The ordering is determined by the order in the list of physical drives. If you're unsure about why the ordering works the way it is on your system, please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Based on that dump we can provide you further details on the order of your SSDs. Thanks, Fiery Quote Link to comment Share on other sites More sharing options...
tistou77 Posted March 26, 2018 Author Share Posted March 26, 2018 It may be "read" from the device managerI noticed that it was reversed too In the SMART Dump, it's the EVO on disk 0 and the Pro on disk 1While with Diskpart, it's the Pro on disk 0Really weird Windows10 Thanks Quote Link to comment Share on other sites More sharing options...
tistou77 Posted March 26, 2018 Author Share Posted March 26, 2018 Weird, in physical drives, 960 Pro is first And in SMART, 960 EVO is first smartdump.txt Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 26, 2018 Share Posted March 26, 2018 Thank you. The problem is that due to the way drives are enumerated, AIDA64 needs to sort the list in an alphabetical order (although it's a bit more complicated than that, but let's gloss over the non-important part here). That makes your Evo drive appear in the list first. The alphabetical order is necessary for AIDA64 to properly filter out redundant entries in the list of drives. Quote Link to comment Share on other sites More sharing options...
tistou77 Posted March 26, 2018 Author Share Posted March 26, 2018 Ok it's by "alphabetical order " Thanks Quote Link to comment Share on other sites More sharing options...
tistou77 Posted May 9, 2018 Author Share Posted May 9, 2018 Hello Why is the Intel SSD "in the middle" of the 2 Samsung SSDs ? And would it be possible for Aida64 to read the "name" of the SSD from the "FriendlyName" registry key ? Like here Thanks Quote Link to comment Share on other sites More sharing options...
tistou77 Posted May 18, 2018 Author Share Posted May 18, 2018 On 26/03/2018 at 5:13 PM, Fiery said: Thank you. The problem is that due to the way drives are enumerated, AIDA64 needs to sort the list in an alphabetical order (although it's a bit more complicated than that, but let's gloss over the non-important part here). That makes your Evo drive appear in the list first. The alphabetical order is necessary for AIDA64 to properly filter out redundant entries in the list of drives. If it's in alphabetical order, why is it "indicated" in that order for the Intel ? In the SMART Dump, it's the Samsung on disk 0, yet it's Intel on disk 0 (Diskpart, Windows, device manager, etc ...)Just to understand, on what Aida64 is based Thanks Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 18, 2018 Share Posted May 18, 2018 6 hours ago, tistou77 said: If it's in alphabetical order, why is it "indicated" in that order for the Intel ? In the SMART Dump, it's the Samsung on disk 0, yet it's Intel on disk 0 (Diskpart, Windows, device manager, etc ...)Just to understand, on what Aida64 is based Thanks The order is alphabetical, but it has 3 groups, and the alphabetical order is only valid inside each group. 1) First group is the internally connected drives (IDE/ATA/SATA drives) that are not enumerated by the AIDA64 RAID module. Usually those are the regular drives that everyone's got. 2) The second group is the internally connected drives that are either part of a RAID array, or not picked up by direct enumeration but only by the RAID module. It's important to note that those drives are not necesserily part of a RAID array, and may not even be connected to a RAID controller. I know, it's weird 3) The final group is the external drives (FireWire, USB, eSATA, Thunderbolt, etc). If you post a current ATA Dump and SMART Dump, I can tell you more about the why's of the ordering. Quote And would it be possible for Aida64 to read the "name" of the SSD from the "FriendlyName" registry key ? Not really a good idea, since then the driver may override the otherwise more explanatory model ID with something useless. In your particular case (of the 280GB Optane 900P drive) it indeed would be useful though, but then again, it would be useful for many other SSDs that have no such "nice" model ID that can be understood by a glance, like for certain Samsung SSDs. Quote Link to comment Share on other sites More sharing options...
tistou77 Posted May 18, 2018 Author Share Posted May 18, 2018 2 hours ago, Fiery said: The order is alphabetical, but it has 3 groups, and the alphabetical order is only valid inside each group. 1) First group is the internally connected drives (IDE/ATA/SATA drives) that are not enumerated by the AIDA64 RAID module. Usually those are the regular drives that everyone's got. 2) The second group is the internally connected drives that are either part of a RAID array, or not picked up by direct enumeration but only by the RAID module. It's important to note that those drives are not necesserily part of a RAID array, and may not even be connected to a RAID controller. I know, it's weird 3) The final group is the external drives (FireWire, USB, eSATA, Thunderbolt, etc). If you post a current ATA Dump and SMART Dump, I can tell you more about the why's of the ordering. Ok thanks for the explanation,Here are the files, oddly it's the Samsung on disk 0, but for Diskpart, Device Manager, it's Intel on disk 0 atadump.txt smartdump.txt Quote Not really a good idea, since then the driver may override the otherwise more explanatory model ID with something useless. In your particular case (of the 280GB Optane 900P drive) it indeed would be useful though, but then again, it would be useful for many other SSDs that have no such "nice" model ID that can be understood by a glance, like for certain Samsung SSDs. Ok, so we go back to the customization of names (rename) probes, disks, etc ... in this menu So that everyone can do as he wants Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 18, 2018 Share Posted May 18, 2018 I'm sorry, I messed up the info on the alphabetical order. It is sorted, but since the drives are numbered with indexes, those indexes override the model ID of each drive. So if we gloss over the 3 groups issue (since your system only has drives in the first group), the order is the order that is dictated by the physical order of drives, as they are connected to their respective drive controllers, as well as the order of controllers. Since Windows may or may not enumerate drive controllers in the same order as AIDA64, only the order of drives connected to a particular drive controller should match between AIDA64 and Windows. Renaming of labels is available in OSD Panel, Desktop Gadget, SensorPanel, and external LCD modules. Quote Link to comment Share on other sites More sharing options...
tistou77 Posted May 21, 2018 Author Share Posted May 21, 2018 On 18/05/2018 at 7:19 PM, Fiery said: I'm sorry, I messed up the info on the alphabetical order. It is sorted, but since the drives are numbered with indexes, those indexes override the model ID of each drive. So if we gloss over the 3 groups issue (since your system only has drives in the first group), the order is the order that is dictated by the physical order of drives, as they are connected to their respective drive controllers, as well as the order of controllers. Since Windows may or may not enumerate drive controllers in the same order as AIDA64, only the order of drives connected to a particular drive controller should match between AIDA64 and Windows. Renaming of labels is available in OSD Panel, Desktop Gadget, SensorPanel, and external LCD modules. Ok thanks for the explanation, even though I did not really understand why the Intel drive is between the 2 Samsung drives Quote Link to comment Share on other sites More sharing options...
tistou77 Posted May 22, 2018 Author Share Posted May 22, 2018 On 5/18/2018 at 7:19 PM, Fiery said: Renaming of labels is available in OSD Panel, Desktop Gadget, SensorPanel, and external LCD modules. Yes, I know but I'll wait until you integrate the customization (renamed) the names of the probes, etc ... in this menu and then it's easy to integrate Quote Link to comment Share on other sites More sharing options...
Ellen Warren Posted November 26, 2018 Share Posted November 26, 2018 follow. Quote Link to comment Share on other sites More sharing options...
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.