search for: persistent_block_device_nam

Nicolas Kovacs wrote: > Le 28/02/2019 ? 04:12, Jobst Schmalenbach a ?crit?: > >> I want to lock in the SDA/SDB/SDC for my drives > > In short : use UUIDs or labels instead of hardcoding /dev/sdX. > > https://wiki.archlinux.org/index.php/persistent_block_device_naming Yeah - I strongly believe in labels, given the fact that *no* one can remember a UUID.... mark

Hi I have read instructions for udev, I also found many example on how to do this. I want to lock in the SDA/SDB/SDC for my drives and I came up with a rule like this KERNEL=="sd?", SUBSYSTEM=="block", ENV{ID_SERIAL}=="ST500DM002-1BC142_W2A56H8A", NAME="sda", RUN+="/usr/bin/logger ID_SERIAL=$ENV{ID_SERIAL} set to /dev/sda ",

Le 28/02/2019 ? 04:12, Jobst Schmalenbach a ?crit?: > I want to lock in the SDA/SDB/SDC for my drives In short : use UUIDs or labels instead of hardcoding /dev/sdX. https://wiki.archlinux.org/index.php/persistent_block_device_naming Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32

...gt; Nicolas Kovacs wrote: > > Le 28/02/2019 ? 04:12, Jobst Schmalenbach a ?crit : > > > >> I want to lock in the SDA/SDB/SDC for my drives > > > > In short : use UUIDs or labels instead of hardcoding /dev/sdX. > > > > https://wiki.archlinux.org/index.php/persistent_block_device_naming > > Yeah - I strongly believe in labels, given the fact that *no* one can > remember a UUID.... > > mark > ls -l /dev/disk/by-uuid (copy) (paste) -- *Matt Phelps* *Information Technology Specialist, Systems Administrator* (Computation Facility, Smithsonian Astro...

...as Kovacs wrote: >>> Le 28/02/2019 ? 04:12, Jobst Schmalenbach a ?crit : >>>> I want to lock in the SDA/SDB/SDC for my drives >>> >>> In short : use UUIDs or labels instead of hardcoding /dev/sdX. >>> >>> https://wiki.archlinux.org/index.php/persistent_block_device_naming >> >> Yeah - I strongly believe in labels, given the fact that *no* one can >> remember a UUID.... > > ls -l /dev/disk/by-uuid > (copy) > (paste) That is, of course, assuming you have a running system, that you haven't replaced a hard drive, an MDraid's not...

>> #1. Map the physical drive slots to how they show up in FBSD so if a >> disk is removed and the machine is rebooted all the disks after that >> removed one do not have an 'off by one error'. i.e. if you have >> ada0-ada14 and remove ada8 then reboot - normally FBSD skips that >> missing ada8 drive and the next drive (that used to be ada9) is now