Hi all, I have several machines in my lab, all of them running Fedora. Some of the have both SSD and non SSD drivers. Since the setup is dynamic (sometimes I transfer disks from machine to machine), there are cases that the SSD drive is one machine is disconnected/moved to a different machine, and the boot is done from the other non SSD driver (on which also Fedora is installed).
Is there a way to know whether to boot was done from SSD or not ? (I know I can try to read the product name of the device from which boot was done, but in many cases this is not enough to know straight away whether it is SSD or not.
Regards, Kevin
is not
On 08/31/2016 11:51 PM, Kevin Wilson wrote:
Is there a way to know whether to boot was done from SSD or not ? (I know I can try to read the product name of the device from which boot was done, but in many cases this is not enough to know straight away whether it is SSD or not.
Why not simply record the UUID of the boot device?
On 01/09/16 14:51, Kevin Wilson wrote:
Is there a way to know whether to boot was done from SSD or not ? (I know I can try to read the product name of the device from which boot was done, but in many cases this is not enough to know straight away whether it is SSD or not.
cat /sys/block/sdX/queue/rotational
1 = Spinning Disk 0 = SSD
Unless you're crudely assuming sda is your boot disk, you'll need to figure that out, but that's not too hard.
You could change the desktop for each system ;) low tech but effective in knowing which system you are on.
On Thu, Sep 1, 2016 at 6:23 AM, Ian Chapman packages@amiga-hardware.com wrote:
On 01/09/16 14:51, Kevin Wilson wrote:
Is there a way to know whether to boot was done from SSD or not ?
(I know I can try to read the product name of the device from which boot was done, but in many cases this is not enough to know straight away whether it is SSD or not.
cat /sys/block/sdX/queue/rotational
1 = Spinning Disk 0 = SSD
Unless you're crudely assuming sda is your boot disk, you'll need to figure that out, but that's not too hard.
-- Ian Chapman.
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 09/01/2016 04:58 AM, fred roller wrote:
You could change the desktop for each system ;) low tech but effective in knowing which system you are on.
On Thu, Sep 1, 2016 at 6:23 AM, Ian Chapman <packages@amiga-hardware.com mailto:packages@amiga-hardware.com> wrote:
On 01/09/16 14:51, Kevin Wilson wrote: Is there a way to know whether to boot was done from SSD or not ? (I know I can try to read the product name of the device from which boot was done, but in many cases this is not enough to know straight away whether it is SSD or not. cat /sys/block/sdX/queue/rotational 1 = Spinning Disk 0 = SSD Unless you're crudely assuming sda is your boot disk, you'll need to figure that out, but that's not too hard. -- Ian Chapman. -- users mailing list users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org <https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct <http://fedoraproject.org/code-of-conduct> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines <http://fedoraproject.org/wiki/Mailing_list_guidelines> Have a question? Ask away: http://ask.fedoraproject.org-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
try running fstrim -av on a spinning vs ssd system
I do use separate pictures in each desktop for ease of identification.
It would probably be helpful to use partitian names.
[note: uuid's scrambled for security] -------------------------------------------- so here is a simple way to find the disk in use and it's unambiguous UUID
tod@tod-1204:~$ mount <<<<<< The Command /dev/sdb1 on / type ext4 (rw,errors=remount-ro) <<<<<< The line I wanted to see! proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) gvfs-fuse-daemon on /home/tod/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=tod) tod@tod-1204:~$ ls -l /dev/disk/by-uuid <<<<<< The next command total 0 lrwxrwxrwx 1 root root 10 Sep 1 00:55 05cdfa19-c951-422b-be66-9871958f83ba -> ../../sdb9 lrwxrwxrwx 1 root root 10 Sep 1 00:55 0cc413fe-7bb2-4ff4-9fdb-b6b7767c55b1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 Sep 1 00:55 26cbcb32-de2d-457c-9dce-de56a12e0c6d -> ../../sdb6 lrwxrwxrwx 1 root root 11 Sep 1 00:55 39bbcc4b-2f15-4e70-b09c-badc03e44e21 -> ../../sdb10 lrwxrwxrwx 1 root root 11 Sep 1 00:55 3cbaf86e-d6fd-4498-b446-1661aaf4364d -> ../../sdb13 lrwxrwxrwx 1 root root 10 Sep 1 00:55 486779e8-c99b-4900-b0b4-f735ee4d88e9 -> ../../sda1 lrwxrwxrwx 1 root root 10 Sep 1 00:55 6499a8e5-b6b4-5683-9135-4146728d7102 -> ../../sdb5 lrwxrwxrwx 1 root root 11 Sep 1 00:55 654bae5d-9440-4a44-a211-eb163336919c -> ../../sdb15 lrwxrwxrwx 1 root root 10 Sep 1 00:55 65eafd02-9a26-4355-817a-c29f97dd11cb -> ../../sdb2 lrwxrwxrwx 1 root root 10 Sep 1 00:55 89bad1f1-475d-4788-ae7e-b46c4a6b8479 -> ../../sdb1 << it's UUID!!! lrwxrwxrwx 1 root root 11 Sep 1 00:55 a35899e2-bc3e-49dd-80f6-35f315cc426f -> ../../sdb11 lrwxrwxrwx 1 root root 11 Sep 1 00:55 a53bb68d-bd94-4955-9bf5-e38ef218c1fa -> ../../sdb14 lrwxrwxrwx 1 root root 10 Sep 1 00:55 ab568d75-3b9a-426a-b566-a61db8526a05 -> ../../sdb7 lrwxrwxrwx 1 root root 10 Sep 1 00:55 ae80baf7-6429-4932-91bf-c8ea269363ba -> ../../sdc2 lrwxrwxrwx 1 root root 10 Sep 1 00:55 CDF9-4CD0 -> ../../sdb8 lrwxrwxrwx 1 root root 11 Sep 1 00:55 BF99-21F0 -> ../../sdb12 lrwxrwxrwx 1 root root 10 Sep 1 00:55 BECCFE7C9CFE2F11 -> ../../sdd1 lrwxrwxrwx 1 root root 10 Sep 1 00:55 eef36365-3989-49c7-8e43-94bf03799a3c -> ../../sdb4 ---------------------------------------
But I think you are asking "where did I boot from?" which can be a very interesting thing to find. I cannot think of any fingerprints left by the loader other than perhaps "boot-once" from grub. Perhaps you can add a command in through a section of grub whereby you can talk to a file so you could query it.
See "README" in /etc/grub.d
On Wed, Aug 31, 2016 at 11:51 PM, Kevin Wilson wkevils@gmail.com wrote:
Hi all, I have several machines in my lab, all of them running Fedora. Some of the have both SSD and non SSD drivers. Since the setup is dynamic (sometimes I transfer disks from machine to machine), there are cases that the SSD drive is one machine is disconnected/moved to a different machine, and the boot is done from the other non SSD driver (on which also Fedora is installed).
Is there a way to know whether to boot was done from SSD or not ? (I know I can try to read the product name of the device from which boot was done, but in many cases this is not enough to know straight away whether it is SSD or not.
Regards, Kevin
is not
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
I have a similar setup at home. I have a dozen or so boot drives with various OSes on them that I can throw into my primary server. Mostly Linux Distros, BSD and a single Windows SSD for gaming (yeah, I know...). In my case I have a couple of non-SSD drives in this server that are data only. That way, I know which drive is the boot drive.
What I don't get is why you would have such a setup in your lab. It seems to be way more complicated than it needs to be. Granted, I have no idea what your lab is for, but I'd never have movable boot drive and a static one in the same system.
However, if I did, I'd make the hostnames unique. To me that would be simpler than mucking the UUIDs of the drives.
On Thu, Sep 1, 2016 at 2:51 AM, Kevin Wilson wkevils@gmail.com wrote:
Hi all, I have several machines in my lab, all of them running Fedora. Some of the have both SSD and non SSD drivers. Since the setup is dynamic (sometimes I transfer disks from machine to machine), there are cases that the SSD drive is one machine is disconnected/moved to a different machine, and the boot is done from the other non SSD driver (on which also Fedora is installed).
Is there a way to know whether to boot was done from SSD or not ? (I know I can try to read the product name of the device from which boot was done, but in many cases this is not enough to know straight away whether it is SSD or not.
Regards, Kevin
is not
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Also consider the physical aspect of the MB's priority detection....
sata1-4 is first in sequence followed by USB 1-* when Linux and/or bios puts everything together. So, any spinner disk or ssd in sata 1 slot will be detected as sda, sata 2 slot as sdb, etc /then/ any usb gets picked up in sequence to continue the lettering scheme. Always has when I was tracking which drive the systems where using. In this case if no usb drive is attached then note which slot you have the hdd plugged into, noted on the print on the MB, and this should lead you to the scheme in system /then/ where ever grub is pointed to is your device; typically sda if a solo drive install.
On Fri, Sep 2, 2016 at 6:53 AM, Mark Haney mark.haney@vifprogram.com wrote:
I have a similar setup at home. I have a dozen or so boot drives with various OSes on them that I can throw into my primary server. Mostly Linux Distros, BSD and a single Windows SSD for gaming (yeah, I know...). In my case I have a couple of non-SSD drives in this server that are data only. That way, I know which drive is the boot drive.
What I don't get is why you would have such a setup in your lab. It seems to be way more complicated than it needs to be. Granted, I have no idea what your lab is for, but I'd never have movable boot drive and a static one in the same system.
However, if I did, I'd make the hostnames unique. To me that would be simpler than mucking the UUIDs of the drives.
On Thu, Sep 1, 2016 at 2:51 AM, Kevin Wilson wkevils@gmail.com wrote:
Hi all, I have several machines in my lab, all of them running Fedora. Some of the have both SSD and non SSD drivers. Since the setup is dynamic (sometimes I transfer disks from machine to machine), there are cases that the SSD drive is one machine is disconnected/moved to a different machine, and the boot is done from the other non SSD driver (on which also Fedora is installed).
Is there a way to know whether to boot was done from SSD or not ? (I know I can try to read the product name of the device from which boot was done, but in many cases this is not enough to know straight away whether it is SSD or not.
Regards, Kevin
is not
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
--
Mark Haney ::: Senior Systems Engineer *VIF* *International Education* P.O. Box 3566 ::: Chapel Hill, N.C. 27515 ::: USA 919-265-5006 office
Global learning for all. www.viflearn.com Find VIF on Facebook http://facebook.com/VIFInternationalEducation | Twitter https://twitter.com/vifglobaled | LinkedIn http://www.linkedin.com/company/vif-international-education
Recognized as a ‘Best for the World’ http://bestfortheworld.bcorporation.net/ B Corp!
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
-
fred roller -
Ian Chapman -
Joe Zeff -
Joseph Loo -
Kevin Wilson -
Mark Haney -
Tod Merley