Jump to content

Unmountable drive (need help)

united418

By united418
in General Support

Recommended Posts

united418 Noob

united418

Posted
Posted

Hi,

 

I've just updated all my hardware system and I don'T know why but in the first boot of my new rig everything was fine. All drive are up and running. I made some change on Bios , change Sata pcie card etc.. and now I got two drive that are now unmountable.

 

Disk 2 • WDC_WD20EARS-00J2GB0_WD-WCAYY0147710 (sde)

Disk 5 • WDC_WD20EARS-00J2GB0_WD-WCAYY0150613 (sdd)

 

FYI

Unraid 6.1.9

Mobo: MSI Krait Gaming

CPU: I7-6700K

MEM: 32gb DDR4

5 drive in array

1 parity 4tb

1 cache SSD

1 unassigne SSD for VMs

 

Mobo got 6 sata port and I have a PCIE with 2 sata port.

 

I'Ve try different setup with sata cable , changing sata port of each drive etc..

 

What i can tell you is that the two unmountable drive was first of all on the PCIE Sata card during multiple reboot for fine tuning the new hardware.

I guess something got wrong with the PCIE Sata card and each drive got now error.

 

I've swap the drive with two other , place it directly on the onboard sata port and they still unmountable and those on the PCIE card work perfectly.

 

Anyone could help me for getting back those 2 drives?

 

root@UFTP-Tower:~# cat /var/log/syslog
May 12 19:48:43 UFTP-Tower kernel: scsi 0:0:0:0: Direct-Access     Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2
May 12 19:48:43 UFTP-Tower kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
May 12 19:48:43 UFTP-Tower kernel: sd 0:0:0:0: [sda] 3911616 512-byte logical blocks: (2.00 GB/1.86 GiB)
May 12 19:48:43 UFTP-Tower kernel: sd 0:0:0:0: [sda] Write Protect is off
May 12 19:48:43 UFTP-Tower kernel: sd 0:0:0:0: [sda] Mode Sense: 16 03 09 51
May 12 19:48:43 UFTP-Tower kernel: sd 0:0:0:0: [sda] Incomplete mode parameter data
May 12 19:48:43 UFTP-Tower kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
May 12 19:48:43 UFTP-Tower kernel: sda: sda1
May 12 19:48:43 UFTP-Tower kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk
May 12 19:48:43 UFTP-Tower kernel: floppy0: no floppy controllers found
May 12 19:48:43 UFTP-Tower kernel: Freeing unused kernel memory: 916K (ffffffff8188f000 - ffffffff81974000)
May 12 19:48:43 UFTP-Tower kernel: sata_sil24 0000:08:00.0: version 1.1
May 12 19:48:43 UFTP-Tower kernel: sata_via 0000:07:00.0: version 2.6
May 12 19:48:43 UFTP-Tower kernel: pps_core: LinuxPPS API ver. 1 registered
May 12 19:48:43 UFTP-Tower kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
May 12 19:48:43 UFTP-Tower kernel: ACPI Warning: SystemIO range 0x000000000000F040-0x000000000000F05F conflicts with OpRegion 0x000000000000F040-0x000000000000F04F (\_SB_.PCI0.SBUS.SMBI) (20150410/utaddress-254)
May 12 19:48:43 UFTP-Tower kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
May 12 19:48:43 UFTP-Tower kernel: ahci 0000:00:17.0: version 3.0
May 12 19:48:43 UFTP-Tower kernel: sata_via 0000:07:00.0: routed to hard irq line 11
May 12 19:48:43 UFTP-Tower kernel: scsi host1: sata_sil24
May 12 19:48:43 UFTP-Tower kernel: scsi host2: sata_sil24
May 12 19:48:43 UFTP-Tower kernel: ata1: SATA max UDMA/100 host m128@0xdf184000 port 0xdf180000 irq 17
May 12 19:48:43 UFTP-Tower kernel: ata2: SATA max UDMA/100 host m128@0xdf184000 port 0xdf182000 irq 17
May 12 19:48:43 UFTP-Tower kernel: ahci 0000:00:17.0: AHCI 0001.0301 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
May 12 19:48:43 UFTP-Tower kernel: ahci 0000:00:17.0: flags: 64bit ncq sntf led clo only pio slum part ems deso sadm sds apst
May 12 19:48:43 UFTP-Tower kernel: scsi host3: sata_via
May 12 19:48:43 UFTP-Tower kernel: scsi host4: sata_via
May 12 19:48:43 UFTP-Tower kernel: scsi host5: sata_via
May 12 19:48:43 UFTP-Tower kernel: ata3: SATA max UDMA/133 port i16@0xc150 bmdma 0xc100 irq 18
May 12 19:48:43 UFTP-Tower kernel: ata4: SATA max UDMA/133 port i16@0xc140 bmdma 0xc108 irq 18
May 12 19:48:43 UFTP-Tower kernel: ata5: PATA max UDMA/133 port i16@0xc130 bmdma 0xc110 irq 18
May 12 19:48:43 UFTP-Tower kernel: PTP clock support registered
May 12 19:48:43 UFTP-Tower kernel: e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
May 12 19:48:43 UFTP-Tower kernel: e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
May 12 19:48:43 UFTP-Tower kernel: scsi host6: ahci
May 12 19:48:43 UFTP-Tower kernel: scsi host7: ahci
May 12 19:48:43 UFTP-Tower kernel: scsi host8: ahci
May 12 19:48:43 UFTP-Tower kernel: scsi host9: ahci
May 12 19:48:43 UFTP-Tower kernel: scsi host10: ahci
May 12 19:48:43 UFTP-Tower kernel: scsi host11: ahci
May 12 19:48:43 UFTP-Tower kernel: ata6: SATA max UDMA/133 abar m2048@0xdf54c000 port 0xdf54c100 irq 132
May 12 19:48:43 UFTP-Tower kernel: ata7: SATA max UDMA/133 abar m2048@0xdf54c000 port 0xdf54c180 irq 132
May 12 19:48:43 UFTP-Tower kernel: ata8: SATA max UDMA/133 abar m2048@0xdf54c000 port 0xdf54c200 irq 132
May 12 19:48:43 UFTP-Tower kernel: ata9: SATA max UDMA/133 abar m2048@0xdf54c000 port 0xdf54c280 irq 132
May 12 19:48:43 UFTP-Tower kernel: ata10: SATA max UDMA/133 abar m2048@0xdf54c000 port 0xdf54c300 irq 132
May 12 19:48:43 UFTP-Tower kernel: ata11: SATA max UDMA/133 abar m2048@0xdf54c000 port 0xdf54c380 irq 132
May 12 19:48:43 UFTP-Tower kernel: e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
May 12 19:48:43 UFTP-Tower kernel: e1000e 0000:00:1f.6 eth0: registered PHC clock
May 12 19:48:43 UFTP-Tower kernel: e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) d8:cb:8a:e0:c4:df
May 12 19:48:43 UFTP-Tower kernel: e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
May 12 19:48:43 UFTP-Tower kernel: e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF
May 12 19:48:43 UFTP-Tower kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 12 19:48:43 UFTP-Tower kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May 12 19:48:43 UFTP-Tower kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May 12 19:48:43 UFTP-Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May 12 19:48:43 UFTP-Tower kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 12 19:48:43 UFTP-Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 12 19:48:43 UFTP-Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 12 19:48:43 UFTP-Tower kernel: ata8.00: ATA-9: WDC WD40EZRX-00SPEB0,      WD-WCC4E5DXDAJ1, 80.00A80, max UDMA/133
May 12 19:48:43 UFTP-Tower kernel: ata8.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
May 12 19:48:43 UFTP-Tower kernel: ata9.00: ATA-9: WDC WD40EZRX-00SPEB0,      WD-WCC4E5CY55K7, 80.00A80, max UDMA/133
May 12 19:48:43 UFTP-Tower kernel: ata9.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
May 12 19:48:43 UFTP-Tower kernel: ata8.00: configured for UDMA/133
May 12 19:48:43 UFTP-Tower kernel: ata9.00: configured for UDMA/133
May 12 19:48:43 UFTP-Tower kernel: ata7.00: ATA-8: WDC WD20EARS-00J2GB0,      WD-WCAYY0147710, 80.00A80, max UDMA/133
May 12 19:48:43 UFTP-Tower kernel: ata7.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
May 12 19:48:43 UFTP-Tower kernel: ata6.00: ATA-8: WDC WD20EARS-00J2GB0,      WD-WCAYY0150613, 80.00A80, max UDMA/133
May 12 19:48:43 UFTP-Tower kernel: ata6.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
May 12 19:48:43 UFTP-Tower kernel: ata3.00: ATA-8: KINGSTON SV300S37A120G, 50026B774B04F686, 580ABBF0, max UDMA/133
May 12 19:48:43 UFTP-Tower kernel: ata3.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 0/32)
May 12 19:48:43 UFTP-Tower kernel: ata10.00: ATA-8: WDC WD20EARS-00MVWB0,      WD-WMAZA3781136, 51.0AB51, max UDMA/133
May 12 19:48:43 UFTP-Tower kernel: ata10.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
May 12 19:48:43 UFTP-Tower kernel: ata11.00: ATA-8: WDC WD20EARX-00PASB0,      WD-WMAZA9131213, 51.0AB51, max UDMA/133
May 12 19:48:43 UFTP-Tower kernel: ata11.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
May 12 19:48:43 UFTP-Tower kernel: ata7.00: configured for UDMA/133
May 12 19:48:43 UFTP-Tower kernel: ata6.00: configured for UDMA/133
May 12 19:48:43 UFTP-Tower kernel: ata10.00: configured for UDMA/133
May 12 19:48:43 UFTP-Tower kernel: ata11.00: configured for UDMA/133
May 12 19:48:43 UFTP-Tower kernel: ata3.00: configured for UDMA/133
May 12 19:48:43 UFTP-Tower kernel: ata1: SATA link down (SStatus 0 SControl 0)
May 12 19:48:43 UFTP-Tower kernel: ata2: SATA link down (SStatus 0 SControl 0)
May 12 19:48:43 UFTP-Tower kernel: scsi 3:0:0:0: Direct-Access     ATA      KINGSTON SV300S3 BBF0 PQ: 0 ANSI: 5
May 12 19:48:43 UFTP-Tower kernel: sd 3:0:0:0: [sdb] 234441648 512-byte logical blocks: (120 GB/112 GiB)
May 12 19:48:43 UFTP-Tower kernel: sd 3:0:0:0: Attached scsi generic sg1 type 0
May 12 19:48:43 UFTP-Tower kernel: sd 3:0:0:0: [sdb] Write Protect is off
May 12 19:48:43 UFTP-Tower kernel: sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
May 12 19:48:43 UFTP-Tower kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 12 19:48:43 UFTP-Tower kernel: sdb: sdb1
May 12 19:48:43 UFTP-Tower kernel: sd 3:0:0:0: [sdb] Attached SCSI disk
May 12 19:48:43 UFTP-Tower kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 12 19:48:43 UFTP-Tower kernel: ata4.00: ATA-9: CT480BX200SSD1, 1542F00E9079, MU01.4, max UDMA/133
May 12 19:48:43 UFTP-Tower kernel: ata4.00: 937703088 sectors, multi 1: LBA48 NCQ (depth 0/32)
May 12 19:48:43 UFTP-Tower kernel: ata4.00: configured for UDMA/133
May 12 19:48:43 UFTP-Tower kernel: scsi 4:0:0:0: Direct-Access     ATA      CT480BX200SSD1   .4   PQ: 0 ANSI: 5
May 12 19:48:43 UFTP-Tower kernel: sd 4:0:0:0: Attached scsi generic sg2 type 0
May 12 19:48:43 UFTP-Tower kernel: sd 4:0:0:0: [sdc] 937703088 512-byte logical blocks: (480 GB/447 GiB)
May 12 19:48:43 UFTP-Tower kernel: sd 4:0:0:0: [sdc] 4096-byte physical blocks
May 12 19:48:43 UFTP-Tower kernel: sd 4:0:0:0: [sdc] Write Protect is off
May 12 19:48:43 UFTP-Tower kernel: sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
May 12 19:48:43 UFTP-Tower kernel: sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 12 19:48:43 UFTP-Tower kernel: sdc: sdc1
May 12 19:48:43 UFTP-Tower kernel: sd 4:0:0:0: [sdc] Attached SCSI disk
May 12 19:48:43 UFTP-Tower kernel: scsi 6:0:0:0: Direct-Access     ATA      WDC WD20EARS-00J 0A80 PQ: 0 ANSI: 5
May 12 19:48:43 UFTP-Tower kernel: sd 6:0:0:0: Attached scsi generic sg3 type 0
May 12 19:48:43 UFTP-Tower kernel: sd 6:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
May 12 19:48:43 UFTP-Tower kernel: sd 6:0:0:0: [sdd] Write Protect is off
May 12 19:48:43 UFTP-Tower kernel: sd 6:0:0:0: [sdd] Mode Sense: 00 3a 00 00
May 12 19:48:43 UFTP-Tower kernel: scsi 7:0:0:0: Direct-Access     ATA      WDC WD20EARS-00J 0A80 PQ: 0 ANSI: 5
May 12 19:48:43 UFTP-Tower kernel: sd 6:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 12 19:48:43 UFTP-Tower kernel: sd 7:0:0:0: Attached scsi generic sg4 type 0
May 12 19:48:43 UFTP-Tower kernel: sd 7:0:0:0: [sde] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
May 12 19:48:43 UFTP-Tower kernel: sd 7:0:0:0: [sde] Write Protect is off
May 12 19:48:43 UFTP-Tower kernel: sd 7:0:0:0: [sde] Mode Sense: 00 3a 00 00
May 12 19:48:43 UFTP-Tower kernel: sd 7:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 12 19:48:43 UFTP-Tower kernel: scsi 8:0:0:0: Direct-Access     ATA      WDC WD40EZRX-00S 0A80 PQ: 0 ANSI: 5
May 12 19:48:43 UFTP-Tower kernel: sd 8:0:0:0: [sdf] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
May 12 19:48:43 UFTP-Tower kernel: sd 8:0:0:0: Attached scsi generic sg5 type 0
May 12 19:48:43 UFTP-Tower kernel: scsi 9:0:0:0: Direct-Access     ATA      WDC WD40EZRX-00S 0A80 PQ: 0 ANSI: 5
May 12 19:48:43 UFTP-Tower kernel: sd 9:0:0:0: [sdg] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
May 12 19:48:43 UFTP-Tower kernel: sd 9:0:0:0: [sdg] 4096-byte physical blocks
May 12 19:48:43 UFTP-Tower kernel: sd 9:0:0:0: Attached scsi generic sg6 type 0
May 12 19:48:43 UFTP-Tower kernel: sd 9:0:0:0: [sdg] Write Protect is off
May 12 19:48:43 UFTP-Tower kernel: sd 9:0:0:0: [sdg] Mode Sense: 00 3a 00 00
May 12 19:48:43 UFTP-Tower kernel: sd 9:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 12 19:48:43 UFTP-Tower kernel: scsi 10:0:0:0: Direct-Access     ATA      WDC WD20EARS-00M AB51 PQ: 0 ANSI: 5
May 12 19:48:43 UFTP-Tower kernel: sd 10:0:0:0: Attached scsi generic sg7 type 0
May 12 19:48:43 UFTP-Tower kernel: sd 10:0:0:0: [sdh] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
May 12 19:48:43 UFTP-Tower kernel: sd 10:0:0:0: [sdh] 4096-byte physical blocks
May 12 19:48:43 UFTP-Tower kernel: sd 10:0:0:0: [sdh] Write Protect is off
May 12 19:48:43 UFTP-Tower kernel: sd 10:0:0:0: [sdh] Mode Sense: 00 3a 00 00
May 12 19:48:43 UFTP-Tower kernel: sd 10:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 12 19:48:43 UFTP-Tower kernel: scsi 11:0:0:0: Direct-Access     ATA      WDC WD20EARX-00P AB51 PQ: 0 ANSI: 5
May 12 19:48:43 UFTP-Tower kernel: sd 11:0:0:0: [sdi] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
May 12 19:48:43 UFTP-Tower kernel: sd 11:0:0:0: [sdi] 4096-byte physical blocks
May 12 19:48:43 UFTP-Tower kernel: sd 11:0:0:0: Attached scsi generic sg8 type 0
May 12 19:48:43 UFTP-Tower kernel: sd 11:0:0:0: [sdi] Write Protect is off
May 12 19:48:43 UFTP-Tower kernel: sd 11:0:0:0: [sdi] Mode Sense: 00 3a 00 00
May 12 19:48:43 UFTP-Tower kernel: sd 11:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 12 19:48:43 UFTP-Tower kernel: sd 8:0:0:0: [sdf] 4096-byte physical blocks
May 12 19:48:43 UFTP-Tower kernel: sd 8:0:0:0: [sdf] Write Protect is off
May 12 19:48:43 UFTP-Tower kernel: sd 8:0:0:0: [sdf] Mode Sense: 00 3a 00 00
May 12 19:48:43 UFTP-Tower kernel: sd 8:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 12 19:48:43 UFTP-Tower kernel: sdd: sdd1
May 12 19:48:43 UFTP-Tower kernel: sd 6:0:0:0: [sdd] Attached SCSI disk
May 12 19:48:43 UFTP-Tower kernel: sdg: sdg1
May 12 19:48:43 UFTP-Tower kernel: sd 9:0:0:0: [sdg] Attached SCSI disk
May 12 19:48:43 UFTP-Tower kernel: sdf: sdf1
May 12 19:48:43 UFTP-Tower kernel: sd 8:0:0:0: [sdf] Attached SCSI disk
May 12 19:48:43 UFTP-Tower kernel: sde: sde1
May 12 19:48:43 UFTP-Tower kernel: sd 7:0:0:0: [sde] Attached SCSI disk
May 12 19:48:43 UFTP-Tower kernel: random: nonblocking pool is initialized
May 12 19:48:43 UFTP-Tower kernel: sdh: sdh1
May 12 19:48:43 UFTP-Tower kernel: sd 10:0:0:0: [sdh] Attached SCSI disk
May 12 19:48:43 UFTP-Tower kernel: sdi: sdi1
May 12 19:48:43 UFTP-Tower kernel: sd 11:0:0:0: [sdi] Attached SCSI disk

 

PS: I prefer to save the data on it...

Capture2.PNG.507c11849cadea6903f5c29202b02a12.PNG

Link to comment
Squid Grand Master

Squid

Posted
Posted

I could be mistaken (as I'm not a real VM guy), but I see a "KVM" tab on your tabs.  If I'm not mistaken you've got the old KVM manager installed (and it really shouldn't be)

 

And, if I'm right that it shouldn't be there, you might want to install fix common problems to have a quick check as to what else is kicking around that shouldn't still be installed.

Link to comment
united418 Noob

united418

Posted
  • Author
Posted

Squid , I will remove it right away.

 

on my last rig is doesnt cause me any trouble getting the old kvm manager. I use only the VM table in the latest unraid built.

 

it's sure I need to clean up some old plugins as I used unraid since 2-3 years. (not active on forum as I normally troubleshoot everything myself)

 

thanks

Link to comment
united418 Noob

united418

Posted
  • Author
Posted

Update...

 

yesterday i've run a chdsk on one of those drive and it did not give any error.

 

if I try reiserfsck --check , or ----fix-fixable  or -rebuild-tree , i'm always getting this,

 

The problem has occurred looks like a hardware problem. If you have
bad blocks, we advise you to get a new hard drive, because once you
get one bad block  that the disk  drive internals  cannot hide from
your sight,the chances of getting more are generally said to become
much higher  (precise statistics are unknown to us), and  this disk
drive is probably not expensive enough  for you to you to risk your
time and  data on it.  If you don't want to follow that follow that
advice then  if you have just a few bad blocks,  try writing to the
bad blocks  and see if the drive remaps  the bad blocks (that means
it takes a block  it has  in reserve  and allocates  it for use for
of that block number).  If it cannot remap the block,  use badblock
option (-B) with  reiserfs utils to handle this block correctly.

bread: Cannot read the block (2): (Input/output error).

uftp-tower-diagnostics-20160512-2136.zip

Link to comment
JorgeB Grand Master

JorgeB

Posted
Posted

Very bad sata cables/controller:

 

Device Model:     WDC WD20EARS-00J2GB0
Serial Number:    WD-WCAYY0147710
199 UDMA_CRC_Error_Count    0x0032   200   001   000    Old_age   Always       -       1823433

Device Model:     WDC WD20EARS-00J2GB0
Serial Number:    WD-WCAYY0150613
199 UDMA_CRC_Error_Count    0x0032   200   156   000    Old_age   Always       -       661277

 

Replace and try running reiserfsck again.

Link to comment
united418 Noob

united418

Posted
  • Author
Posted

Very bad sata cables/controller:

 

Device Model:     WDC WD20EARS-00J2GB0
Serial Number:    WD-WCAYY0147710
199 UDMA_CRC_Error_Count    0x0032   200   001   000    Old_age   Always       -       1823433

Device Model:     WDC WD20EARS-00J2GB0
Serial Number:    WD-WCAYY0150613
199 UDMA_CRC_Error_Count    0x0032   200   156   000    Old_age   Always       -       661277

 

Replace and try running reiserfsck again.

 

 

I've put the two drive on the onboard sata.

also change cable with brand new one.

 

reseirfs command give same error...

 

attached I put the new log.

 

thanks..

uftp-tower-diagnostics-20160513-0727.zip

Link to comment
united418 Noob

united418

Posted
  • Author
Posted

I believe your best chance is still reiserfsck, try running it on a different pc with only those two disks connected, use an unRAID trial key.

 

it worked!

 

I'm now running reiserfsck --check-fix-fixable on it , i'll wait for the result..

Link to comment
united418 Noob

united418

Posted
  • Author
Posted

everything looks fine after the chdsk.

 

I mount it perfectly on an unraid Trial , my files were available.

 

I put it back in my unraid tower , and still unmountable contents emulated..

 

should I try a new config ? is there's any risk of data loss ?

Link to comment
trurl Grand Master

trurl

Posted
Posted

everything looks fine after the chdsk.

 

I mount it perfectly on an unraid Trial , my files were available.

 

I put it back in my unraid tower , and still unmountable contents emulated..

 

should I try a new config ? is there's any risk of data loss ?

Post a screenshot. Sounds like you must have only one disabled disk and its emulated drive, not the real drive, is unmountable.
Link to comment
united418 Noob

united418

Posted
  • Author
Posted

everything looks fine after the chdsk.

 

I mount it perfectly on an unraid Trial , my files were available.

 

I put it back in my unraid tower , and still unmountable contents emulated..

 

should I try a new config ? is there's any risk of data loss ?

Post a screenshot. Sounds like you must have only one disabled disk and its emulated drive, not the real drive, is unmountable.

Capture3.PNG.ecf7d76b79508012e98563eb645eae68.PNG

Capture4.PNG.e4908dcd5c7ce0076fac742f80a7cb2f.PNG

Link to comment
united418 Noob

united418

Posted
  • Author
Posted

like I said , I mount the two unmountable drive in another PC , with a virgin unraid and I was able to start the array perfectly.

 

return back to my normal PC and they still unmountable. (power/sata cable/sata port .. I tried every possibilities on that)

Link to comment
united418 Noob

united418

Posted
  • Author
Posted

You should do a new config, parity is not valid anyway since the disks filesystem was repaired outside the array.

 

I didn't do any repair on the unraid trial . chdks did not find eny error.Anyway..

 

I did a new config.

All drives get mount  :D

 

parity check is started, i'm pretty everything will be fine after this.

Link to comment
united418 Noob

united418

Posted
  • Author
Posted

You should do a new config, parity is not valid anyway since the disks filesystem was repaired outside the array.

 

I didn't do any repair on the unraid trial . chdks did not find eny error.Anyway..

 

I did a new config.

All drives get mount  :D

 

parity check is started, i'm pretty sure everything will be fine after this.

Link to comment

Archived

This topic is now archived and is closed to further replies.

Go to topic listing
×
×
  • Create New...