@bodhi, Bad news. I was running one 2.5" and one 3.5" in bays 3 and 4 before. Now I followed your instructions and booted with two 3.5" in bays 3 and 4 and got the errors again(1 Hitachi + 1 WD) :( I think you're right about something else may be happening(power management issue, custom work around from Iomega/Lenovo), etc @bodhi and @1000001101000, Here is the lby nialbr - Debian
bodhi, I've found a Lifeline Fosskit zip that seems to contain the GPL code from Iomega/Lenovo for this NAS. Do you think it might help? I'm running some tests with two WD, one Toshiba and one Samsung drives installed, let's see if my suspicious makes sense. Here is the log you asked.. __ __ _ _ | \/ | __ _ _ ____ _____| | |by nialbr - Debian
bodhi, Dunno if it helps or not but I've reverted back to AHCI and tried with two smaller WD spare drives and I had no errors. Seems like an issue with Seagate drives. It's weird because the NAS came with these Seagate drives from factory. Any clue?by nialbr - Debian
bodhi, Now I think it's detecting the disks but not creating the device under /dev/sdX. [ 13.363549][ T170] scsi host3: pata_marvell [ 13.394828][ T170] scsi host4: pata_marvell [ 13.399472][ T170] ata3: PATA max UDMA/100 cmd 0x10010 ctl 0x10020 bmdma 0x10000 irq 38 [ 13.467951][ T170] ata4: PATA max UDMA/133 cmd 0x10018 ctl 0x10024 bmdma 0x10008 irq 38 I noticed tby nialbr - Debian
bodhi, Seems like it has no effect :( [ 61.031388][ T182] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 66.089757][ T182] ata3.00: qc timeout (cmd 0xec) [ 66.094589][ T182] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 66.101436][ T182] ata3.00: revalidation failed (errno=-5) [ 66.431381][ T182] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)by nialbr - Debian
bodhi, I have two spare drives(no important data) that I can swap in. Do you think that would make sense to test the para_module with only two drives in? That would be perfect for me. I have a backup from the important data from the original ones but I would like to try to keep these disks if possible.by nialbr - Debian
@bodhi I don`t have any config file in /boot. The dmsg has no "pata" either root@ix4-200d:/# dmesg | grep pata root@ix4-200d:/# Here is the ls lspci output from the Stock OS: root@ix4-200d:/# lspci -vv 00:01.0 IDE interface: Marvell Technology Group Ltd. Device 6121 (rev b2) (prog-if 8f ) Subsystem: Marvell Technology Group Ltd. Device 6121 Control: Iby nialbr - Debian
@bodhi Here is the output root@debian:~# lspci -vv 00:01.0 PCI bridge: Marvell Technology Group Ltd. 88F6281 ARM SoC (rev 03) (prog-if 00 ) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cachby nialbr - Debian
@bodhi In my case the issue is not about activating the SATA Ports. I've followed your instructions and appended the DTB file to the kernel image. The OS can see the ports and the disks attached. My problem occurrs intermittently when trying to access(read/write/hdparm) some of the drives. [ 152.766204] Segment Routing with IPv6 [ 411.119283] ata4: SATA link up 3.0 Gbps (SStatus 123by nialbr - Debian
@TrashCanMan Sorry to 'hijack' your topic but have you found the fix for the 4 sata port issue? I'm having the exactly same problem and couldn't find the topic @bodhi mentioned earlier. I've found this topic but couldn't find the solution: https://forum.doozan.com/read.php?2,22623,page=1 Thank you.by nialbr - Debian