| View previous topic :: View next topic |
| Author |
Message |
Argetlam
n00b
Joined: 09 Jan 2007
Posts: 14
|
 Posted: Wed May 18, 2011 12:10 am Post subject: Superblock Invalid on RAID 5 after reboot |
 |
|
Ok so the machine booted. I am not sure why. But when it came back I am getting a error for my RAID 5. This RAID 5 has all my data and I am in the process of building a new computer to copy it too, so getting this RAID back is key.
Anyway before I panic more. Let me post the info because I may just be over reacting. Here is the dmesg output.
| Code: |
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 9 and added 9 devices.
md: autorun ...
md: considering sdf4 ...
md: adding sdf4 ...
md: sdf3 has different UUID to sdf4
md: sdf1 has different UUID to sdf4
md: adding sde4 ...
md: sde3 has different UUID to sdf4
md: sde1 has different UUID to sdf4
md: sdc1 has different UUID to sdf4
md: sdb1 has different UUID to sdf4
md: sda1 has different UUID to sdf4
md: created md4
md: bind<sde4>
md: bind<sdf4>
md: running: <sdf4><sde4>
raid1: raid set md4 active with 2 out of 2 mirrors
md4: detected capacity change from 0 to 90395705344
md: considering sdf3 ...
md: adding sdf3 ...
md: sdf1 has different UUID to sdf3
md: adding sde3 ...
md: sde1 has different UUID to sdf3
md: sdc1 has different UUID to sdf3
md: sdb1 has different UUID to sdf3
md: sda1 has different UUID to sdf3
md: created md3
md: bind<sde3>
md: bind<sdf3>
md: running: <sdf3><sde3>
raid1: raid set md3 active with 2 out of 2 mirrors
md3: detected capacity change from 0 to 65004306432
md: considering sdf1 ...
md: adding sdf1 ...
md: adding sde1 ...
md: sdc1 has different UUID to sdf1
md: sdb1 has different UUID to sdf1
md: sda1 has different UUID to sdf1
md: created md1
md: bind<sde1>
md: bind<sdf1>
md: running: <sdf1><sde1>
raid1: raid set md1 active with 2 out of 2 mirrors
md1: detected capacity change from 0 to 131465216
md: considering sdc1 ...
md: adding sdc1 ...
md: adding sdb1 ...
md: adding sda1 ...
md: created md5
md: bind<sda1>
md: bind<sdb1>
md: bind<sdc1>
md: running: <sdc1><sdb1><sda1>
raid5: md5 is not clean -- starting background reconstruction
raid5: device sdc1 operational as raid disk 2
raid5: device sdb1 operational as raid disk 1
raid5: device sda1 operational as raid disk 0
raid5: allocated 4270kB for md5
2: w=1 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
1: w=2 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
0: w=3 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
raid5: cannot start dirty degraded array for md5
RAID5 conf printout:
--- rd:4 wd:3
disk 0, o:1, dev:sda1
disk 1, o:1, dev:sdb1
disk 2, o:1, dev:sdc1
raid5: failed to run raid set md5
md: pers->run() failed ...
md: do_md_run() returned -5
md: md5 stopped.
md: unbind<sdc1>
md: export_rdev(sdc1)
md: unbind<sdb1>
md: export_rdev(sdb1)
md: unbind<sda1>
md: export_rdev(sda1)
md: ... autorun DONE.
md3: unknown partition table
EXT3-fs (md3): recovery required on readonly filesystem
EXT3-fs (md3): write access will be enabled during recovery
kjournald starting. Commit interval 5 seconds
EXT3-fs (md3): recovery complete
EXT3-fs (md3): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) readonly on device 9:3.
Freeing unused kernel memory: 356k freed
udev: starting version 151
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
nvidia 0000:05:00.0: PCI INT A -> Link[APC3] -> GSI 18 (level, low) -> IRQ 18
nvidia 0000:05:00.0: setting latency timer to 64
vgaarb: device changed decodes: PCI:0000:05:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 195.36.24 Thu Apr 22 19:10:14 PDT 2010
md4:
md1: unknown partition table
unknown partition table
EXT3-fs (md3): using internal journal
kjournald starting. Commit interval 5 seconds
EXT3-fs (md4): using internal journal
EXT3-fs (md4): mounted filesystem with writeback data mode
EXT3-fs (md5): error: unable to read superblock
Adding 4401804k swap on /dev/sde2. Priority:1 extents:1 across:4401804k
sky2 0000:02:00.0: eth0: enabling interface
sky2 0000:02:00.0: eth0: Link is up at 100 Mbps, full duplex, flow control both
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
EXT3-fs (md5): error: unable to read superblock
|
Any help is appreciated. Cause at the moment. I am a little freaked out. |
|
| Back to top |
|
 |
Argetlam
n00b
Joined: 09 Jan 2007
Posts: 14
|
| Posted: Wed May 18, 2011 2:21 am Post subject: |
|
|
| I think the drives are dying. I can't tell, the box has powered down a few times and I don't know if its cause of the drives. They all report ok in bios and on bootup. Anyone have any suggestions. I have a freenas box that I was setting up that has most of the data. Does anyone have any thoughts about maybe getting the data off these drives?? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gentoo on AMD64
