RE: Cant read superblocks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: Samuel Sieb [mailto:samuel@xxxxxxxx] 

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.

[root@raos_apps01 ~]# cat /proc/partitions
major minor  #blocks  name

   8     0  976224256 sda
   8     1     104391 sda1
   8     2  976117432 sda2
   8    16 14643363840 sdb
   8    17 14643362847 sdb1
   8    32 42971168768 sdc
   8    33 42971167775 sdc1
 253     0  841973760 dm-0
 253     1  134119424 dm-1

>> 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.

Thanks!

===================================


 Please consider the environment before printing this e-mail

Cleveland Clinic is ranked as one of the top hospitals in America by U.S.News & World Report (2015).  
Visit us online at http://www.clevelandclinic.org for a complete listing of our services, staff and locations.


Confidentiality Note:  This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law.  If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.  If you have received this communication in error,  please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy.  

Thank you.
--
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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux