Recently I checked the ClearOS configuration and I noticed there were a heap of sdc errors and the level 5 RAID was degraded so I took out the HDD in bay 3 of my Microserver and replaced it with another one but that didn't help so I put it back how it was then replaced the HDD in bay 2 with another one and that didn't work either so I put it back how it was originally and hooked it up to a monitor and now when I try to boot I get a message saying:
"ClearOS 7 (Final) dracut-033-360.el7_2 (initramfs)[ 158.163086 BUG: unable to handle kernel NULL pointer dereference at 00000000000002e8
<and some other stuff that is harder to make out as the bottom half is cut off>"
Is it possible to do a recovery? If I have to start all over again what is the point of using RAID? How does one avoid this problem?
Thanks.
"ClearOS 7 (Final) dracut-033-360.el7_2 (initramfs)[ 158.163086 BUG: unable to handle kernel NULL pointer dereference at 00000000000002e8
<and some other stuff that is harder to make out as the bottom half is cut off>"
Is it possible to do a recovery? If I have to start all over again what is the point of using RAID? How does one avoid this problem?
Thanks.
Share this post:
Responses (7)
-
Accepted Answer
What logic did you use to determine which disk to pull? Your append seems to indicate they were selected at random (try one, then another - that's not good as you mess up the last access times and further degrade the array...)
To really know which disk is which, just before powering down, simplest is to run "smartctl -a /dev/sdx | grep Serial" - where sdx is the disk in question. then check the disks for that serial number... alternatively "hdparm -I /dev/sdx | grep 'Serial\ Number' " will also provide the same information.
Note that swapping disks may change the way linux enumerates the disk logical numbers, and understand that the disk number and "RaidDevice" numbers in the output from mdadm bear no direct relationship with physical slots or bays.
Do we assume from your error that the system is no longer bootable? If so, you will need to boot a live linux system on CD, DVD, SD card or USB drive to find out the state of your raid array - impossible to know from the information rovided whether it can be salvaged...
Raid has saved data here several times - but you need to understand totally what you are doing, not panic, and ask questions first before touching anything if not 100% sure... -
Accepted Answer
You removed /sdc, why do you say it didn't help? You need to partition as raid, and then insert with raid utility
By removing the other drive you broke your raid array and now it will not automatically reassemble. It is possible to reassemble the array with a missing drive and use the force switch with the raid utilities.
I've learned to save my raid configuration to a file with all the serial numbers, and yes that was the hard way! -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
[root@server ~]# yum whatprovides hdparm
Loaded plugins: clearcenter-marketplace, fastestmirror
ClearCenter Marketplace: fetching repositories...
Loading mirror speeds from cached hostfile
* clearos: mirror2.timburgess.net
* clearos-addons: mirror2.timburgess.net
* clearos-centos: download2.clearsdn.com
* clearos-centos-updates: download2.clearsdn.com
* clearos-extras: mirror2.timburgess.net
* clearos-fast-updates: download2.clearsdn.com
* clearos-updates: mirror2.timburgess.net
* contribs: download2.clearsdn.com
* private-clearcenter-dyndns: download3.clearsdn.com:80
* private-clearcenter-plex: download4.clearsdn.com:80
* private-clearcenter-roundcubemail: download2.clearsdn.com:80
* private-clearcenter-smart-monitor: download2.clearsdn.com:80
* private-clearcenter-static-vpn: download1.clearsdn.com:80
hdparm-9.43-4.el6.x86_64 : A utility for displaying and/or setting hard disk
: parameters
Repo : clearos
Matched from:
hdparm-9.43-4.el6.x86_64 : A utility for displaying and/or setting hard disk
: parameters
Repo : clearos
Matched from:
hdparm-9.43-4.el6.x86_64 : A utility for displaying and/or setting hard disk
: parameters
Repo : clearos-centos
Matched from:
hdparm-9.43-4.el6.x86_64 : A utility for displaying and/or setting hard disk
: parameters
Repo : installed
Matched from:
Other : Provides-match: hdparm
[root@server ~]# yum whatprovides */smartctl
Loaded plugins: clearcenter-marketplace, fastestmirror
ClearCenter Marketplace: fetching repositories...
Loading mirror speeds from cached hostfile
* clearos: mirror2.timburgess.net
* clearos-addons: mirror2.timburgess.net
* clearos-centos: download2.clearsdn.com
* clearos-centos-updates: download2.clearsdn.com
* clearos-extras: mirror2.timburgess.net
* clearos-fast-updates: download2.clearsdn.com
* clearos-updates: mirror2.timburgess.net
* contribs: download2.clearsdn.com
* private-clearcenter-dyndns: download4.clearsdn.com:80
* private-clearcenter-plex: download4.clearsdn.com:80
* private-clearcenter-roundcubemail: download2.clearsdn.com:80
* private-clearcenter-smart-monitor: download2.clearsdn.com:80
* private-clearcenter-static-vpn: download1.clearsdn.com:80
clearos/filelists_db | 1.0 MB 00:00
clearos-addons/filelists_db | 72 kB 00:00
clearos-centos/filelists_db | 6.3 MB 00:19
clearos-centos-updates/filelists_db | 5.3 MB 00:14
clearos-extras/filelists_db | 122 kB 00:00
clearos-fast-updates/filelists_db | 1.3 kB 00:00
clearos-updates/filelists_db | 409 kB 00:00
1:smartmontools-5.43-1.el6.x86_64 : Tools for monitoring SMART capable hard
: disks
Repo : clearos-centos
Matched from:
Filename : /usr/sbin/smartctl
1:smartmontools-5.43-1.el6.x86_64 : Tools for monitoring SMART capable hard
: disks
Repo : clearos-extras
Matched from:
Filename : /usr/sbin/smartctl
1:smartmontools-5.43-1.el6.x86_64 : Tools for monitoring SMART capable hard
: disks
Repo : installed
Matched from:
Filename : /usr/sbin/smartctl
So:yum install hdparm smartmontools
-
Accepted Answer
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »