CentOS trying to mount non existant RAID array -> recovery modeAn existing mdadm RAID5 is not mounting, Either a problem drive or SuperblockHow to map a sata device name to a physical sata interface for RAID systemsCan I convert and deconvert a bache0 device to a standard block device and still read the filesystem?MDADM lists same device twice“DegradedArray event”Unable to mount raid 5 array (mdadm), with no drive errorsError setting up Raid 1 with mdadm at RaspberryPi 2Help with mdadm will not reassembleRebuilding mdadm RAID 5 array with multiple failed drivesrecover data from former RAID 1 drive
Is it possible to run Internet Explorer on OS X El Capitan?
What is a clear way to write a bar that has an extra beat?
Are astronomers waiting to see something in an image from a gravitational lens that they've already seen in an adjacent image?
Has there ever been an airliner design involving reducing generator load by installing solar panels?
Rock identification in KY
Why doesn't H₄O²⁺ exist?
If human space travel is limited by the G force vulnerability, is there a way to counter G forces?
Is it inappropriate for a student to attend their mentor's dissertation defense?
Alternative to sending password over mail?
Is it unprofessional to ask if a job posting on GlassDoor is real?
Unable to deploy metadata from Partner Developer scratch org because of extra fields
Why does Kotter return in Welcome Back Kotter?
Modeling an IP Address
What does "Puller Prush Person" mean?
Why do I get two different answers for this counting problem?
Cross compiling for RPi - error while loading shared libraries
How old can references or sources in a thesis be?
How to determine what difficulty is right for the game?
Do other languages have an "irreversible aspect"?
Today is the Center
Why can't we play rap on piano?
Do I have a twin with permutated remainders?
Horror movie about a virus at the prom; beginning and end are stylized as a cartoon
DC-DC converter from low voltage at high current, to high voltage at low current
CentOS trying to mount non existant RAID array -> recovery mode
An existing mdadm RAID5 is not mounting, Either a problem drive or SuperblockHow to map a sata device name to a physical sata interface for RAID systemsCan I convert and deconvert a bache0 device to a standard block device and still read the filesystem?MDADM lists same device twice“DegradedArray event”Unable to mount raid 5 array (mdadm), with no drive errorsError setting up Raid 1 with mdadm at RaspberryPi 2Help with mdadm will not reassembleRebuilding mdadm RAID 5 array with multiple failed drivesrecover data from former RAID 1 drive
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
My first try using RAID1 ended with CentOS not starting anymore - throwing me into Recovery mode. Luckily a test system
At first i set-up the raid1 which worked rather good. Later i noticed that my partitions are only 2.2TB of the available 3TB (yet using fdisk's default start/end sector - it didn't use the full HDD is this normal? edit: yes it is / using parted now)
After I noticed my thoughts were 'Yup just remove the RAID and start over again', but it seems like removing a raid is much heavier than creating one. This are just about the commands i used to delete it:
mdadm --stop /dev/md0
mdadm --zero-superblock /dev/sdb (which didn't work)
mdadm --zero-superblock /dev/sdc (also wasn't working)
mdadm --remove /dev/md0
umount /dev/md0
Then removed my entry in /etc/fstab. That was the moment i was thrown into Rescue (after reboot certainly) - so I deleted the partitions of the sdb and sdc too but it didn't change.
The errors from 'journalctl -xb' are saying:
Received SIGRTMIN+20 from PID 1694 (plymouthd)
Timed out waiting for device dev-md0.device.
Dependency failed for /data
Dependency failed for Local File Systems
Dependency failed for Mark the need to relabel after reboot.
Job rhel-autorelabel-mark.services/start failed with result 'dependency'.
Dependency failed for Migrate local SELinux policy changes from the old store structure to the new structure.
Job selinux-policy-migrate-local-changes@targeted.services/start failed with result 'dependency'.
Dependency failed for Relabel all filesystems, if necessary.
Can't understand why it's still trying to mount /dev/md0 to /data as i removed the fstab entry and the /dev/md0 device isn't available anymore.
Thanks!
centos mount raid mdadm system-recovery
asked Apr 19 '18 at 15:47
dahedahe
215
add a comment |
My first try using RAID1 ended with CentOS not starting anymore - throwing me into Recovery mode. Luckily a test system
At first i set-up the raid1 which worked rather good. Later i noticed that my partitions are only 2.2TB of the available 3TB (yet using fdisk's default start/end sector - it didn't use the full HDD is this normal? edit: yes it is / using parted now)
After I noticed my thoughts were 'Yup just remove the RAID and start over again', but it seems like removing a raid is much heavier than creating one. This are just about the commands i used to delete it:
mdadm --stop /dev/md0
mdadm --zero-superblock /dev/sdb (which didn't work)
mdadm --zero-superblock /dev/sdc (also wasn't working)
mdadm --remove /dev/md0
umount /dev/md0
Then removed my entry in /etc/fstab. That was the moment i was thrown into Rescue (after reboot certainly) - so I deleted the partitions of the sdb and sdc too but it didn't change.
The errors from 'journalctl -xb' are saying:
Received SIGRTMIN+20 from PID 1694 (plymouthd)
Timed out waiting for device dev-md0.device.
Dependency failed for /data
Dependency failed for Local File Systems
Dependency failed for Mark the need to relabel after reboot.
Job rhel-autorelabel-mark.services/start failed with result 'dependency'.
Dependency failed for Migrate local SELinux policy changes from the old store structure to the new structure.
Job selinux-policy-migrate-local-changes@targeted.services/start failed with result 'dependency'.
Dependency failed for Relabel all filesystems, if necessary.
Can't understand why it's still trying to mount /dev/md0 to /data as i removed the fstab entry and the /dev/md0 device isn't available anymore.
Thanks!
centos mount raid mdadm system-recovery
asked Apr 19 '18 at 15:47
dahedahe
215
Fixed: created partitions again with parted and recreated the RAID array. Still wouldn't know how to delete a raid, I think the main problem was that I'm missing the mdadm.conf file..
– dahe
Apr 19 '18 at 17:34
add a comment |
My first try using RAID1 ended with CentOS not starting anymore - throwing me into Recovery mode. Luckily a test system
At first i set-up the raid1 which worked rather good. Later i noticed that my partitions are only 2.2TB of the available 3TB (yet using fdisk's default start/end sector - it didn't use the full HDD is this normal? edit: yes it is / using parted now)
After I noticed my thoughts were 'Yup just remove the RAID and start over again', but it seems like removing a raid is much heavier than creating one. This are just about the commands i used to delete it:
mdadm --stop /dev/md0
mdadm --zero-superblock /dev/sdb (which didn't work)
mdadm --zero-superblock /dev/sdc (also wasn't working)
mdadm --remove /dev/md0
umount /dev/md0
Then removed my entry in /etc/fstab. That was the moment i was thrown into Rescue (after reboot certainly) - so I deleted the partitions of the sdb and sdc too but it didn't change.
The errors from 'journalctl -xb' are saying:
Received SIGRTMIN+20 from PID 1694 (plymouthd)
Timed out waiting for device dev-md0.device.
Dependency failed for /data
Dependency failed for Local File Systems
Dependency failed for Mark the need to relabel after reboot.
Job rhel-autorelabel-mark.services/start failed with result 'dependency'.
Dependency failed for Migrate local SELinux policy changes from the old store structure to the new structure.
Job selinux-policy-migrate-local-changes@targeted.services/start failed with result 'dependency'.
Dependency failed for Relabel all filesystems, if necessary.
Can't understand why it's still trying to mount /dev/md0 to /data as i removed the fstab entry and the /dev/md0 device isn't available anymore.
Thanks!
centos mount raid mdadm system-recovery
asked Apr 19 '18 at 15:47
dahedahe
215
My first try using RAID1 ended with CentOS not starting anymore - throwing me into Recovery mode. Luckily a test system
At first i set-up the raid1 which worked rather good. Later i noticed that my partitions are only 2.2TB of the available 3TB (yet using fdisk's default start/end sector - it didn't use the full HDD is this normal? edit: yes it is / using parted now)
After I noticed my thoughts were 'Yup just remove the RAID and start over again', but it seems like removing a raid is much heavier than creating one. This are just about the commands i used to delete it:
mdadm --stop /dev/md0
mdadm --zero-superblock /dev/sdb (which didn't work)
mdadm --zero-superblock /dev/sdc (also wasn't working)
mdadm --remove /dev/md0
umount /dev/md0
Then removed my entry in /etc/fstab. That was the moment i was thrown into Rescue (after reboot certainly) - so I deleted the partitions of the sdb and sdc too but it didn't change.
The errors from 'journalctl -xb' are saying:
Received SIGRTMIN+20 from PID 1694 (plymouthd)
Timed out waiting for device dev-md0.device.
Dependency failed for /data
Dependency failed for Local File Systems
Dependency failed for Mark the need to relabel after reboot.
Job rhel-autorelabel-mark.services/start failed with result 'dependency'.
Dependency failed for Migrate local SELinux policy changes from the old store structure to the new structure.
Job selinux-policy-migrate-local-changes@targeted.services/start failed with result 'dependency'.
Dependency failed for Relabel all filesystems, if necessary.
Can't understand why it's still trying to mount /dev/md0 to /data as i removed the fstab entry and the /dev/md0 device isn't available anymore.
Thanks!
centos mount raid mdadm system-recovery
centos mount raid mdadm system-recovery
asked Apr 19 '18 at 15:47
dahedahe
215
asked Apr 19 '18 at 15:47
dahedahe
215
edited Apr 19 '18 at 16:16
dahe
asked Apr 19 '18 at 15:47
dahedahe
215
asked Apr 19 '18 at 15:47
dahedahe
215
asked Apr 19 '18 at 15:47
dahedahe
215
215
Fixed: created partitions again with parted and recreated the RAID array. Still wouldn't know how to delete a raid, I think the main problem was that I'm missing the mdadm.conf file..
– dahe
Apr 19 '18 at 17:34
add a comment |
Fixed: created partitions again with parted and recreated the RAID array. Still wouldn't know how to delete a raid, I think the main problem was that I'm missing the mdadm.conf file..
– dahe
Apr 19 '18 at 17:34
Fixed: created partitions again with parted and recreated the RAID array. Still wouldn't know how to delete a raid, I think the main problem was that I'm missing the mdadm.conf file..
– dahe
Apr 19 '18 at 17:34
Fixed: created partitions again with parted and recreated the RAID array. Still wouldn't know how to delete a raid, I think the main problem was that I'm missing the mdadm.conf file..
– dahe
Apr 19 '18 at 17:34
add a comment |
1 Answer
1
active
oldest
votes
Actually I forgot to make the new filesystems with mkfs.extX /dev/sdcX, after using parted.. That's it.
Other Steps with mdadm and parted (if i need it again):
List your Block deviceslsblk
Start parted (instead of fdisk as its only capable of 2TB) in optimal mode for checking alignment errorsparted -a optimal /dev/sdX
Create GPT partition (for more than 2tb again) mklabel gpt
Partitionmkpart1ext22048s-1 // don't use full space..set 1 raid on
Create Array:mdadm --create /dev/md/0 --level=mirror --raid-devices=2 /dev/sdb1 /dev/sdc1yes
Un/Mounting RAID:mount /dev/md0 /data/umount /data/
OR add this to /etc/fstab/dev/md0 /data ext4 defaults 0 0
and then:mount -a
answered May 26 '18 at 13:24
dahedahe
215
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f438767%2fcentos-trying-to-mount-non-existant-raid-array-recovery-mode%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Actually I forgot to make the new filesystems with mkfs.extX /dev/sdcX, after using parted.. That's it.
Other Steps with mdadm and parted (if i need it again):
List your Block deviceslsblk
Start parted (instead of fdisk as its only capable of 2TB) in optimal mode for checking alignment errorsparted -a optimal /dev/sdX
Create GPT partition (for more than 2tb again) mklabel gpt
Partitionmkpart1ext22048s-1 // don't use full space..set 1 raid on
Create Array:mdadm --create /dev/md/0 --level=mirror --raid-devices=2 /dev/sdb1 /dev/sdc1yes
Un/Mounting RAID:mount /dev/md0 /data/umount /data/
OR add this to /etc/fstab/dev/md0 /data ext4 defaults 0 0
and then:mount -a
answered May 26 '18 at 13:24
dahedahe
215
add a comment |
Actually I forgot to make the new filesystems with mkfs.extX /dev/sdcX, after using parted.. That's it.
Other Steps with mdadm and parted (if i need it again):
List your Block deviceslsblk
Start parted (instead of fdisk as its only capable of 2TB) in optimal mode for checking alignment errorsparted -a optimal /dev/sdX
Create GPT partition (for more than 2tb again) mklabel gpt
Partitionmkpart1ext22048s-1 // don't use full space..set 1 raid on
Create Array:mdadm --create /dev/md/0 --level=mirror --raid-devices=2 /dev/sdb1 /dev/sdc1yes
Un/Mounting RAID:mount /dev/md0 /data/umount /data/
OR add this to /etc/fstab/dev/md0 /data ext4 defaults 0 0
and then:mount -a
answered May 26 '18 at 13:24
dahedahe
215
add a comment |
Actually I forgot to make the new filesystems with mkfs.extX /dev/sdcX, after using parted.. That's it.
Other Steps with mdadm and parted (if i need it again):
List your Block deviceslsblk
Start parted (instead of fdisk as its only capable of 2TB) in optimal mode for checking alignment errorsparted -a optimal /dev/sdX
Create GPT partition (for more than 2tb again) mklabel gpt
Partitionmkpart1ext22048s-1 // don't use full space..set 1 raid on
Create Array:mdadm --create /dev/md/0 --level=mirror --raid-devices=2 /dev/sdb1 /dev/sdc1yes
Un/Mounting RAID:mount /dev/md0 /data/umount /data/
OR add this to /etc/fstab/dev/md0 /data ext4 defaults 0 0
and then:mount -a
answered May 26 '18 at 13:24
dahedahe
215
Actually I forgot to make the new filesystems with mkfs.extX /dev/sdcX, after using parted.. That's it.
Other Steps with mdadm and parted (if i need it again):
List your Block deviceslsblk
Start parted (instead of fdisk as its only capable of 2TB) in optimal mode for checking alignment errorsparted -a optimal /dev/sdX
Create GPT partition (for more than 2tb again) mklabel gpt
Partitionmkpart1ext22048s-1 // don't use full space..set 1 raid on
Create Array:mdadm --create /dev/md/0 --level=mirror --raid-devices=2 /dev/sdb1 /dev/sdc1yes
Un/Mounting RAID:mount /dev/md0 /data/umount /data/
OR add this to /etc/fstab/dev/md0 /data ext4 defaults 0 0
and then:mount -a
answered May 26 '18 at 13:24
dahedahe
215
edited 2 days ago
answered May 26 '18 at 13:24
dahedahe
215
answered May 26 '18 at 13:24
dahedahe
215
answered May 26 '18 at 13:24
dahedahe
215
215
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f438767%2fcentos-trying-to-mount-non-existant-raid-array-recovery-mode%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Fixed: created partitions again with parted and recreated the RAID array. Still wouldn't know how to delete a raid, I think the main problem was that I'm missing the mdadm.conf file..
– dahe
Apr 19 '18 at 17:34