Ubuntu - HDD error fsck died with exit status 4
I have not Ubuntu experience.
on boot I get:
/dev/sda1 clean
fsck 1.40.8
/dev/md0 contains a file system with errors, check forced
Duplicate or bad block in use!
/dev/md0: Multiply-claimed block(s) in inode 8: 24576
/dev/md0: Multiply-claimed block(s) in inode 4981200: 24576
/dev/md0: Unexpected inconsistency; run fsck Manually
fsck died with exit status 4
RAID1 (software)
I have cloned the drive and it is bootable.
What steps should I take to repair this error, assuming the drives are ok.
I am testing that now.
on boot I get:
/dev/sda1 clean
fsck 1.40.8
/dev/md0 contains a file system with errors, check forced
Duplicate or bad block in use!
/dev/md0: Multiply-claimed block(s) in inode 8: 24576
/dev/md0: Multiply-claimed block(s) in inode 4981200: 24576
/dev/md0: Unexpected inconsistency; run fsck Manually
fsck died with exit status 4
RAID1 (software)
I have cloned the drive and it is bootable.
What steps should I take to repair this error, assuming the drives are ok.
I am testing that now.
Boot your system with Live CD and run the fsck, It should fix your issue.
ASKER
Does that handle RAID, or do I need to break it first?
Boot up with one disk only first with LiveCD first.
fix disk and boot with another one to repeat the same thing.
fix disk and boot with another one to repeat the same thing.
I never tried over software RAID, but you can boot and check, wheter the volume is accessable or not.
If not then you have to breack it.
As per my views the RAID valume would not be accessible directly, It should require some additional settings to get accessible.
If not then you have to breack it.
As per my views the RAID valume would not be accessible directly, It should require some additional settings to get accessible.
ASKER
I ran these
df -h
/dev/sda1 19g 749 used 17g available
/dev/md0 128g 27g used 95g available
cat /proc/mdstat
md0 : active raid1 sdb3[1] 134801344 blocks [2/1] [_u]
does this mean that the raid is already broken?
If yes, does the [-u] point to it being drive0 that is the problem and not drive1?
df -h
/dev/sda1 19g 749 used 17g available
/dev/md0 128g 27g used 95g available
cat /proc/mdstat
md0 : active raid1 sdb3[1] 134801344 blocks [2/1] [_u]
does this mean that the raid is already broken?
If yes, does the [-u] point to it being drive0 that is the problem and not drive1?
As per the given output still raid is active.
Below given URL will give you idea about how to modify the RAID.
http://www.ogre.com/node/349
Below given URL will give you idea about how to modify the RAID.
http://www.ogre.com/node/349
> does this mean that the raid is already broken?
With software raid, you can boot up with single disk.
Why you need to spend time to break it up and add it back?
shut down the machine, disable the second disk from bios, the boot with LiveCD the do fsck.
Then boot up with single disk to see if everything ok.
Repeat with the same on the other disk.
With software raid, you can boot up with single disk.
Why you need to spend time to break it up and add it back?
shut down the machine, disable the second disk from bios, the boot with LiveCD the do fsck.
Then boot up with single disk to see if everything ok.
Repeat with the same on the other disk.
ASKER
ok,
Drive0 had been repaired.
Drive1 will not
What are the procedures for replacing the existing 160GB? I only have a 320GB.
Now I get:
I ran these
df -h
/dev/sda1 19g 750 used 17g available
/dev/md0 128g 27g used 95g available
cat /proc/mdstat
md0 : active raid1 sdb3[0] 134801344 blocks [2/1] [U_]
Drive0 had been repaired.
Drive1 will not
What are the procedures for replacing the existing 160GB? I only have a 320GB.
Now I get:
I ran these
df -h
/dev/sda1 19g 750 used 17g available
/dev/md0 128g 27g used 95g available
cat /proc/mdstat
md0 : active raid1 sdb3[0] 134801344 blocks [2/1] [U_]
ASKER
when trying to enter rescue mode I get:
No usable shell was found on your root file system
No usable shell was found on your root file system
ASKER
Drive1 tests ok
Can I clone it from Drive0 and boot?
Will the RAID still work if I do this?
Can I clone it from Drive0 and boot?
Will the RAID still work if I do this?
> Can I clone it from Drive0 and boot?
Yes, you can clone from Drive0 to Drive1.
Use the following method to add back to RAID.
http://www.howtoforge.com/replacing_hard_disks_in_a_raid1_array
Yes, you can clone from Drive0 to Drive1.
Use the following method to add back to RAID.
http://www.howtoforge.com/replacing_hard_disks_in_a_raid1_array
ASKER
I am still unsure of exactly what to do. Based on:
With both drives in:
cat /proc/mdstat
md0 : active raid1 sdb3[1] 134801344 blocks [2/1] [_u]
With just DRIVE0 in:
cat /proc/mdstat
md0 : active raid1 sdb3[0] 134801344 blocks [2/1] [U_]
What is this telling me?
what is the difference between sdb3[1] and sdb3[0]?
with both drives, shouldn't it have listed both
what is the difference between [_u] and [U_]
is a u versus a U significant?
does [U_] mean drive0
and
[_u] mean drive1
With both drives in:
cat /proc/mdstat
md0 : active raid1 sdb3[1] 134801344 blocks [2/1] [_u]
With just DRIVE0 in:
cat /proc/mdstat
md0 : active raid1 sdb3[0] 134801344 blocks [2/1] [U_]
What is this telling me?
what is the difference between sdb3[1] and sdb3[0]?
with both drives, shouldn't it have listed both
what is the difference between [_u] and [U_]
is a u versus a U significant?
does [U_] mean drive0
and
[_u] mean drive1
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have the option of buying a 160gb drive or a 350gb. Does it matter?
For RAID1, the volume of both disks are better to be the same.
Otherwise, it will be the wait of the disk space.
It depends on what's your original disk size.
160GB will be better if you just replace one.
Otherwise, it will be the wait of the disk space.
It depends on what's your original disk size.
160GB will be better if you just replace one.
ASKER