Re: Cant read superblocks

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

 



On Wed, Apr 20, 2016 at 6:33 AM, Weiner, Michael <weinerm@xxxxxxx> wrote:
> I have a Dell PowerEdge R910 with a PERC 700 controller that has a virtual drive configured as a RAID 5 with 15 disks in it. We're running CentOS 5.10 at the moment, and I created a 15Tb ext3 filesystem on that RAID group (set this up a few years back) that has been running fine up until yesterday. I had the opportunity to add another PERC H810 controller along with a PowerVault MD1200 to add more space (44Tb as XFS), but when we went to turn the server back on, we noticed one of the disks in the RAID group had apparently failed. I didn't think much of it at the time, as it was a RAID 5, but when the server came up and I tried to mount it, I received the following error:
>
> mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
>        missing codepage or other error
>        In some cases useful info is found in syslog - try
>        dmesg | tail  or so
>
> I tried to get a listing of backup superblocks by doing the following:
>
> [root@raos_apps01 ~]# mke2fs -b 8192 -n /dev/sdb1
> Warning: blocksize 8192 not usable on most systems.
> mke2fs 1.39 (29-May-2006)
> mke2fs: 8192-byte blocks too big for system (max 4096)
> Proceed anyway? (y,n) y
> Warning: 8192-byte blocks too big for system (max 4096), forced to continue


Why are you ignoring these warnings as if they aren't relevant? 8K
block size isn't valid on x86.



>
> [root@raos_apps01 ~]# e2fsck -b 65528 /dev/sdb1

64K block size is not valid on x86.


> any idea how I can get the FS back? I ordered another drive to replace the failed on thinking that *might* be part of the problem, so I will have to wait and see on that, but I SHOULD be able to mount it, but I am not able to.

Chances are the block size is either 1K or 4K. That's the problem.




-- 
Chris Murphy
--
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