I'm using the RP64 with the dual SATA board to run two drives in a RAID 1 configuration. This is using OpenMediaVault 4.
The drives were seen as /dev/sda and /dev/sdb.
It was running fine for a while. And then I found that the Raid was showing as 'degraded' and only sda was showing in the Raid config. When I looked at the Disks section I found that sdb had disappeared and sdc had appeared. Using lsblk showed sdc as not having a partition.
Looking through syslog, I found this:
Code: Dec 2 09:07:45 mediavault kernel: [ 1766.245638] ata2.00: irq_stat 0x08000000, interface fatal error
Dec 2 09:07:45 mediavault kernel: [ 1766.251514] ata2: SError: { Handshk }
Dec 2 09:07:45 mediavault kernel: [ 1766.257211] ata2.00: failed command: WRITE FPDMA QUEUED
Dec 2 09:07:45 mediavault kernel: [ 1766.263010] ata2.00: cmd 61/28:00:00:70:08/06:00:01:00:00/40 tag 0 ncq 806912 out
Dec 2 09:07:45 mediavault kernel: [ 1766.263010] res 40/00:b8:00:08:09/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
Dec 2 09:07:45 mediavault kernel: [ 1766.274936] ata2.00: status: { DRDY }
Dec 2 09:07:45 mediavault kernel: [ 1766.280635] ata2.00: failed command: WRITE FPDMA QUEUED
Dec 2 09:07:45 mediavault kernel: [ 1766.286419] ata2.00: cmd 61/d8:08:28:76:08/01:00:01:00:00/40 tag 1 ncq 241664 out
Dec 2 09:07:45 mediavault kernel: [ 1766.286419] res 40/00:b8:00:08:09/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
Followed by those last four lines repeated many times. Then:
Code: Dec 2 09:07:45 mediavault kernel: [ 1766.819510] ata2.00: status: { DRDY }
Dec 2 09:07:45 mediavault kernel: [ 1766.823698] ata2: hard resetting link
Dec 2 09:07:55 mediavault kernel: [ 1776.824271] ata2: softreset failed (1st FIS failed)
Dec 2 09:07:55 mediavault kernel: [ 1776.828531] ata2: hard resetting link
Dec 2 09:08:05 mediavault kernel: [ 1786.829268] ata2: softreset failed (1st FIS failed)
Dec 2 09:08:05 mediavault kernel: [ 1786.833469] ata2: hard resetting link
Dec 2 09:08:40 mediavault kernel: [ 1821.834491] ata2: softreset failed (1st FIS failed)
Dec 2 09:08:40 mediavault kernel: [ 1821.838710] ata2: limiting SATA link speed to 3.0 Gbps
Dec 2 09:08:40 mediavault kernel: [ 1821.842808] ata2: hard resetting link
Dec 2 09:08:42 mediavault kernel: [ 1824.053694] ata2: SATA link down (SStatus 1 SControl 320)
Dec 2 09:08:42 mediavault kernel: [ 1824.058049] ata2: hard resetting link
Dec 2 09:08:45 mediavault kernel: [ 1826.265715] ata2: SATA link down (SStatus 1 SControl 320)
Dec 2 09:08:45 mediavault kernel: [ 1826.269883] ata2: limiting SATA link speed to 1.5 Gbps
Dec 2 09:08:50 mediavault kernel: [ 1831.269486] ata2: hard resetting link
Dec 2 09:08:52 mediavault kernel: [ 1833.480738] ata2: SATA link down (SStatus 1 SControl 310)
Dec 2 09:08:52 mediavault kernel: [ 1833.484879] ata2.00: disabled
Dec 2 09:08:52 mediavault kernel: [ 1833.493213] ata2: irq_stat 0x00000040, connection status changed
Dec 2 09:08:52 mediavault kernel: [ 1833.497272] ata2: SError: { CommWake DevExch }
Dec 2 09:08:52 mediavault kernel: [ 1833.501183] ata2: hard resetting link
Dec 2 09:08:53 mediavault kernel: [ 1834.382757] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 2 09:08:53 mediavault kernel: [ 1834.425005] ata2.00: ATA-10: ST1000LM048-2E7172, SDM1, max UDMA/133
Dec 2 09:08:53 mediavault kernel: [ 1834.429135] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Dec 2 09:08:53 mediavault kernel: [ 1834.484307] ata2.00: configured for UDMA/133
Dec 2 09:08:53 mediavault kernel: [ 1834.488274] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Dec 2 09:08:53 mediavault kernel: [ 1834.492577] sd 1:0:0:0: [sdb] tag#0 Sense Key : 0x5 [current] [descriptor]
Dec 2 09:08:53 mediavault kernel: [ 1834.496755] sd 1:0:0:0: [sdb] tag#0 ASC=0x21 ASCQ=0x4
Dec 2 09:08:53 mediavault kernel: [ 1834.500726] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 01 08 70 00 00 06 28 00
Dec 2 09:08:53 mediavault kernel: [ 1834.504911] blk_update_request: I/O error, dev sdb, sector 17330176
Dec 2 09:08:53 mediavault kernel: [ 1834.509051] sd 1:0:0:0: rejecting I/O to offline device
Dec 2 09:08:53 mediavault kernel: [ 1834.513001] sd 1:0:0:0: [sdb] killing request
Dec 2 09:08:53 mediavault kernel: [ 1834.516833] sd 1:0:0:0: rejecting I/O to offline device
Dec 2 09:08:53 mediavault kernel: [ 1834.520696] blk_update_request: I/O error, dev sdb, sector 16
Dec 2 09:08:53 mediavault kernel: [ 1834.524624] md: super_written gets error=-5
Dec 2 09:08:53 mediavault kernel: [ 1834.528376] md/raid1:md127: Disk failure on sdb, disabling device.
Dec 2 09:08:53 mediavault kernel: [ 1834.528376] md/raid1:md127: Operation continuing on 1 devices.
Dec 2 09:08:53 mediavault kernel: [ 1834.536240] sd 1:0:0:0: rejecting I/O to offline device
Dec 2 09:08:53 mediavault kernel: [ 1834.540072] blk_update_request: I/O error, dev sdb, sector 16
Dec 2 09:08:53 mediavault kernel: [ 1834.543942] md: super_written gets error=-5
Dec 2 09:08:53 mediavault kernel: [ 1834.547728] sd 1:0:0:0: rejecting I/O to offline device
Followed by that last line repeated many, many times. Followed by this:
Code: Dec 2 09:08:55 mediavault kernel: [ 1836.385630] ata2.00: detaching (SCSI 1:0:0:0)
Dec 2 09:08:55 mediavault kernel: [ 1836.392394] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Dec 2 09:08:55 mediavault kernel: [ 1836.394083] sd 1:0:0:0: [sdb] Stopping disk
Dec 2 09:08:56 mediavault kernel: [ 1837.154695] scsi 1:0:0:0: Direct-Access ATA ST1000LM048-2E71 SDM1 PQ: 0 ANSI: 5
Dec 2 09:08:56 mediavault kernel: [ 1837.157630] sd 1:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Dec 2 09:08:56 mediavault kernel: [ 1837.159989] sd 1:0:0:0: [sdc] 4096-byte physical blocks
Dec 2 09:08:56 mediavault kernel: [ 1837.162502] sd 1:0:0:0: [sdc] Write Protect is off
Dec 2 09:08:56 mediavault kernel: [ 1837.164634] sd 1:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Dec 2 09:08:56 mediavault kernel: [ 1837.164779] sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 2 09:08:56 mediavault kernel: [ 1837.734092] sd 1:0:0:0: [sdc] Attached SCSI disk
Dec 2 09:08:59 mediavault systemd-udevd[4876]: Process '/sbin/mdadm -If sdb --path platform-f8000000.pcie-pci-0000:01:00.0-ata-2' failed with exit code 1.
I have no clue what any of this means. This happened to me before, too, and I assumed it might be a disk fault and used a different (brand new) disk.
Can anyone give me some clues as to what's going on here?
Quick update: rebooting made sdb reappear again and it was automatically recognised by the raid config. But, of course, it's now taking hours for the Raid to rebuild, and I still don't know what caused the problem in the first place (and whether it might happen again).
I just got my RockPro64 today and was experiencing similar issues with my 250gb SSD while my 2.5" 250gb HDD worked just fine. Once I updated however (Ubuntu 18.04 minimal) everything started working fine. I realize this may not be a huge help to you if you are up to date on OMV.
01-18-2019, 03:00 AM
(This post was last modified: 01-27-2019, 12:22 AM by flocke196.)
I have exactly the same issue, using the official Sata Card on "stretch-openmediavault-rock64-0.7.9-1067-arm64.img".
The connected disks (2x WD Red 6TB) are connected/powerd by the official adapters, that cam with the NAS case. The psu is an official one, suited for the NAS use case.
Any ideas on this?
Due to these issues, i am even not able to create a filesystem on a HDD. So, the RockPro is not usable as a NAS at the moment.
I will give "Ubuntu 18.04 minimal" a try, as Belakor said, and report if these errors persist.
Edit: Issue persisted until i updated the psu (official 12V/5A --> Leicke NT33402 12V/7.5A).
(01-18-2019, 03:00 AM)flocke196 Wrote: I have exactly the same issue, using the official Sata Card on "stretch-openmediavault-rock64-0.7.9-1067-arm64.img".
The connected disks (2x WD Red 6TB) are connected/powerd by the official adapters, that cam with the NAS case. The psu is an official one, suited for the NAS use case.
Any ideas on this?
Due to these issues, i am even not able to create a filesystem on a HDD. So, the RockPro is not usable as a NAS at the moment.
I will give "Ubuntu 18.04 minimal" a try, as Belakor said, and report if these errors persist.
Edit: Issue persisted until i updated the psu (official 12V/5A --> Leicke NT33402 12V/7.5A).
I ended up switching to Armbian as eventually I had problems again with Ubuntu. I haven't had a repeat with Armbian but it does make me nervous.
The PSU does seem like the most likely culprit. I'll order a new one as well and do some further testing once I have it. Wish I had thought of it myself.
(02-26-2019, 12:15 PM)Belakor Wrote: (01-18-2019, 03:00 AM)flocke196 Wrote: I have exactly the same issue, using the official Sata Card on "stretch-openmediavault-rock64-0.7.9-1067-arm64.img".
The connected disks (2x WD Red 6TB) are connected/powerd by the official adapters, that cam with the NAS case. The psu is an official one, suited for the NAS use case.
Any ideas on this?
Due to these issues, i am even not able to create a filesystem on a HDD. So, the RockPro is not usable as a NAS at the moment.
I will give "Ubuntu 18.04 minimal" a try, as Belakor said, and report if these errors persist.
Edit: Issue persisted until i updated the psu (official 12V/5A --> Leicke NT33402 12V/7.5A).
I ended up switching to Armbian as eventually I had problems again with Ubuntu. I haven't had a repeat with Armbian but it does make me nervous.
The PSU does seem like the most likely culprit. I'll order a new one as well and do some further testing once I have it. Wish I had thought of it myself.
I have the same issue, The funny stuff is that the seller ask me to do strange and stupid trials while i see the issue is already reported. Incredible and bad support, I hope that paypal will let me to get refund teh ~250$ i spent for a garbage NAS kit (only their hw: rockpro64/4gb+ their sata + ...). I have to mention that another sata card with the same chipset they use performs the same (errors).
I also have issue to see my openmediavault from my win10 pc (I try all what i found in internet)...no way.
While Synology works out of the box....
Having no customer support is really disappointing...
There was a post on 4pda.ru forum about SATA controllers for ROCKPro64. In short, the SATA controller chips are overheating and may fail.
Try to mount a small heatsing on SATA controller chip.
Also here: PCI-E Card failure? the SATA controller chip overheating was reported too.
(05-08-2019, 03:56 AM)fieni Wrote: (02-26-2019, 12:15 PM)Belakor Wrote: (01-18-2019, 03:00 AM)flocke196 Wrote: I have exactly the same issue, using the official Sata Card on "stretch-openmediavault-rock64-0.7.9-1067-arm64.img".
The connected disks (2x WD Red 6TB) are connected/powerd by the official adapters, that cam with the NAS case. The psu is an official one, suited for the NAS use case.
Any ideas on this?
Due to these issues, i am even not able to create a filesystem on a HDD. So, the RockPro is not usable as a NAS at the moment.
I will give "Ubuntu 18.04 minimal" a try, as Belakor said, and report if these errors persist.
Edit: Issue persisted until i updated the psu (official 12V/5A --> Leicke NT33402 12V/7.5A).
I ended up switching to Armbian as eventually I had problems again with Ubuntu. I haven't had a repeat with Armbian but it does make me nervous.
The PSU does seem like the most likely culprit. I'll order a new one as well and do some further testing once I have it. Wish I had thought of it myself.
I have the same issue, The funny stuff is that the seller ask me to do strange and stupid trials while i see the issue is already reported. Incredible and bad support, I hope that paypal will let me to get refund teh ~250$ i spent for a garbage NAS kit (only their hw: rockpro64/4gb+ their sata + ...). I have to mention that another sata card with the same chipset they use performs the same (errors).
I also have issue to see my openmediavault from my win10 pc (I try all what i found in internet)...no way.
While Synology works out of the box....
Having no customer support is really disappointing...
Hello, did the new 12V 7.5A fixed your issues w.ith the nas case + sata pcie card? I am having issues with a nas system that I ordered in july and freezes randomly running omv with 2 hard drives connected.
BTW, the customer support is garbage. I asked for help and they told me to look for similarbissues in the forum. I am never going to buy anything from them again. 200 usd wasted.
(08-11-2019, 11:23 AM)hexxx Wrote: Hello, did the new 12V 7.5A fixed your issues w.ith the nas case + sata pcie card? I am having issues with a nas system that I ordered in july and freezes randomly running omv with 2 hard drives connected.
You need to collect more data for further investigation. The kernel log is most important thing. For hardest cases, UART serial output may be the last option to collect the information. Being a developer, I'd connect SBC's serial output to serial input of another computer with serial logger running. minicom terminal is enough to setup a serial port and store the output into a file. Real time logging may greatly help to investigate the cause of freezing.
Also, you need to try different distributives. You may try to choose something with latest kernel version (most freezes are kernel problems). Then to install OMV over selected distro.
Try this instructions: https://openmediavault.readthedocs.io/en...ebian.html
Quote:BTW, the customer support is garbage. I asked for help and they told me to look for similarbissues in the forum. I am never going to buy anything from them again. 200 usd wasted.
As I'm understanding Pine64 business, they are selling mostly development boards, development platforms. Not a complete hardware and software solutions. They are warranting that the hardware is assembled in correspondence with circuit diagram and is in good condition. What software to load into the board is up to a customer. Hardware bugs in CPU or another integrated circuits on the board should be addressed to these IC manufacturers but Pine64 stuff. Software bugs - to software maintainers. I don't know, but it seems to me Pine64 have none software development team. Just because end users have very different tasks that can't be covered by common software.
It is not like a, say, Internet router or TV set-top-box. If you need a router, your'e buying a router. Such devices have fixed functionality and fixed software from a manufacturer. This is not the case with Pine64. The ROCKPro64 is much more universal, than a NAS. Look at the LVDS display interface, camera interfaces. The SBC is a platform for embedded developer to test his (her?) ideas in hardware. Then to develop his own PCB with Rockchip CPU which will exactly fit certain design needs.
Pine64 are selling SBC and NAS case separately. As a components for DIY NAS. And software assumed to be DIY too. Just re-checked. Pine64 store doesn't offer a "NAS" or a "NAS kit". Only the SBS and a case for NAS separately. So the NAS building, including the software, is customer responsibility. All this is explaining why Pine64 support is unable to provide you with a solution. Only the community may help. But an efforts from your side are needed. Start from different distributive trials and log collecting.
|
