[GH-ISSUE #684] Disk Hardware Details move to Disks #2382

Open
opened 2026-03-14 03:47:01 +03:00 by kerem · 4 comments
Owner

Originally created by @Movingtarget818 on GitHub (Sep 2, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/684

Would love to have the disk information moved from "Hardware Details" to "Disks"

Handy when you have multiple drives located on the one device

See attachment.

diskdetails

Originally created by @Movingtarget818 on GitHub (Sep 2, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/684 Would love to have the disk information moved from "Hardware Details" to "Disks" Handy when you have multiple drives located on the one device See attachment. ![diskdetails](https://user-images.githubusercontent.com/89956127/131775854-82ff5159-afb5-4db7-81ce-45540456f2bc.png)
Author
Owner

@dinger1986 commented on GitHub (Sep 2, 2021):

I don't agree but up to the devs.

Disks are hardware and should be listed under that. The other side is for disk space. Separate things and more intuitive keeping them separate.

Up to the devs if they want to change it however.

<!-- gh-comment-id:911326714 --> @dinger1986 commented on GitHub (Sep 2, 2021): I don't agree but up to the devs. Disks are hardware and should be listed under that. The other side is for disk space. Separate things and more intuitive keeping them separate. Up to the devs if they want to change it however.
Author
Owner

@johnnyq commented on GitHub (Sep 2, 2021):

I agree with @dinger1986 because for example one disk can have many partitions. I think a good approach to this would be to flip it so manufacturer is on top and the drive partitions / letters below it.

<!-- gh-comment-id:911554805 --> @johnnyq commented on GitHub (Sep 2, 2021): I agree with @dinger1986 because for example one disk can have many partitions. I think a good approach to this would be to flip it so manufacturer is on top and the drive partitions / letters below it.
Author
Owner

@silversword411 commented on GitHub (Sep 2, 2021):

I think you'd get a hairball either way.

What about mirrored software arrays, or Storage Spaces. There's no consistency between disks and partitions.

Hardware is hardware. Disks are disks.

<!-- gh-comment-id:911611646 --> @silversword411 commented on GitHub (Sep 2, 2021): I think you'd get a hairball either way. What about mirrored software arrays, or Storage Spaces. There's no consistency between disks and partitions. Hardware is hardware. Disks are disks.
Author
Owner

@Movingtarget818 commented on GitHub (Sep 2, 2021):

I think a good approach to this would be to flip it so manufacturer is on top and the drive partitions / letters below it.

That could work, i didn't think of the whole "partition" side of it, but having a way of seeing what drives are associated with what disk (without going digging) would be handy

<!-- gh-comment-id:912105698 --> @Movingtarget818 commented on GitHub (Sep 2, 2021): > I think a good approach to this would be to flip it so manufacturer is on top and the drive partitions / letters below it. That could work, i didn't think of the whole "partition" side of it, but having a way of seeing what drives are associated with what disk (without going digging) would be handy
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tacticalrmm#2382
No description provided.