The editor is only trying to make your question better.

1. "I am a lazy bum" this states that you are not willing to try reasonable solutions, and people will avoid trying to answer your question because of it.

2. Were these "Rules" part of a bounty you offered, and now are irrelevant to the question. Making suggestions that you perfer a Gui or terminal solution is a good thing, but making "rules" that bar answers is not a good thing. Possibally your question would be better suited in better explaining your situation.

Sample more friendly version of your question using the "rules" as part of your question.

"I have server with several disks, In opening my case I can see the labels of each of the drives (or if you can't see the labels with out removing them, say that- In a later comment I see you said this "but in my scenario the disks are crammed in a holder that blocks the sticker from view. The best I can do is trace the cables. " add that to the question!) I can where each of the SATA disks is plugged in to on the motherboard.

I want to know which hard disk drive corresponds to which device path (/dev/sda, /dev/sdb, etc). It's trivial to match the hard disk stats (brand, size) with the dev path, but I want more.

I want to know which drive is which inside my case. What's a good way to go about getting this info? Are there good Command line and Graphical interface tools?

So you see that with just a little bit of work we can make this a better question for everyone.

I fully support the edit that @Jacob Johan Edwards did.

The editor is only trying to make your question better.

1. "I am a lazy bum" this states that you are not willing to try reasonable solutions, and people will avoid trying to answer your question because of it.

2. Were these "Rules" part of a bounty you offered, and now are irrelevant to the question. Making suggestions that you perfer a Gui or terminal solution is a good thing, but making "rules" that bar answers is not a good thing. Possibally your question would be better suited in better explaining your situation.

Sample more friendly version of your question using the "rules" as part of your question.

"I have server with several disks, In opening my case I can see the labels of each of the drives (or if you can't see the labels with out removing them, say that- In a later comment I see you said this "but in my scenario the disks are crammed in a holder that blocks the sticker from view. The best I can do is trace the cables. " add that to the question!) I can where each of the SATA disks is plugged in to on the motherboard.

I want to know which hard disk drive corresponds to which device path (/dev/sda, /dev/sdb, etc). It's trivial to match the hard disk stats (brand, size) with the dev path, but I want more.

I want to know which drive is which inside my case. What's a good way to go about getting this info? Are there good Command line and Graphical interface tools?

So you see that with just a little bit of work we can make this a better question for everyone.

I fully support the edit that @Jacob Johan Edwards did.

Regardless, the "bonus" part should be removed as it is specific to the bounty and accepted answer which is now over.