March 23, 201115 yr I had an array running with: Parity 2.0TB WD20EARS Disc 1) 2.0TB WD20EARS Disc 2) 2.0TB WD20EARS Disc 3) 500GB WD500AAKS Disc 4) 500GB WD500AAKS Cache 500GB WD500AAKS So after running the array for a few months I was coming to the max limit of the setup. Following instructions I replaced one drive at a time an allowed for the system to reset between disc change outs. Along with adding in an additional drive bringing my array to 5 disc. New array: Parity 2.0TB WD20EARS Disc 1) 2.0TB WD20EARS Disc 2) 2.0TB WD20EARS Disc 3) 2.0TB WD20EARS Disc 4) 2.0TB WD20EARS Disc 5) 2.0TB WD20EARS Cache 500GB WD500AAKS This set up went for a week when I had two drive failed( Disc 3 and 4) within hours of each other. At least that is what I can tell, from files not being accessible from my network. So I started the replacing the hard drive both at the same time. not sure if this was a bad idea, the array would not remount. Gave me a drives not matched in unmenu.main page, so I then started the process of doing one change out at a time. Replacing Disc 4 with the bad drive, and tried to format the drive again. this went on all night, the system seem it never formatted the drive. Tried it again with the other drive, following the instruction of stopping the array and taking the drive out of the device allocation. with no luck when rebooting the system back up. I am sure I am skipping something but it comes down to I have tried to get these drive to become part of the array with no luck. I even tried to mount the old 500GB drive to see if it will do something to help load the new drive with no luck. Now my array is stuck at not noticing any of the newer drive added. New to Linux, so if you can help. could you give command layout line by line, any help is appreciated. Thanks in advanced. Dan SYSLOG Mar 23 07:34:32 Tower kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none Mar 23 07:34:32 Tower kernel: vgaarb: loaded Mar 23 07:34:32 Tower kernel: SCSI subsystem initialized Mar 23 07:34:32 Tower kernel: libata version 3.00 loaded. Mar 23 07:34:32 Tower kernel: usbcore: registered new interface driver usbfs Mar 23 07:34:32 Tower kernel: usbcore: registered new interface driver hub Mar 23 07:34:32 Tower kernel: usbcore: registered new device driver usb Mar 23 07:34:32 Tower kernel: PCI: Using ACPI for IRQ routing Mar 23 07:34:32 Tower kernel: Switching to clocksource tsc Mar 23 07:34:32 Tower kernel: pnp: PnP ACPI init Mar 23 07:34:32 Tower kernel: ACPI: bus type pnp registered Mar 23 07:34:32 Tower kernel: pnp: PnP ACPI: found 15 devices Mar 23 07:34:32 Tower kernel: ACPI: ACPI bus type pnp unregistered Mar 23 07:34:32 Tower kernel: system 00:01: ioport range 0x4d0-0x4d1 has been reserved Mar 23 07:34:32 Tower kernel: system 00:01: ioport range 0x290-0x29f has been reserved Mar 23 07:34:32 Tower kernel: system 00:01: ioport range 0x800-0x805 has been reserved Mar 23 07:34:32 Tower kernel: system 00:01: ioport range 0x290-0x294 has been reserved Mar 23 07:34:32 Tower kernel: system 00:01: ioport range 0x880-0x88f has been reserved Mar 23 07:34:32 Tower kernel: system 00:0b: ioport range 0x400-0x4cf could not be reserved Mar 23 07:34:32 Tower kernel: system 00:0b: ioport range 0x4d2-0x4ff has been reserved Mar 23 07:34:32 Tower kernel: system 00:0c: iomem range 0xf4000000-0xf7ffffff has been reserved Mar 23 07:34:32 Tower kernel: system 00:0d: iomem range 0xd5000-0xd7fff has been reserved Mar 23 07:34:32 Tower kernel: system 00:0d: iomem range 0xf0000-0xf7fff could not be reserved Mar 23 07:34:32 Tower kernel: system 00:0d: iomem range 0xf8000-0xfbfff could not be reserved Mar 23 07:34:32 Tower kernel: system 00:0d: iomem range 0xfc000-0xfffff could not be reserved Mar 23 07:34:32 Tower kernel: system 00:0d: iomem range 0xdfeb0000-0xdfefffff could not be reserved Mar 23 07:34:32 Tower kernel: system 00:0d: iomem range 0x0-0x9ffff could not be reserved Mar 23 07:34:32 Tower kernel: system 00:0d: iomem range 0x100000-0xdfeaffff could not be reserved Mar 23 07:34:32 Tower kernel: system 00:0d: iomem range 0xfec00000-0xfec00fff could not be reserved Mar 23 07:34:32 Tower kernel: system 00:0d: iomem range 0xfed10000-0xfed1dfff has been reserved Mar 23 07:34:32 Tower kernel: system 00:0d: iomem range 0xfed20000-0xfed8ffff has been reserved Mar 23 07:34:32 Tower kernel: system 00:0d: iomem range 0xfee00000-0xfee00fff has been reserved Mar 23 07:34:32 Tower kernel: system 00:0d: iomem range 0xffb00000-0xffb7ffff has been reserved Mar 23 07:34:32 Tower kernel: system 00:0d: iomem range 0xfff00000-0xffffffff has been reserved Mar 23 07:34:32 Tower kernel: system 00:0d: iomem range 0xe0000-0xeffff has been reserved Mar 23 07:34:32 Tower kernel: pci 0000:00:01.0: PCI bridge, secondary bus 0000:01 Mar 23 07:34:32 Tower kernel: pci 0000:00:01.0: IO window: 0xb000-0xbfff Mar 23 07:34:32 Tower kernel: pci 0000:00:01.0: MEM window: 0xf8000000-0xfbffffff Mar 23 07:34:32 Tower kernel: pci 0000:00:01.0: PREFETCH window: 0x000000e0000000-0x000000efffffff Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.0: PCI bridge, secondary bus 0000:02 Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.0: IO window: 0x1000-0x1fff Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.0: MEM window: 0xf0000000-0xf01fffff Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.0: PREFETCH window: 0x000000f0200000-0x000000f03fffff Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.3: PCI bridge, secondary bus 0000:03 Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.3: IO window: 0xe000-0xefff Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.3: MEM window: 0xfdc00000-0xfdcfffff Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.3: PREFETCH window: 0x000000f0400000-0x000000f05fffff Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.4: PCI bridge, secondary bus 0000:04 Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.4: IO window: 0xd000-0xdfff Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.4: MEM window: 0xfda00000-0xfdafffff Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.4: PREFETCH window: 0x000000fde00000-0x000000fdefffff Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.5: PCI bridge, secondary bus 0000:05 Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.5: IO window: 0x2000-0x2fff Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.5: MEM window: 0xfdd00000-0xfddfffff Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.5: PREFETCH window: 0x000000f0600000-0x000000f07fffff Mar 23 07:34:32 Tower kernel: pci 0000:00:1e.0: PCI bridge, secondary bus 0000:06 Mar 23 07:34:32 Tower kernel: pci 0000:00:1e.0: IO window: 0xc000-0xcfff Mar 23 07:34:32 Tower kernel: pci 0000:00:1e.0: MEM window: 0xfdb00000-0xfdbfffff Mar 23 07:34:32 Tower kernel: pci 0000:00:1e.0: PREFETCH window: 0xf0800000-0xf08fffff Mar 23 07:34:32 Tower kernel: pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Mar 23 07:34:32 Tower kernel: pci 0000:00:01.0: setting latency timer to 64 Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.0: enabling device (0000 -> 0003) Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.0: setting latency timer to 64 Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.3: PCI INT D -> GSI 19 (level, low) -> IRQ 19 Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.3: setting latency timer to 64 Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.4: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.4: setting latency timer to 64 Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.5: enabling device (0006 -> 0007) Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17 Mar 23 07:34:32 Tower kernel: pci 0000:00:1c.5: setting latency timer to 64 Mar 23 07:34:32 Tower kernel: pci 0000:00:1e.0: setting latency timer to 64 Mar 23 07:34:32 Tower kernel: pci_bus 0000:00: resource 0 io: [0x00-0xffff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:01: resource 0 io: [0xb000-0xbfff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:01: resource 1 mem: [0xf8000000-0xfbffffff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:01: resource 2 pref mem [0xe0000000-0xefffffff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:02: resource 0 io: [0x1000-0x1fff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:02: resource 1 mem: [0xf0000000-0xf01fffff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:02: resource 2 pref mem [0xf0200000-0xf03fffff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:03: resource 0 io: [0xe000-0xefff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:03: resource 1 mem: [0xfdc00000-0xfdcfffff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:03: resource 2 pref mem [0xf0400000-0xf05fffff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:04: resource 0 io: [0xd000-0xdfff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:04: resource 1 mem: [0xfda00000-0xfdafffff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:04: resource 2 pref mem [0xfde00000-0xfdefffff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:05: resource 0 io: [0x2000-0x2fff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:05: resource 1 mem: [0xfdd00000-0xfddfffff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:05: resource 2 pref mem [0xf0600000-0xf07fffff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:06: resource 0 io: [0xc000-0xcfff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:06: resource 1 mem: [0xfdb00000-0xfdbfffff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:06: resource 2 pref mem [0xf0800000-0xf08fffff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:06: resource 3 io: [0x00-0xffff] Mar 23 07:34:32 Tower kernel: pci_bus 0000:06: resource 4 mem: [0x000000-0xffffffffffffffff] Mar 23 07:34:32 Tower kernel: NET: Registered protocol family 2 Mar 23 07:34:32 Tower kernel: IP route cache hash table entries: 32768 (order: 5, 131072 bytes) Mar 23 07:34:32 Tower kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes) Mar 23 07:34:32 Tower kernel: TCP bind hash table entries: 65536 (order: 7, 524288 bytes) Mar 23 07:34:32 Tower kernel: TCP: Hash tables configured (established 131072 bind 65536) Mar 23 07:34:32 Tower kernel: TCP reno registered Mar 23 07:34:32 Tower kernel: NET: Registered protocol family 1 Mar 23 07:34:32 Tower kernel: RPC: Registered udp transport module. Mar 23 07:34:32 Tower kernel: RPC: Registered tcp transport module. Mar 23 07:34:32 Tower kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Mar 23 07:34:32 Tower kernel: pci 0000:01:00.0: Boot video device Mar 23 07:34:32 Tower kernel: Unpacking initramfs... Mar 23 07:34:32 Tower kernel: Freeing initrd memory: 53456k freed Mar 23 07:34:32 Tower kernel: highmem bounce pool size: 64 pages Mar 23 07:34:32 Tower kernel: Installing knfsd (copyright © 1996 [email protected]). Mar 23 07:34:32 Tower kernel: Slow work thread pool: Starting up Mar 23 07:34:32 Tower kernel: Slow work thread pool: Ready Mar 23 07:34:32 Tower kernel: fuse init (API version 7.13) Mar 23 07:34:32 Tower kernel: msgmni has been set to 1695 Mar 23 07:34:32 Tower kernel: io scheduler noop registered (default) Mar 23 07:34:32 Tower kernel: io scheduler anticipatory registered Mar 23 07:34:32 Tower kernel: io scheduler deadline registered Mar 23 07:34:32 Tower kernel: io scheduler cfq registered Mar 23 07:34:32 Tower kernel: pcieport 0000:00:01.0: irq 24 for MSI/MSI-X Mar 23 07:34:32 Tower kernel: pcieport 0000:00:01.0: setting latency timer to 64 Mar 23 07:34:32 Tower kernel: pcieport 0000:00:1c.0: irq 25 for MSI/MSI-X Mar 23 07:34:32 Tower kernel: pcieport 0000:00:1c.0: setting latency timer to 64 Mar 23 07:34:32 Tower kernel: pcieport 0000:00:1c.3: irq 26 for MSI/MSI-X Mar 23 07:34:32 Tower kernel: pcieport 0000:00:1c.3: setting latency timer to 64 Mar 23 07:34:32 Tower kernel: pcieport 0000:00:1c.4: irq 27 for MSI/MSI-X Mar 23 07:34:32 Tower kernel: pcieport 0000:00:1c.4: setting latency timer to 64 Mar 23 07:34:32 Tower kernel: pcieport 0000:00:1c.5: irq 28 for MSI/MSI-X Mar 23 07:34:32 Tower kernel: pcieport 0000:00:1c.5: setting latency timer to 64 Mar 23 07:34:32 Tower kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 Mar 23 07:34:32 Tower kernel: ACPI: Power Button [PWRB] Mar 23 07:34:32 Tower kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 Mar 23 07:34:32 Tower kernel: ACPI: Power Button [PWRF] Mar 23 07:34:32 Tower kernel: ACPI Warning: Incorrect checksum in table [TAMG] - 9B, should be 9A (20090903/tbutils-314) Mar 23 07:34:32 Tower kernel: ACPI: SSDT dfeee320 002AE (v01 PmRef Cpu0Ist 00003000 INTL 20040311) Mar 23 07:34:32 Tower kernel: Marking TSC unstable due to TSC halts in idle Mar 23 07:34:32 Tower kernel: Switching to clocksource hpet Mar 23 07:34:32 Tower kernel: processor LNXCPU:00: registered as cooling_device0 Mar 23 07:34:32 Tower kernel: ACPI: SSDT dfeee7e0 00152 (v01 PmRef Cpu1Ist 00003000 INTL 20040311) Mar 23 07:34:32 Tower kernel: processor LNXCPU:01: registered as cooling_device1 Mar 23 07:34:32 Tower kernel: lp: driver loaded but no devices found Mar 23 07:34:32 Tower kernel: Real Time Clock Driver v1.12b Mar 23 07:34:32 Tower kernel: Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds). Mar 23 07:34:32 Tower kernel: Hangcheck: Using get_cycles(). Mar 23 07:34:32 Tower kernel: Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled Mar 23 07:34:32 Tower kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Mar 23 07:34:32 Tower kernel: 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Mar 23 07:34:32 Tower kernel: parport_pc 00:09: reported by Plug and Play ACPI Mar 23 07:34:32 Tower kernel: parport0: PC-style at 0x378, irq 7 [PCSPP(,...)] Mar 23 07:34:32 Tower kernel: lp0: using parport0 (interrupt-driven). Mar 23 07:34:32 Tower kernel: Floppy drive(s): fd0 is 1.44M Mar 23 07:34:32 Tower kernel: FDC 0 is a post-1991 82077 Mar 23 07:34:32 Tower kernel: loop: module loaded Mar 23 07:34:32 Tower kernel: Uniform Multi-Platform E-IDE driver Mar 23 07:34:32 Tower kernel: e100: Intel® PRO/100 Network Driver, 3.5.24-k2-NAPI Mar 23 07:34:32 Tower kernel: e100: Copyright© 1999-2006 Intel Corporation Mar 23 07:34:32 Tower kernel: Broadcom NetXtreme II CNIC Driver cnic v2.0.1 (Oct 01, 2009) Mar 23 07:34:32 Tower kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Mar 23 07:34:32 Tower kernel: ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18 Mar 23 07:34:32 Tower kernel: ehci_hcd 0000:00:1a.7: setting latency timer to 64 Mar 23 07:34:32 Tower kernel: ehci_hcd 0000:00:1a.7: EHCI Host Controller Mar 23 07:34:32 Tower kernel: ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1 Mar 23 07:34:32 Tower kernel: ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported Mar 23 07:34:32 Tower kernel: ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfdfff000 Mar 23 07:34:32 Tower kernel: ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00 Mar 23 07:34:32 Tower kernel: usb usb1: configuration #1 chosen from 1 choice Mar 23 07:34:32 Tower kernel: hub 1-0:1.0: USB hub found Mar 23 07:34:32 Tower kernel: hub 1-0:1.0: 6 ports detected Mar 23 07:34:32 Tower kernel: ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23 Mar 23 07:34:32 Tower kernel: ehci_hcd 0000:00:1d.7: setting latency timer to 64 Mar 23 07:34:32 Tower kernel: ehci_hcd 0000:00:1d.7: EHCI Host Controller Mar 23 07:34:32 Tower kernel: ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2 Mar 23 07:34:32 Tower kernel: ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported Mar 23 07:34:32 Tower kernel: ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfdffe000 Mar 23 07:34:32 Tower kernel: ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00 Mar 23 07:34:32 Tower kernel: usb usb2: configuration #1 chosen from 1 choice Mar 23 07:34:32 Tower kernel: hub 2-0:1.0: USB hub found Mar 23 07:34:32 Tower kernel: hub 2-0:1.0: 6 ports detected Mar 23 07:34:32 Tower kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Mar 23 07:34:32 Tower kernel: uhci_hcd: USB Universal Host Controller Interface driver Mar 23 07:34:32 Tower kernel: uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Mar 23 07:34:32 Tower kernel: uhci_hcd 0000:00:1a.0: setting latency timer to 64 Mar 23 07:34:32 Tower kernel: uhci_hcd 0000:00:1a.0: UHCI Host Controller Mar 23 07:34:32 Tower kernel: uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3 Mar 23 07:34:32 Tower kernel: uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000ff00 Mar 23 07:34:32 Tower kernel: usb usb3: configuration #1 chosen from 1 choice Mar 23 07:34:32 Tower kernel: hub 3-0:1.0: USB hub found Mar 23 07:34:32 Tower kernel: hub 3-0:1.0: 2 ports detected Mar 23 07:34:32 Tower kernel: uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21 Mar 23 07:34:32 Tower kernel: uhci_hcd 0000:00:1a.1: setting latency timer to 64 Mar 23 07:34:32 Tower kernel: uhci_hcd 0000:00:1a.1: UHCI Host Controller Mar 23 07:34:32 Tower kernel: uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4 Mar 23 07:34:32 Tower kernel: uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000fe00 Mar 23 07:34:32 Tower kernel: usb usb4: configuration #1 chosen from 1 choice Mar 23 07:34:32 Tower kernel: hub 4-0:1.0: USB hub found Mar 23 07:34:32 Tower kernel: hub 4-0:1.0: 2 ports detected Mar 23 07:34:32 Tower kernel: uhci_hcd 0000:00:1a.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 Mar 23 07:34:32 Tower kernel: uhci_hcd 0000:00:1a.2: setting latency timer to 64
March 23, 201115 yr Starting at the beginning, when you say 2 drives failed because the files were no longer accessible from the network - what was their status in the Unraid? Based on what you've stated so far, its possible the drives / data are salvageable, but you need to back up a few steps... replacing the drives should be down only after all attempts to fix them are exhausted. Put the system back the way it was originally, with the "failed" drives. Start it up, see what Unraid says, post the syslog. If it sees the drives, then you'll get guidance on running SMART tests, as well as checking the file system on them.
March 23, 201115 yr If you do not care about the data then assign the drives how you want them on the devices page, log-in and type initconfig. Answer Yes and the array will be reset and work again. Make sure you do not get the assignments wrong and you will lose any possibility of rebuilding those failed drives. Peter
March 23, 201115 yr Author Status Update, I got the array back up and seems to be formatting my drive. I had to leave out Disc 4 and only install one new disc for the failed disc. current array: Parity 2.0TB WD20EARS Disc 1) 2.0TB WD20EARS Disc 2) 2.0TB WD20EARS Disc 3) 2.0TB WD20EARS In Formatting stage I believe Disc 4) No DISC Disc 5) 2.0TB WD20EARS Cache 500GB WD500AAKS I am trying to keep the parity, hopefully I don't lose any of my files. I am going to let this run to see if the disc take a format. I will try to post the output once it's done. Thanks
March 23, 201115 yr Author O.k. last attempt did not work, it's show it syslog file that there is errors on the hard drive. I do not see any percentage of formatting on hard drive. the log files are to large to post, what would be the main body anyone might like to see. syslogs_03-23-2011.txt
March 23, 201115 yr You can not recover from 2 failed disks. You must get one of them working again to rebuild the second one. I have no idea what you mean by formatting. unRAID should have attempted to rebuild the failed drive. It doesn't really matter though since putting a disk in and getting it formatted won't recover any data. Peter
March 24, 201115 yr Author On the http://Tower/main.htm page where the basic information is laid out for the array. when you install a new disc it what to format the drive to the file system. While these are new drive and I went along with what the system was asking. Now if I run the initconfig will I lose all my files or just the ones from the dead drives?
March 24, 201115 yr Author Mar 23 19:19:48 Tower kernel: hub 7-0:1.0: USB hub found Mar 23 19:19:48 Tower kernel: hub 7-0:1.0: 2 ports detected Mar 23 19:19:48 Tower kernel: uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 Mar 23 19:19:48 Tower kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64 Mar 23 19:19:48 Tower kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller Mar 23 19:19:48 Tower kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8 Mar 23 19:19:48 Tower kernel: uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000fa00 Mar 23 19:19:48 Tower kernel: usb usb8: configuration #1 chosen from 1 choice Mar 23 19:19:48 Tower kernel: hub 8-0:1.0: USB hub found Mar 23 19:19:48 Tower kernel: hub 8-0:1.0: 2 ports detected Mar 23 19:19:48 Tower kernel: usbcore: registered new interface driver usblp Mar 23 19:19:48 Tower kernel: Initializing USB Mass Storage driver... Mar 23 19:19:48 Tower kernel: usbcore: registered new interface driver usb-storage Mar 23 19:19:48 Tower kernel: USB Mass Storage support registered. Mar 23 19:19:48 Tower kernel: PNP: No PS/2 controller found. Probing ports directly. Mar 23 19:19:48 Tower kernel: Failed to disable AUX port, but continuing anyway... Is this a SiS? Mar 23 19:19:48 Tower kernel: If AUX port is really absent please use the 'i8042.noaux' option. Mar 23 19:19:48 Tower kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Mar 23 19:19:48 Tower kernel: mice: PS/2 mouse device common for all mice Mar 23 19:19:48 Tower kernel: input: PC Speaker as /devices/platform/pcspkr/input/input2 Mar 23 19:19:48 Tower kernel: it87: Found IT8718F chip at 0x290, revision 8 Mar 23 19:19:48 Tower kernel: it87: in3 is VCC (+5V) Mar 23 19:19:48 Tower kernel: cpuidle: using governor ladder Mar 23 19:19:48 Tower kernel: usbcore: registered new interface driver hiddev Mar 23 19:19:48 Tower kernel: usbcore: registered new interface driver usbhid Mar 23 19:19:48 Tower kernel: usbhid: v2.6:USB HID core driver Mar 23 19:19:48 Tower kernel: TCP cubic registered Mar 23 19:19:48 Tower kernel: NET: Registered protocol family 17 Mar 23 19:19:48 Tower kernel: Using IPI No-Shortcut mode Mar 23 19:19:48 Tower kernel: Freeing unused kernel memory: 312k freed Mar 23 19:19:48 Tower kernel: usb 1-5: new high speed USB device using ehci_hcd and address 2 Mar 23 19:19:48 Tower kernel: usb 1-5: configuration #1 chosen from 1 choice Mar 23 19:19:48 Tower kernel: scsi0 : SCSI emulation for USB Mass Storage devices Mar 23 19:19:48 Tower kernel: usb-storage: device found at 2 Mar 23 19:19:48 Tower kernel: usb-storage: waiting for device to settle before scanning Mar 23 19:19:48 Tower kernel: ahci 0000:03:00.0: version 3.0 Mar 23 19:19:48 Tower kernel: ahci 0000:03:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 Mar 23 19:19:48 Tower kernel: ahci 0000:03:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA mode Mar 23 19:19:48 Tower kernel: ahci 0000:03:00.0: flags: 64bit ncq pm led clo pmp pio slum part Mar 23 19:19:48 Tower kernel: ahci 0000:03:00.0: setting latency timer to 64 Mar 23 19:19:48 Tower kernel: scsi1 : ahci Mar 23 19:19:48 Tower kernel: scsi2 : ahci Mar 23 19:19:48 Tower kernel: ata1: SATA max UDMA/133 abar m8192@0xfdcfe000 port 0xfdcfe100 irq 19 Mar 23 19:19:48 Tower kernel: ata2: SATA max UDMA/133 abar m8192@0xfdcfe000 port 0xfdcfe180 irq 19 Mar 23 19:19:48 Tower kernel: usb 8-1: new low speed USB device using uhci_hcd and address 2 Mar 23 19:19:48 Tower kernel: ata1: SATA link down (SStatus 0 SControl 300) Mar 23 19:19:48 Tower kernel: ata2: SATA link down (SStatus 0 SControl 300) Mar 23 19:19:48 Tower kernel: jmicron 0000:03:00.1: IDE controller (0x197b:0x2363 rev 0x02) Mar 23 19:19:48 Tower kernel: JMicron IDE 0000:03:00.1: enabling device (0000 -> 0001) Mar 23 19:19:48 Tower kernel: JMicron IDE 0000:03:00.1: PCI INT B -> GSI 16 (level, low) -> IRQ 16 Mar 23 19:19:48 Tower kernel: jmicron 0000:03:00.1: 100%% native mode on irq 16 Mar 23 19:19:48 Tower kernel: JMicron IDE 0000:03:00.1: setting latency timer to 64 Mar 23 19:19:48 Tower kernel: ide0: BM-DMA at 0xeb00-0xeb07 Mar 23 19:19:48 Tower kernel: ide1: BM-DMA at 0xeb08-0xeb0f Mar 23 19:19:48 Tower kernel: Probing IDE interface ide0... Mar 23 19:19:48 Tower kernel: usb 8-1: configuration #1 chosen from 1 choice Mar 23 19:19:48 Tower kernel: input: Dell Dell USB Optical Mouse as /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0/input/input3 Mar 23 19:19:48 Tower kernel: generic-usb 0003:413C:3012.0001: input,hidraw0: USB HID v1.11 Mouse [Dell Dell USB Optical Mouse] on usb-0000:00:1d.2-1/input0 Mar 23 19:19:48 Tower kernel: usb 8-2: new low speed USB device using uhci_hcd and address 3 Mar 23 19:19:48 Tower kernel: usb 8-2: configuration #1 chosen from 1 choice Mar 23 19:19:48 Tower kernel: input: Dell Dell USB Keyboard as /devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2:1.0/input/input4 Mar 23 19:19:48 Tower kernel: generic-usb 0003:413C:2003.0002: input,hidraw1: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-0000:00:1d.2-2/input0 Mar 23 19:19:48 Tower kernel: Probing IDE interface ide1... Mar 23 19:19:48 Tower kernel: ide0 at 0xef00-0xef07,0xee02 on irq 16 Mar 23 19:19:48 Tower kernel: ide1 at 0xed00-0xed07,0xec02 on irq 16 Mar 23 19:19:48 Tower kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded Mar 23 19:19:48 Tower kernel: r8169 0000:04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Mar 23 19:19:48 Tower kernel: r8169 0000:04:00.0: setting latency timer to 64 Mar 23 19:19:48 Tower kernel: r8169 0000:04:00.0: irq 29 for MSI/MSI-X Mar 23 19:19:48 Tower kernel: eth0: RTL8168d/8111d at 0xf82bc000, 6c:f0:49:77:09:7e, XID 083000c0 IRQ 29 Mar 23 19:19:48 Tower kernel: sata_promise 0000:06:00.0: version 2.12 Mar 23 19:19:48 Tower kernel: sata_promise 0000:06:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 Mar 23 19:19:48 Tower kernel: scsi3 : sata_promise Mar 23 19:19:48 Tower kernel: scsi4 : sata_promise Mar 23 19:19:48 Tower kernel: scsi5 : sata_promise Mar 23 19:19:48 Tower kernel: scsi6 : sata_promise Mar 23 19:19:48 Tower kernel: ata3: SATA max UDMA/133 mmio m4096@0xfdbff000 ata 0xfdbff380 irq 20 Mar 23 19:19:48 Tower kernel: ata4: SATA max UDMA/133 mmio m4096@0xfdbff000 ata 0xfdbff280 irq 20 Mar 23 19:19:48 Tower kernel: ata5: SATA max UDMA/133 mmio m4096@0xfdbff000 ata 0xfdbff200 irq 20 Mar 23 19:19:48 Tower kernel: ata6: SATA max UDMA/133 mmio m4096@0xfdbff000 ata 0xfdbff300 irq 20 Mar 23 19:19:48 Tower kernel: ata3: SATA link down (SStatus 0 SControl 300) Mar 23 19:19:48 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 23 19:19:48 Tower kernel: ata4.00: ATA-8: WDC WD5000AAKS-00YGA0, 12.01C02, max UDMA/133 Mar 23 19:19:48 Tower kernel: ata4.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32) Mar 23 19:19:48 Tower kernel: ata4.00: configured for UDMA/133 Mar 23 19:19:48 Tower kernel: scsi 4:0:0:0: Direct-Access ATA WDC WD5000AAKS-0 12.0 PQ: 0 ANSI: 5 Mar 23 19:19:48 Tower kernel: sd 4:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB) Mar 23 19:19:48 Tower kernel: sd 4:0:0:0: [sda] Write Protect is off Mar 23 19:19:48 Tower kernel: sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00 Mar 23 19:19:48 Tower kernel: sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 23 19:19:48 Tower kernel: sda: sda1 Mar 23 19:19:48 Tower kernel: sd 4:0:0:0: [sda] Attached SCSI disk Mar 23 19:19:48 Tower kernel: ata5: SATA link down (SStatus 0 SControl 300) Mar 23 19:19:48 Tower kernel: ata6: SATA link down (SStatus 0 SControl 300) Mar 23 19:19:48 Tower kernel: ata_piix 0000:00:1f.2: version 2.13 Mar 23 19:19:48 Tower kernel: ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19 Mar 23 19:19:48 Tower kernel: ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ] Mar 23 19:19:48 Tower kernel: ata_piix 0000:00:1f.2: setting latency timer to 64 Mar 23 19:19:48 Tower kernel: scsi7 : ata_piix Mar 23 19:19:48 Tower kernel: scsi8 : ata_piix Mar 23 19:19:48 Tower kernel: ata7: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf900 irq 14 Mar 23 19:19:48 Tower kernel: ata8: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf908 irq 15 Mar 23 19:19:48 Tower kernel: ata_piix 0000:00:1f.5: PCI INT B -> GSI 19 (level, low) -> IRQ 19 Mar 23 19:19:48 Tower kernel: ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ] Mar 23 19:19:48 Tower kernel: ata_piix 0000:00:1f.5: setting latency timer to 64 Mar 23 19:19:48 Tower kernel: scsi9 : ata_piix Mar 23 19:19:48 Tower kernel: scsi10 : ata_piix Mar 23 19:19:48 Tower kernel: ata9: SATA max UDMA/133 cmd 0xf600 ctl 0xf500 bmdma 0xf200 irq 19 Mar 23 19:19:48 Tower kernel: ata10: SATA max UDMA/133 cmd 0xf400 ctl 0xf300 bmdma 0xf208 irq 19 Mar 23 19:19:48 Tower kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 23 19:19:48 Tower kernel: ata10.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133 Mar 23 19:19:48 Tower kernel: ata10.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 0/32) Mar 23 19:19:48 Tower kernel: ata7.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 23 19:19:48 Tower kernel: ata7.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 23 19:19:48 Tower kernel: ata8.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 23 19:19:48 Tower kernel: ata8.01: SATA link down (SStatus 0 SControl 300) Mar 23 19:19:48 Tower kernel: ata8.00: HPA detected: current 3907020911, native 3907029168 Mar 23 19:19:48 Tower kernel: ata8.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133 Mar 23 19:19:48 Tower kernel: ata8.00: 3907020911 sectors, multi 16: LBA48 NCQ (depth 0/32) Mar 23 19:19:48 Tower kernel: ata7.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133 Mar 23 19:19:48 Tower kernel: ata7.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 0/32) Mar 23 19:19:48 Tower kernel: ata7.01: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133 Mar 23 19:19:48 Tower kernel: ata7.01: 3907029168 sectors, multi 16: LBA48 NCQ (depth 0/32) Mar 23 19:19:48 Tower kernel: ata8.00: configured for UDMA/133 Mar 23 19:19:48 Tower kernel: ata7.00: configured for UDMA/133 Mar 23 19:19:48 Tower kernel: ata7.01: configured for UDMA/133 Mar 23 19:19:48 Tower kernel: scsi 7:0:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5 Mar 23 19:19:48 Tower kernel: scsi 7:0:1:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5 Mar 23 19:19:48 Tower kernel: sd 7:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) Mar 23 19:19:48 Tower kernel: sd 7:0:0:0: [sdb] Write Protect is off Mar 23 19:19:48 Tower kernel: sd 7:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Mar 23 19:19:48 Tower kernel: sd 7:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 23 19:19:48 Tower kernel: sdb: Mar 23 19:19:48 Tower kernel: scsi 8:0:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5 Mar 23 19:19:48 Tower kernel: sd 8:0:0:0: [sdd] 3907020911 512-byte logical blocks: (2.00 TB/1.81 TiB) Mar 23 19:19:48 Tower kernel: sd 8:0:0:0: [sdd] Write Protect is off Mar 23 19:19:48 Tower kernel: sd 8:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Mar 23 19:19:48 Tower kernel: sd 8:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 23 19:19:48 Tower kernel: sdd: Mar 23 19:19:48 Tower kernel: ata10.00: configured for UDMA/133 Mar 23 19:19:48 Tower kernel: sdb1 Mar 23 19:19:48 Tower kernel: sd 7:0:1:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) Mar 23 19:19:48 Tower kernel: sd 7:0:1:0: [sdc] Write Protect is off Mar 23 19:19:48 Tower kernel: sd 7:0:1:0: [sdc] Mode Sense: 00 3a 00 00 Mar 23 19:19:48 Tower kernel: sd 7:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 23 19:19:48 Tower kernel: Mar 23 19:19:48 Tower kernel: sdc: sdd1 Mar 23 19:19:48 Tower kernel: sd 8:0:0:0: [sdd] Attached SCSI disk Mar 23 19:19:48 Tower kernel: scsi 0:0:0:0: Direct-Access Lexar JD FireFly 1100 PQ: 0 ANSI: 0 CCS Mar 23 19:19:48 Tower kernel: sd 0:0:0:0: [sde] 3915776 512-byte logical blocks: (2.00 GB/1.86 GiB) Mar 23 19:19:48 Tower kernel: usb-storage: device scan complete Mar 23 19:19:48 Tower kernel: sd 0:0:0:0: [sde] Write Protect is off Mar 23 19:19:48 Tower kernel: sd 0:0:0:0: [sde] Mode Sense: 43 00 00 00 Mar 23 19:19:48 Tower kernel: sd 0:0:0:0: [sde] Assuming drive cache: write through Mar 23 19:19:48 Tower kernel: sd 0:0:0:0: [sde] Assuming drive cache: write through Mar 23 19:19:48 Tower kernel: sde: sde1 Mar 23 19:19:48 Tower kernel: sd 0:0:0:0: [sde] Assuming drive cache: write through Mar 23 19:19:48 Tower kernel: sd 0:0:0:0: [sde] Attached SCSI removable disk Mar 23 19:19:48 Tower kernel: sdc1 Mar 23 19:19:48 Tower kernel: sd 7:0:0:0: [sdb] Attached SCSI disk Mar 23 19:19:48 Tower kernel: sd 7:0:1:0: [sdc] Attached SCSI disk Mar 23 19:19:48 Tower kernel: ata9: link is slow to respond, please be patient (ready=0) Mar 23 19:19:48 Tower kernel: ata9: SRST failed (errno=-16) Mar 23 19:19:48 Tower kernel: ata9: link is slow to respond, please be patient (ready=0) Mar 23 19:19:48 Tower kernel: ata9: SRST failed (errno=-16) Mar 23 19:19:48 Tower kernel: ata9: link is slow to respond, please be patient (ready=0) Mar 23 19:19:48 Tower kernel: ata9: SRST failed (errno=-16) Mar 23 19:19:48 Tower kernel: ata9: limiting SATA link speed to 1.5 Gbps Mar 23 19:19:48 Tower kernel: ata9: SRST failed (errno=-16) Mar 23 19:19:48 Tower kernel: ata9: reset failed, giving up Mar 23 19:19:48 Tower kernel: scsi 10:0:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5 Mar 23 19:19:48 Tower kernel: sd 10:0:0:0: [sdf] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) Mar 23 19:19:48 Tower kernel: sd 10:0:0:0: [sdf] Write Protect is off Mar 23 19:19:48 Tower kernel: sd 10:0:0:0: [sdf] Mode Sense: 00 3a 00 00 Mar 23 19:19:48 Tower kernel: sd 10:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 23 19:19:48 Tower kernel: sdf: sdf1 Mar 23 19:19:48 Tower kernel: sd 10:0:0:0: [sdf] Attached SCSI disk Mar 23 19:19:48 Tower kernel: i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18 Mar 23 19:19:48 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Mar 23 19:19:48 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Mar 23 19:19:48 Tower ifplugd(eth0)[1446]: ifplugd 0.28 initializing. Mar 23 19:19:48 Tower ifplugd(eth0)[1446]: Using interface eth0/6C:F0:49:77:09:7E with driver (version: 2.3LK-NAPI) Mar 23 19:19:48 Tower ifplugd(eth0)[1446]: Using detection mode: SIOCETHTOOL Mar 23 19:19:48 Tower ifplugd(eth0)[1446]: Initialization complete, link beat detected. Mar 23 19:19:48 Tower kernel: r8169: eth0: link up Mar 23 19:19:48 Tower kernel: r8169: eth0: link up Mar 23 19:19:48 Tower ifplugd(eth0)[1446]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. Mar 23 19:19:48 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 hw ether 6C:F0:49:77:09:7E Mar 23 19:19:48 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 192.168.1.14 broadcast 192.168.1.255 netmask 255.255.255.0 Mar 23 19:19:48 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.1.1 metric 1 Mar 23 19:19:48 Tower ifplugd(eth0)[1446]: Program executed successfully. Mar 23 19:19:48 Tower rpc.statd[1495]: Version 1.1.4 Starting Mar 23 19:19:48 Tower emhttp: unRAID System Management Utility version 4.5.6 Mar 23 19:19:48 Tower emhttp: Copyright © 2005-2010, Lime Technology, LLC Mar 23 19:19:48 Tower emhttp: Pro key detected, GUID: 05DC-A761-5GDJ-PPQKXVN13J3V Mar 23 19:19:48 Tower emhttp: shcmd (1): udevadm settle Mar 23 19:19:48 Tower emhttp: Device inventory: Mar 23 19:19:48 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:0:0 host7 (sdb) WDC_WD20EARS-00MVWB0_WD-WCAZA1227437 Mar 23 19:19:48 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:1:0 host7 (sdc) WDC_WD20EARS-00MVWB0_WD-WCAZA1226695 Mar 23 19:19:48 Tower emhttp: pci-0000:00:1f.2-scsi-1:0:0:0 host8 (sdd) WDC_WD20EARS-00MVWB0_WD-WCAZA1097252 Mar 23 19:19:48 Tower emhttp: pci-0000:00:1f.5-scsi-1:0:0:0 host10 (sdf) WDC_WD20EARS-00MVWB0_WD-WMAZA2769039 Mar 23 19:19:48 Tower emhttp: pci-0000:06:00.0-scsi-1:0:0:0 host4 (sda) WDC_WD5000AAKS-00YGA0_WD-WCAS80645836 Mar 23 19:19:48 Tower emhttp: shcmd (2): modprobe -rw md-mod 2>&1 | logger Mar 23 19:19:48 Tower emhttp: shcmd (3): modprobe md-mod super=/boot/config/super.dat slots=8,16,8,48,8,32,0,0,0,0,8,80,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 2>&1 | logger Mar 23 19:19:48 Tower kernel: xor: automatically using best checksumming function: pIII_sse Mar 23 19:19:48 Tower kernel: pIII_sse : 10026.000 MB/sec Mar 23 19:19:48 Tower kernel: xor: using function: pIII_sse (10026.000 MB/sec) Mar 23 19:19:48 Tower emhttp: Spinning up all drives... Mar 23 19:19:48 Tower emhttp: shcmd (4): /usr/sbin/hdparm -S0 /dev/sda >/dev/null Mar 23 19:19:48 Tower kernel: md: unRAID driver 0.95.4 installed Mar 23 19:19:48 Tower kernel: md: import disk0: [8,16] (sdb) WDC WD20EARS-00M WD-WCAZA1227437 offset: 63 size: 1953514552 Mar 23 19:19:48 Tower kernel: md: import disk1: [8,48] (sdd) WDC WD20EARS-00M WD-WCAZA1097252 offset: 63 size: 1953510424 Mar 23 19:19:48 Tower kernel: md: import disk2: [8,32] (sdc) WDC WD20EARS-00M WD-WCAZA1226695 offset: 63 size: 1953514552 Mar 23 19:19:48 Tower kernel: md: disk3 missing Mar 23 19:19:48 Tower kernel: md: disk4 removed Mar 23 19:19:48 Tower kernel: md: import disk5: [8,80] (sdf) WDC WD20EARS-00M WD-WMAZA2769039 offset: 63 size: 1953514552 Mar 23 19:19:48 Tower kernel: mdcmd (2): set md_num_stripes 1280 Mar 23 19:19:48 Tower kernel: mdcmd (3): set md_write_limit 768 Mar 23 19:19:48 Tower kernel: mdcmd (4): set md_sync_window 288 Mar 23 19:19:48 Tower kernel: mdcmd (5): set spinup_group 0 0 Mar 23 19:19:48 Tower kernel: mdcmd (6): set spinup_group 1 4 Mar 23 19:19:48 Tower kernel: mdcmd (7): set spinup_group 2 2 Mar 23 19:19:48 Tower kernel: mdcmd (: set spinup_group 5 0 Mar 23 19:19:48 Tower kernel: mdcmd (9): spinup 0 Mar 23 19:19:48 Tower kernel: mdcmd (10): spinup 1 Mar 23 19:19:48 Tower kernel: mdcmd (11): spinup 2 Mar 23 19:19:48 Tower kernel: mdcmd (12): spinup 5 Mar 23 19:19:48 Tower emhttp: stale configuration Mar 23 19:19:48 Tower emhttp: shcmd (5): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Mar 23 19:19:48 Tower emhttp: _shcmd: shcmd (5): exit status: 1 Mar 23 19:19:48 Tower emhttp: shcmd (6): cp /etc/exports- /etc/exports Mar 23 19:19:48 Tower emhttp: shcmd (7): killall -HUP smbd Mar 23 19:19:48 Tower emhttp: shcmd (: /etc/rc.d/rc.nfsd restart | logger Mar 23 19:19:49 Tower emhttp: shcmd (: cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root Mar 23 19:19:49 Tower emhttp: shcmd (9): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root Mar 23 19:19:49 Tower emhttp: shcmd (10): echo '0 */1 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root Mar 23 19:19:49 Tower emhttp: shcmd (11): crontab /var/spool/cron/crontabs/root Mar 23 19:19:56 Tower init: Re-reading inittab
March 24, 201115 yr Author Hello, Thanks for the help, I think I got things back on track after reading this post: Moving drives around [solved] I followed some of the advice on this posting and I am starting to wonder if I have a bad Icy Dock multi-bay cage. I moved the drives down to the bottom icy dock and they both came up and are starting to go through the steps. I am not 100% yet, they are 2.TB each so it will take a few hours to see if everything is 100 % attachment is the new log file. I do have the old ones also. Array_started_again.txt
March 24, 201115 yr OK, I'm trying to not sound like an ass but read and understand this; IT IS NOT POSSIBLE TO RECOVER FROM 2 FAILED DRIVES IN unRAID. PARITY WILL NOT HELP WITH 2 FAILED DRIVES. FORMATTING WILL NOT HELP RECOVER ANY DATA. YOU HAVE GONE BEYOND THE CAPABILITY OF unRAID TO RECOVER YOUR DATA. Normally, when you install a replacement disk unRAID will ask if you are sure you want to rebuild the old disk data onto the new one. You check a box and start the array. There is no question of formatting the drive. You must have futzed around with the interface and attempting to start enough times you got unRAID to believe one of the replacement drives is a correct working data drive. It is certainly not a proper data drive. When 1 drive fails unRAID MUST use every other drive AND the parity drive to recover the failed drive. If you have another missing drive then it is NOT possible to recover either failed drive. You are being very persistant trying to make the impossible work. Please give up because data recovery will not happen. Now that is hopefully clear, your last syslog shows that disk4 has been replaced but disk3 appears to have been recognized as the valid proper disk3, which it is not. According to you second last syslog, disk3 was missing and disk4 was removed. I believe you posted it was unassigned from the devices page while you attempted to "format" disk3. You need to do one of 2 things; Get the old disks working again so you can recover the data off them. You can either mount the drives outside of the array and see what they hold or initconfig the array with the old original disks, placed in working drive bays and properly assigned, and cross your fingers and see what happens. Give up on the data on the old disks and initconfig the current array. You will keep the data on the remaining original drives and get 2 new empty ones. DO NOT press the format button if any of the original data drives show as unformatted. Peter
March 24, 201115 yr I just wanted to add this. If you would install unMENU then you can easily use it to attempt to mount and network share the 2 failed drives. Attempting to mount and examine the drives outside of the array is the safest thing to try right now if you want to recovery the data off them. Knowing the current state of the original drives can change the ways you can attempt to recover the data. I believe there is instructions on how to mount a drive in the WIKI if you want to do it that way. Peter
March 24, 201115 yr Author I see your point and I kinda of figured I will lose some data. If all I will lose is the failed drive data, I could live with that. I will try to get the data from the old drives that where replaced for bigger drives later. O.k. new problems, used the initconfig, The discs I place back in are showing orange, what does orange mean? array starts and it looks like things will be back to normal? but I gave it over night to sync and join the discs. the disc are showing unformatted now. I have prior to you mentioning not to hit format, hit the format button to get the disc to become normal. Here is part of the syslog: Mar 23 21:22:03 Tower emhttp: _shcmd: shcmd (127): exit status: 32 Mar 23 21:22:03 Tower emhttp: disk3 mount error: 32 Mar 23 21:22:03 Tower emhttp: shcmd (128): rmdir /mnt/disk3 Mar 23 21:22:03 Tower kernel: REISERFS warning (device md4): sh-2006 read_super_block: bread failed (dev md4, block 2, size 4096) Mar 23 21:22:03 Tower kernel: REISERFS warning (device md4): sh-2006 read_super_block: bread failed (dev md4, block 16, size 4096) Mar 23 21:22:03 Tower kernel: REISERFS warning (device md4): sh-2021 reiserfs_fill_super: can not find reiserfs on md4 Mar 23 21:22:03 Tower kernel: REISERFS warning (device md3): sh-2006 read_super_block: bread failed (dev md3, block 2, size 4096) Mar 23 21:22:03 Tower kernel: REISERFS warning (device md3): sh-2006 read_super_block: bread failed (dev md3, block 16, size 4096) Mar 23 21:22:03 Tower kernel: REISERFS warning (device md3): sh-2021 reiserfs_fill_super: can not find reiserfs on md3 Mar 23 21:22:03 Tower kernel: REISERFS (device sdc1): found reiserfs format "3.6" with standard journal Mar 23 21:22:03 Tower kernel: REISERFS (device sdc1): using ordered data mode Mar 23 21:22:03 Tower kernel: REISERFS (device sdc1): journal params: device sdc1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Mar 23 21:22:03 Tower kernel: REISERFS (device sdc1): checking transaction log (sdc1) Mar 23 21:22:03 Tower kernel: md: recovery thread has nothing to resync Mar 23 21:22:03 Tower kernel: REISERFS (device sdc1): Using r5 hash to sort names Mar 23 21:22:08 Tower unmenu-status: Starting unmenu web-server Mar 23 21:22:08 Tower unmenu[16353]: awk: ./unmenu.awk:286: fatal: can't open two way socket `/inet/tcp/8080/0/0' for input/output (No such file or directory) Mar 23 21:22:08 Tower unmenu-status: Exiting unmenu web-server, exit status code = 2 Mar 23 21:22:08 Tower unmenu[16353]: unmenu.awk unable to open port. It may already be running Mar 23 21:22:10 Tower kernel: REISERFS (device md5): found reiserfs format "3.6" with standard journal Mar 23 21:22:10 Tower kernel: REISERFS (device md5): using ordered data mode Mar 23 21:22:10 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal Mar 23 21:22:10 Tower kernel: REISERFS (device md2): using ordered data mode Mar 23 21:22:10 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal Mar 23 21:22:10 Tower kernel: REISERFS (device md1): using ordered data mode Mar 23 21:22:10 Tower kernel: REISERFS (device md5): journal params: device md5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Mar 23 21:22:10 Tower kernel: REISERFS (device md5): checking transaction log (md5) Mar 23 21:22:10 Tower kernel: REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Mar 23 21:22:10 Tower kernel: REISERFS (device md2): checking transaction log (md2) Mar 23 21:22:10 Tower kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Mar 23 21:22:10 Tower kernel: REISERFS (device md1): checking transaction log (md1) Mar 23 21:22:11 Tower kernel: REISERFS (device md5): Using r5 hash to sort names Mar 23 21:22:11 Tower kernel: REISERFS (device md1): Using r5 hash to sort names Mar 23 21:22:11 Tower kernel: REISERFS (device md2): Using r5 hash to sort names Mar 23 21:22:11 Tower emhttp: shcmd (134): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Mar 23 21:22:11 Tower emhttp: shcmd (135): cp /etc/exports- /etc/exports Mar 23 21:22:11 Tower emhttp: shcmd (136): mkdir /mnt/user Mar 23 21:22:11 Tower emhttp: shcmd (137): /usr/local/sbin/shfs /mnt/user -cache 1 -floor 2000000 -o noatime,big_writes,allow_other,default_permissions Mar 23 21:22:11 Tower emhttp: shcmd (138): mkdir /mnt/user0 Mar 23 21:22:11 Tower emhttp: shcmd (139): /usr/local/sbin/shfs /mnt/user0 -cache 0 -o noatime,big_writes,allow_other,default_permissions Mar 23 21:22:12 Tower emhttp: get_config_idx: fopen /boot/config/shares/mysql.cfg: No such file or directory - assigning defaults Mar 23 21:22:12 Tower emhttp: shcmd (140): killall -HUP smbd Mar 23 21:22:12 Tower emhttp: shcmd (141): /etc/rc.d/rc.nfsd restart | logger Mar 23 21:22:18 Tower unmenu-status: Starting unmenu web-server Mar 23 21:22:18 Tower unmenu[16353]: awk: ./unmenu.awk:286: fatal: can't open two way socket `/inet/tcp/8080/0/0' for input/output (No such file or directory) Mar 23 21:22:18 Tower unmenu-status: Exiting unmenu web-server, exit status code = 2 Mar 23 21:22:18 Tower unmenu-error: Fatal error:Exiting uu, unmenu may already be running, exit status=2 Mar 23 21:24:31 Tower kernel: mdcmd (879): check Mar 23 21:24:31 Tower kernel: md: recovery thread woken up ... Mar 23 21:24:31 Tower kernel: md: recovery thread has nothing to resync Mar 23 21:37:58 Tower kernel: mdcmd (975): clear Mar 23 22:00:01 Tower logger: mover started Mar 23 22:00:01 Tower logger: . Mar 23 22:00:01 Tower logger: mover finished Mar 23 23:00:01 Tower logger: mover started Mar 23 23:00:01 Tower logger: . Mar 23 23:00:02 Tower logger: mover finished Mar 24 00:00:01 Tower logger: mover started Mar 24 00:00:01 Tower logger: . Mar 24 00:00:02 Tower logger: mover finished Mar 24 01:00:01 Tower logger: mover started Mar 24 01:00:01 Tower logger: . Mar 24 01:00:02 Tower logger: mover finished Mar 24 02:00:01 Tower logger: mover started Mar 24 02:00:01 Tower logger: . Mar 24 02:00:02 Tower logger: mover finished Mar 24 03:00:01 Tower logger: mover started Mar 24 03:00:01 Tower logger: . Mar 24 03:00:01 Tower logger: mover finished Mar 24 04:00:01 Tower logger: mover started Mar 24 04:00:01 Tower logger: . Mar 24 04:00:01 Tower logger: mover finished Mar 24 05:00:01 Tower logger: mover started Mar 24 05:00:01 Tower logger: . Mar 24 05:00:01 Tower logger: mover finished Mar 24 06:00:01 Tower logger: mover started Mar 24 06:00:01 Tower logger: . Mar 24 06:00:02 Tower logger: mover finished Mar 24 07:00:01 Tower logger: mover started Mar 24 07:00:01 Tower logger: . Mar 24 07:00:02 Tower logger: mover finished Thanks for the sound advice, Dan 0-24-2011.txt
March 24, 201115 yr See this page: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems
March 25, 201115 yr Author Thanks for the help: The real reason for the drives failing was the Icy Dock Bays going bad. Have a new one on order and my array is back to 100%. I was sure glade I didn't use the 500gb drives for something before this happened. You could mark this as being solved
March 25, 201115 yr I have prior to you mentioning not to hit format, hit the format button to get the disc to become normal. Thanks for the sound advice, Dan Dan, read the line again. "original disks" = disk which was in the array before the problems occurred and that has data on it. Peter
Archived
This topic is now archived and is closed to further replies.