On 04/20/2016 10:07 AM, Weiner, Michael wrote:
From: Rick Stevens
On 04/20/2016 09:32 AM, Weiner, Michael wrote:
I think the concept here is that you ADDED a controller to the system.
This can cause the system to enumerate the bus differently so your old, existing array may now be /dev/sda or /dev/sdc. This will happen regardless of
whether the new array was initialized or not--it's the order in which the bus was scanned for controllers.
Understood, I certainly wasn’t questioning the wisdom of the question or reasoning, it makes logical sense, unfortunately I am unable to remove the new controller at this point. I will have to schedule an outage
I'm assuming you still have remote access to the computer. Try "cat
/proc/partitions" to see what drives the kernel sees. Then do "fdisk
-l" on each one to see if you can find your partitions.
This is also a very good reason to use labels or UUIDs to identify devices in your /etc/fstab rather than the /dev name as changing the hardware around is
almost guaranteed to change the /dev names and cause you untold grief.
Good point.
This is easy to fix if you do find the right partition. Use blkid to
get the UUID of the filesystem, then edit the fstab.
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
http://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx
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
