<br><br><br><br>[root@backup2 ~]# cat /etc/mtab<br>/dev/sda3 / ext3 rw 0 0<br>proc /proc proc rw 0 0<br>sysfs /sys sysfs rw 0 0<br>devpts /dev/pts devpts rw,gid=5,mode=620 0 0<br>/dev/sda1 /boot ext3 rw 0 0<br>tmpfs /dev/shm tmpfs rw 0 0<br>
/dev/sdb2 /disk01 ext3 rw 0 0<br>none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0<br>sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0<br>[root@backup2 ~]#<br><br><br><br><br>here is the output from dmesg<br><br>SCSI subsystem initialized<br>
3ware 9000 Storage Controller device driver for Linux v2.26.08.002-2.6.18.<br>ACPI: PCI Interrupt 0000:06:00.0[A] -> GSI 16 (level, low) -> IRQ 169<br>PCI: Setting latency timer of device 0000:06:00.0 to 64<br>scsi0 : 3ware 9000 Storage Controller<br>
3w-9xxx: scsi0: Found a 3ware 9000 Storage Controller at 0xda300000, IRQ: 169.<br>3w-9xxx: scsi0: Firmware FE9X 3.08.00.016, BIOS BE9X 3.08.00.004, Ports: 24.<br> Vendor: AMCC Model: 9650SE-24M DISK Rev: 3.08<br> Type: Direct-Access ANSI SCSI revision: 05<br>
SCSI device sda: 156227584 512-byte hdwr sectors (79989 MB)<br>sda: Write Protect is off<br>sda: Mode Sense: 23 00 00 00<br>SCSI device sda: drive cache: none<br>SCSI device sda: 156227584 512-byte hdwr sectors (79989 MB)<br>
sda: Write Protect is off<br>sda: Mode Sense: 23 00 00 00<br>SCSI device sda: drive cache: none<br> sda: sda1 sda2 sda3<br>sd 0:0:0:0: Attached scsi disk sda<br> Vendor: AMCC Model: 9650SE-24M DISK Rev: 3.08<br> Type: Direct-Access ANSI SCSI revision: 05<br>
sdb : very big device. try to use READ CAPACITY(16).<br>SCSI device sdb: 6835791872 512-byte hdwr sectors (3499925 MB)<br>sdb: Write Protect is off<br>sdb: Mode Sense: 23 00 00 00<br>SCSI device sdb: drive cache: none<br>
sdb : very big device. try to use READ CAPACITY(16).<br>SCSI device sdb: 6835791872 512-byte hdwr sectors (3499925 MB)<br>sdb: Write Protect is off<br>sdb: Mode Sense: 23 00 00 00<br>SCSI device sdb: drive cache: none<br>
sdb: sdb1 sdb2<br>sd 0:0:1:0: Attached scsi disk sdb<br> Vendor: AMCC Model: 9650SE-24M DISK Rev: 3.08<br> Type: Direct-Access ANSI SCSI revision: 05<br>sdc : very big device. try to use READ CAPACITY(16).<br>
SCSI device sdc: 10741958656 512-byte hdwr sectors (5499883 MB)<br>sdc: Write Protect is off<br>sdc: Mode Sense: 23 00 00 00<br>SCSI device sdc: drive cache: none<br>sdc : very big device. try to use READ CAPACITY(16).<br>
SCSI device sdc: 10741958656 512-byte hdwr sectors (5499883 MB)<br>sdc: Write Protect is off<br>sdc: Mode Sense: 23 00 00 00<br>SCSI device sdc: drive cache: none<br> sdc: unknown partition table<br>sd 0:0:2:0: Attached scsi disk sdc<br>
kjournald starting. Commit interval 5 seconds<br>EXT3-fs: mounted filesystem with ordered data mode.<br>audit(1285090871.535:2): enforcing=1 old_enforcing=0 auid=4294967295<br>security: 3 users, 6 roles, 1587 types, 172 bools, 1 sens, 1024 cats<br>
security: 59 classes, 49762 rules<br>SELinux: Completing initialization.<br>SELinux: Setting up existing superblocks.<br>SELinux: initialized (dev sda3, type ext3), uses xattr<br>SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts<br>
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs<br>SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts<br>SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts<br>SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs<br>
SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses genfs_contexts<br>SELinux: initialized (dev devpts, type devpts), uses transition SIDs<br>SELinux: initialized (dev eventpollfs, type eventpollfs), uses task SIDs<br>
SELinux: initialized (dev inotifyfs, type inotifyfs), uses genfs_contexts<br>SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs<br>SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts<br>SELinux: initialized (dev pipefs, type pipefs), uses task SIDs<br>
SELinux: initialized (dev sockfs, type sockfs), uses task SIDs<br>SELinux: initialized (dev cpuset, type cpuset), not configured for labeling<br>SELinux: initialized (dev proc, type proc), uses genfs_contexts<br>SELinux: initialized (dev bdev, type bdev), uses genfs_contexts<br>
SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts<br>SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts<br>audit(1285090871.836:3): policy loaded auid=4294967295<br>input: PC Speaker as /class/input/input1<br>
sd 0:0:0:0: Attached scsi generic sg0 type 0<br>sd 0:0:1:0: Attached scsi generic sg1 type 0<br>sd 0:0:2:0: Attached scsi generic sg2 type 0<br>Intel(R) PRO/1000 Network Driver - version 7.2.7-k2-NAPI<br>Copyright (c) 1999-2006 Intel Corporation.<br>
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 169<br>PCI: Setting latency timer of device 0000:03:00.0 to 64<br>e1000: 0000:03:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x4) 00:15:17:29:dc:62<br>
ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 19 (level, low) -> IRQ 233<br>hdb: ATAPI 24X CD-ROM drive, 256kB Cache, UDMA(33)<br>Uniform CD-ROM driver Revision: 3.20<br>intel_rng: FWH not detected<br>e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection<br>
ACPI: PCI Interrupt 0000:03:00.1[B] -> GSI 17 (level, low) -> IRQ 185<br>PCI: Setting latency timer of device 0000:03:00.1 to 64<br>e1000: 0000:03:00.1: e1000_probe: (PCI Express:2.5Gb/s:Width x4) 00:15:17:29:dc:63<br>
Floppy drive(s): fd0 is 1.44M<br>FDC 0 is a post-1991 82077<br>e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection<br>ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 18 (level, low) -> IRQ 177<br>PCI: Setting latency timer of device 0000:04:00.0 to 64<br>
parport: PnPBIOS parport detected.<br>parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP]<br>e1000: 0000:04:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x4) 00:30:48:63:c7:44<br>e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network Connection<br>
ACPI: PCI Interrupt 0000:04:00.1[B] -> GSI 19 (level, low) -> IRQ 233<br>PCI: Setting latency timer of device 0000:04:00.1 to 64<br>e1000: 0000:04:00.1: e1000_probe: (PCI Express:2.5Gb/s:Width x4) 00:30:48:63:c7:45<br>
e1000: eth3: e1000_probe: Intel(R) PRO/1000 Network Connection<br>lp0: using parport0 (interrupt-driven).<br>lp0: console ready<br>ACPI: Power Button (FF) [PWRF]<br>ACPI: Power Button (CM) [PWRB]<br>ibm_acpi: ec object not found<br>
md: Autodetecting RAID arrays.<br>md: autorun ...<br>md: ... autorun DONE.<br>device-mapper: ioctl: 4.11.0-ioctl (2006-09-14) initialised: <a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a><br>EXT3 FS on sda3, internal journal<br>
kjournald starting. Commit interval 5 seconds<br>EXT3 FS on sda1, internal journal<br>EXT3-fs: mounted filesystem with ordered data mode.<br>SELinux: initialized (dev sda1, type ext3), uses xattr<br>SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs<br>
kjournald starting. Commit interval 5 seconds<br>EXT3 FS on sdb2, internal journal<br>EXT3-fs: mounted filesystem with ordered data mode.<br>SELinux: initialized (dev sdb2, type ext3), uses xattr<br>Adding 16386292k swap on /dev/sda2. Priority:-1 extents:1 across:16386292k<br>
SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts<br>IA-32 Microcode Update Driver: v1.14a <<a href="mailto:tigran@veritas.com">tigran@veritas.com</a>><br>NET: Registered protocol family 10<br>
lo: Disabled Privacy Extensions<br>IPv6 over IPv4 tunneling driver<br>process `sysctl' is using deprecated sysctl (syscall) net.ipv6.neigh.lo.retrans_time; Use net.ipv6.neigh.lo.retrans_time_ms instead.<br>ADDRCONF(NETDEV_UP): eth0: link is not ready<br>
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex<br>ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready<br>ADDRCONF(NETDEV_UP): eth1: link is not ready<br>e1000: eth1: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex<br>
e1000: eth1: e1000_watchdog: 10/100 speed: disabling TSO<br>ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready<br>audit(1285090889.292:4): audit_pid=2179 old=0 by auid=4294967295 subj=system_u:system_r:auditd_t:s0<br>SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts<br>
Bluetooth: Core ver 2.10<br>NET: Registered protocol family 31<br>Bluetooth: HCI device and connection manager initialized<br>Bluetooth: HCI socket layer initialized<br>Bluetooth: L2CAP ver 2.8<br>Bluetooth: L2CAP socket layer initialized<br>
Bluetooth: RFCOMM socket layer initialized<br>Bluetooth: RFCOMM TTY layer initialized<br>Bluetooth: RFCOMM ver 1.8<br>Bluetooth: HIDP (Human Interface Emulation) ver 1.1<br>SELinux: initialized (dev autofs, type autofs), uses genfs_contexts<br>
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts<br>SELinux: initialized (dev autofs, type autofs), uses genfs_contexts<br>eth0: no IPv6 routers present<br>eth1: no IPv6 routers present<br>3w-9xxx: scsi0: AEN: INFO (0x04:0x0029): Verify started:unit=2.<br>
3w-9xxx: scsi0: AEN: INFO (0x04:0x002B): Verify completed:unit=2.<br>[root@backup2 ~]#<br><br><br><br>after re-reading this I tried to fsck /dev/sdc but got these results<br><br><br>[root@backup2 ~]# fsck /dev/sdc<br>fsck 1.39 (29-May-2006)<br>
e2fsck 1.39 (29-May-2006)<br>Group descriptors look bad... trying backup blocks...<br>fsck.ext2: Bad magic number in super-block while trying to open /dev/sdc<br><br>The superblock could not be read or does not describe a correct ext2<br>
filesystem. If the device is valid and it really contains an ext2<br>filesystem (and not swap or ufs or something else), then the superblock<br>is corrupt, and you might try running e2fsck with an alternate superblock:<br>
e2fsck -b 8193 <device><br><br>[root@backup2 ~]#<br><br><br><br><div class="gmail_quote">On Fri, Sep 24, 2010 at 4:58 PM, tid <span dir="ltr"><<a href="mailto:td@bloogaloo.co.uk">td@bloogaloo.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On 22 September 2010 21:45, John Edwards <<a href="mailto:john@cornerstonelinux.co.uk">john@cornerstonelinux.co.uk</a>> wrote:<br>
> As this is a problem with your 3ware RAID controller (which is<br>
> propriety and non-open) I think their support department would<br>
> be the best people to ask.<br>
<br>
</div>Having recently been through the rather terrifying experience of<br>
recovering 5Tb+ of data<br>
from a failed SAN based on a 3ware card, I personally recommend using<br>
this as the<br>
last option if no other alternatives are available. I wasn't impressed<br>
with the call-center<br>
drone's level of technical expertise.<br>
<br>
What filesystem type were you using on the failed disk?<br>
<div><div></div><div class="h5">--<br>
Gllug mailing list - <a href="mailto:Gllug@gllug.org.uk">Gllug@gllug.org.uk</a><br>
<a href="http://lists.gllug.org.uk/mailman/listinfo/gllug" target="_blank">http://lists.gllug.org.uk/mailman/listinfo/gllug</a><br>
</div></div></blockquote></div><br>