RobJ Posted September 18, 2014 Share Posted September 18, 2014 The last syslog posted was booted at Sep 13 10:01:53, with UnRAID v6.0-beta9 with unraidsafemode set, has 18 data drives, a cache drive, and a parity drive connected to the 4th port of the first SAS card (sdk, sd 1:0:3:0, ata10.00). Perhaps there is another syslog? Sep 13 10:01:53 Tower kernel: ahci 0000:00:1f.2: version 3.0 these are the 6 motherboard ports Sep 13 10:01:53 Tower kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 3 Gbps 0x3f impl SATA mode Sep 13 10:01:53 Tower kernel: ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pmp pio slum part ems sxs apst Sep 13 10:01:53 Tower kernel: scsi2 : ahci Sep 13 10:01:53 Tower kernel: scsi3 : ahci Sep 13 10:01:53 Tower kernel: scsi4 : ahci Sep 13 10:01:53 Tower kernel: scsi5 : ahci Sep 13 10:01:53 Tower kernel: scsi6 : ahci Sep 13 10:01:53 Tower kernel: scsi7 : ahci Sep 13 10:01:53 Tower kernel: ata1: SATA max UDMA/133 abar m2048@0xf79f3000 port 0xf79f3100 irq 41 Sep 13 10:01:53 Tower kernel: ata2: SATA max UDMA/133 abar m2048@0xf79f3000 port 0xf79f3180 irq 41 Sep 13 10:01:53 Tower kernel: ata3: SATA max UDMA/133 abar m2048@0xf79f3000 port 0xf79f3200 irq 41 Sep 13 10:01:53 Tower kernel: ata4: SATA max UDMA/133 abar m2048@0xf79f3000 port 0xf79f3280 irq 41 Sep 13 10:01:53 Tower kernel: ata5: SATA max UDMA/133 abar m2048@0xf79f3000 port 0xf79f3300 irq 41 Sep 13 10:01:53 Tower kernel: ata6: SATA max UDMA/133 abar m2048@0xf79f3000 port 0xf79f3380 irq 41 here, 6 drives are set up, sd 2:0:0:0: [sdb] through sd 7:0:0:0: [sdg] ... Sep 13 10:01:53 Tower kernel: Fusion MPT base driver 3.04.20 Sep 13 10:01:53 Tower kernel: Copyright © 1999-2008 LSI Corporation Sep 13 10:01:53 Tower kernel: Fusion MPT SAS Host driver 3.04.20 Sep 13 10:01:53 Tower kernel: mptbase: ioc0: Initiating bringup Sep 13 10:01:53 Tower kernel: mvsas 0000:02:00.0: mvsas: driver version 0.8.16 Sep 13 10:01:53 Tower kernel: mvsas 0000:02:00.0: mvsas: PCI-E x4, Bandwidth Usage: 2.5 Gbps ... Sep 13 10:01:53 Tower kernel: ioc0: LSISAS1068E B3: Capabilities={Initiator} ... Sep 13 10:01:53 Tower kernel: scsi1 : mvsas first SAS card, apparently 6 ports, 6 drives attached Sep 13 10:01:53 Tower kernel: sas: phy-1:0 added to port-1:0, phy_mask:0x1 ( 0) Sep 13 10:01:53 Tower kernel: sas: phy-1:1 added to port-1:1, phy_mask:0x2 ( 100000000000000) Sep 13 10:01:53 Tower kernel: sas: phy-1:2 added to port-1:2, phy_mask:0x4 ( 200000000000000) Sep 13 10:01:53 Tower kernel: sas: phy-1:3 added to port-1:3, phy_mask:0x8 ( 300000000000000) Sep 13 10:01:53 Tower kernel: sas: phy-1:4 added to port-1:4, phy_mask:0x10 ( 400000000000000) Sep 13 10:01:53 Tower kernel: sas: phy-1:6 added to port-1:5, phy_mask:0x40 ( 600000000000000) here, 6 drives are set up, sd 1:0:0:0: [sdh] through sd 1:0:5:0: [sdm] ... Sep 13 10:01:53 Tower kernel: scsi 1:0:3:0: Direct-Access ATA WDC WD30EFRX-68E 0A80 PQ: 0 ANSI: 5 Parity drive, 4th port Sep 13 10:01:53 Tower kernel: sd 1:0:3:0: [sdk] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) ... Sep 13 10:01:53 Tower kernel: scsi8 : ioc0: LSISAS1068E B3, FwRev=01200000h, Ports=1, MaxQ=483, IRQ=16 second SAS card, apparently 8 ports, 8 drives attached Sep 13 10:01:53 Tower kernel: mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 5, phy 0, sas_addr 0x455f383ddbb4b28e here, 8 drives are set up, sd 8:0:0:0: [sdn] through sd 8:0:7:0: [sdu] ... Sep 13 10:01:56 Tower emhttp: WDC_WD30EFRX-68EUZN0_WD-WCC4N1032741 (sdk) 2930266584 ... Sep 13 10:01:56 Tower kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68EUZN0_WD-WCC4N1032741 size: 2930266532 sdk is assigned as Parity (disk0) Didn't mean to bury you in detail, but thought the extra might help you understand what to look for. Hope this helps... Quote Link to comment
jonp Posted September 19, 2014 Share Posted September 19, 2014 Just an FYI, we are actively monitoring this thread here at Lime Tech. From all the bright minds in here helping, it seems fairly clear to me that this is a hardware issue, but will continue to monitor as this progresses and involve Tom if and when necessary. Thanks! Quote Link to comment
MrLondon Posted September 20, 2014 Author Share Posted September 20, 2014 RobJ, sorry I changed the parity disk to another 3TB drive and the old parity drive was connected to the motherboard the new parity was not. So now I connected the new parity disk to the motherboard and started the parity sync again will see if that now goes through. Parity building is currently at 30% and no errors yet. Quote Link to comment
MrLondon Posted September 21, 2014 Author Share Posted September 21, 2014 Parity finally completed this morning after connecting the parity drive to the motherboards sata port and connecting a data drive to the AOC controller Quote Link to comment
RobJ Posted September 25, 2014 Share Posted September 25, 2014 Well you now have a partner, a fellow sufferer, with almost identical failure. You might want to read his thread also. I've posted some ideas here. Quote Link to comment
dgaschk Posted September 25, 2014 Share Posted September 25, 2014 See check disk file systems in my sig. Quote Link to comment
dgaschk Posted September 25, 2014 Share Posted September 25, 2014 Which model PSU? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.