Device missing from mdadm raid, but it exists, and looks fine?How do I get mdadm to auto assemble my raid...
How do I interpret this "sky cover" chart?
Calculus II Professor will not accept my correct integral evaluation that uses a different method, should I bring this up further?
Official degrees of earth’s rotation per day
Brexit - No Deal Rejection
Why does Deadpool say "You're welcome, Canada," after shooting Ryan Reynolds in the end credits?
Current sense amp + op-amp buffer + ADC: Measuring down to 0 with single supply
What has been your most complicated TikZ drawing?
What is this large pipe coming out of my roof?
Employee lack of ownership
Replacing Windows 7 security updates with anti-virus?
How could a female member of a species produce eggs unto death?
Instead of Universal Basic Income, why not Universal Basic NEEDS?
2D counterpart of std::array in C++17
Does the statement `int val = (++i > ++j) ? ++i : ++j;` invoke undefined behavior?
Latest web browser compatible with Windows 98
When do we add an hyphen (-) to a complex adjective word?
Use of プラトニック in this sentence?
Why are there 40 737 Max planes in flight when they have been grounded as not airworthy?
Have researchers managed to "reverse time"? If so, what does that mean for physics?
Rules about breaking the rules. How do I do it well?
How to explain that I do not want to visit a country due to personal safety concern?
Who is our nearest planetary neighbor, on average?
Did CPM support custom hardware using device drivers?
What is IP squat space
Device missing from mdadm raid, but it exists, and looks fine?
How do I get mdadm to auto assemble my raid array?mdadm raid5 failure. set wrong drive to faulty by accidentMissing 2 Disk out of software RAID 5mdadm Stuck at rebuilding sparemdadm isn't rebuilding the arraymdadm: drive replacement shows up as spare and refuses to syncSoftware RAID 1 does not extend on two new additional drivesHow to fix my broken raid10 arraymdadm RAID6, recover 2 disk failure during reshapeJBOD Failed to assemble after middle device Failed
I have raid 5 over 4 devices: sda10 sdh10 sdi10 sdf10. All these devices are available, and smart doesn't show errors (sdf was, but i replaced it with new disk, resynced, but then current situation showed).
In /proc/mdstat the array looks:
md19 : inactive sdh10[2](S) sdi10[4](S) sdf10[5](S)
1171482624 blocks super 1.2
As you can see sda10 is missing. But, according to --query, it should be ok:
=# mdadm --query --examine /dev/sda10
/dev/sda10:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 9216999b:8dab944b:564530eb:4a61e078
Name : blob:19 (local to host blob)
Creation Time : Sat Jan 21 21:05:44 2017
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 780988416 (372.40 GiB 399.87 GB)
Array Size : 1171482624 (1117.21 GiB 1199.60 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=0 sectors
State : clean
Device UUID : 8fdf8a46:4a84989c:e20fb280:c38053ea
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Mar 15 01:09:45 2019
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : b72fe223 - correct
Events : 1848
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 0
Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
On another device in the array state looks different:
=# mdadm --query --examine /dev/sdh10
/dev/sdh10:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 9216999b:8dab944b:564530eb:4a61e078
Name : blob:19 (local to host blob)
Creation Time : Sat Jan 21 21:05:44 2017
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 780988416 (372.40 GiB 399.87 GB)
Array Size : 1171482624 (1117.21 GiB 1199.60 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=0 sectors
State : clean
Device UUID : a6b44214:e50eb531:dc76d0f6:867db6ec
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Mar 15 01:14:45 2019
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : 9284b6cb - correct
Events : 5956
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 2
Array State : ..AA ('A' == active, '.' == missing, 'R' == replacing)
I tried stopping the array, and assambling with --scan, or with manually providing device names, but to no avail.
I am sure, for 100%, that data on sda10, sdh10 and sdi10 is ok. sdf10 is new disk, so it can be resynced.
Is there any way I could repair this raid?
linux raid mdadm
asked 2 mins ago
eijezeeijeze
8317
add a comment |
I have raid 5 over 4 devices: sda10 sdh10 sdi10 sdf10. All these devices are available, and smart doesn't show errors (sdf was, but i replaced it with new disk, resynced, but then current situation showed).
In /proc/mdstat the array looks:
md19 : inactive sdh10[2](S) sdi10[4](S) sdf10[5](S)
1171482624 blocks super 1.2
As you can see sda10 is missing. But, according to --query, it should be ok:
=# mdadm --query --examine /dev/sda10
/dev/sda10:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 9216999b:8dab944b:564530eb:4a61e078
Name : blob:19 (local to host blob)
Creation Time : Sat Jan 21 21:05:44 2017
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 780988416 (372.40 GiB 399.87 GB)
Array Size : 1171482624 (1117.21 GiB 1199.60 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=0 sectors
State : clean
Device UUID : 8fdf8a46:4a84989c:e20fb280:c38053ea
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Mar 15 01:09:45 2019
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : b72fe223 - correct
Events : 1848
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 0
Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
On another device in the array state looks different:
=# mdadm --query --examine /dev/sdh10
/dev/sdh10:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 9216999b:8dab944b:564530eb:4a61e078
Name : blob:19 (local to host blob)
Creation Time : Sat Jan 21 21:05:44 2017
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 780988416 (372.40 GiB 399.87 GB)
Array Size : 1171482624 (1117.21 GiB 1199.60 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=0 sectors
State : clean
Device UUID : a6b44214:e50eb531:dc76d0f6:867db6ec
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Mar 15 01:14:45 2019
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : 9284b6cb - correct
Events : 5956
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 2
Array State : ..AA ('A' == active, '.' == missing, 'R' == replacing)
I tried stopping the array, and assambling with --scan, or with manually providing device names, but to no avail.
I am sure, for 100%, that data on sda10, sdh10 and sdi10 is ok. sdf10 is new disk, so it can be resynced.
Is there any way I could repair this raid?
linux raid mdadm
asked 2 mins ago
eijezeeijeze
8317
add a comment |
I have raid 5 over 4 devices: sda10 sdh10 sdi10 sdf10. All these devices are available, and smart doesn't show errors (sdf was, but i replaced it with new disk, resynced, but then current situation showed).
In /proc/mdstat the array looks:
md19 : inactive sdh10[2](S) sdi10[4](S) sdf10[5](S)
1171482624 blocks super 1.2
As you can see sda10 is missing. But, according to --query, it should be ok:
=# mdadm --query --examine /dev/sda10
/dev/sda10:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 9216999b:8dab944b:564530eb:4a61e078
Name : blob:19 (local to host blob)
Creation Time : Sat Jan 21 21:05:44 2017
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 780988416 (372.40 GiB 399.87 GB)
Array Size : 1171482624 (1117.21 GiB 1199.60 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=0 sectors
State : clean
Device UUID : 8fdf8a46:4a84989c:e20fb280:c38053ea
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Mar 15 01:09:45 2019
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : b72fe223 - correct
Events : 1848
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 0
Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
On another device in the array state looks different:
=# mdadm --query --examine /dev/sdh10
/dev/sdh10:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 9216999b:8dab944b:564530eb:4a61e078
Name : blob:19 (local to host blob)
Creation Time : Sat Jan 21 21:05:44 2017
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 780988416 (372.40 GiB 399.87 GB)
Array Size : 1171482624 (1117.21 GiB 1199.60 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=0 sectors
State : clean
Device UUID : a6b44214:e50eb531:dc76d0f6:867db6ec
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Mar 15 01:14:45 2019
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : 9284b6cb - correct
Events : 5956
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 2
Array State : ..AA ('A' == active, '.' == missing, 'R' == replacing)
I tried stopping the array, and assambling with --scan, or with manually providing device names, but to no avail.
I am sure, for 100%, that data on sda10, sdh10 and sdi10 is ok. sdf10 is new disk, so it can be resynced.
Is there any way I could repair this raid?
linux raid mdadm
asked 2 mins ago
eijezeeijeze
8317
I have raid 5 over 4 devices: sda10 sdh10 sdi10 sdf10. All these devices are available, and smart doesn't show errors (sdf was, but i replaced it with new disk, resynced, but then current situation showed).
In /proc/mdstat the array looks:
md19 : inactive sdh10[2](S) sdi10[4](S) sdf10[5](S)
1171482624 blocks super 1.2
As you can see sda10 is missing. But, according to --query, it should be ok:
=# mdadm --query --examine /dev/sda10
/dev/sda10:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 9216999b:8dab944b:564530eb:4a61e078
Name : blob:19 (local to host blob)
Creation Time : Sat Jan 21 21:05:44 2017
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 780988416 (372.40 GiB 399.87 GB)
Array Size : 1171482624 (1117.21 GiB 1199.60 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=0 sectors
State : clean
Device UUID : 8fdf8a46:4a84989c:e20fb280:c38053ea
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Mar 15 01:09:45 2019
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : b72fe223 - correct
Events : 1848
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 0
Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
On another device in the array state looks different:
=# mdadm --query --examine /dev/sdh10
/dev/sdh10:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 9216999b:8dab944b:564530eb:4a61e078
Name : blob:19 (local to host blob)
Creation Time : Sat Jan 21 21:05:44 2017
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 780988416 (372.40 GiB 399.87 GB)
Array Size : 1171482624 (1117.21 GiB 1199.60 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=0 sectors
State : clean
Device UUID : a6b44214:e50eb531:dc76d0f6:867db6ec
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Mar 15 01:14:45 2019
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : 9284b6cb - correct
Events : 5956
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 2
Array State : ..AA ('A' == active, '.' == missing, 'R' == replacing)
I tried stopping the array, and assambling with --scan, or with manually providing device names, but to no avail.
I am sure, for 100%, that data on sda10, sdh10 and sdi10 is ok. sdf10 is new disk, so it can be resynced.
Is there any way I could repair this raid?
linux raid mdadm
linux raid mdadm
asked 2 mins ago
eijezeeijeze
8317
asked 2 mins ago
eijezeeijeze
8317
asked 2 mins ago
eijezeeijeze
8317
asked 2 mins ago
eijezeeijeze
8317
asked 2 mins ago
eijezeeijeze
8317
8317
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fserverfault.com%2fquestions%2f958389%2fdevice-missing-from-mdadm-raid-but-it-exists-and-looks-fine%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f958389%2fdevice-missing-from-mdadm-raid-but-it-exists-and-looks-fine%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
