Problems using MyCloud OS5

I am very disappointing about this upgrade. It seems that this has been a persistence issue and without a proper resolution. If I knew about this issue I would not even consider upgrading the firmware.
Like others here, I am even able to access the Dashboard as I am getting Refuse connection or Timeout. I am not sure if the indexing is in progress or not. The blue light is consistence. I have tried to connect via Mobile App and via Desktop web, both with the same issue.

After 14 days without access to the NAS, I disconnected at the source and disabled access to the cloud. I will give up WD and look for another manufacturer.

O meu passou 14 dias inacessível, perdi a paciência e desliguei na fonte. Quando voltou, desabilitei o acesso à nuvem. Agora só acesso os dados na minha rede. Estou buscando outro fabricando de NAS para substituir minha unidade WD.

Do not update. Nothing works.

Eu lá consegui.
Deixei com acesso cloud apenas pastas mais pequenas que ache mais importante aceder pela app ou website (li isto algures, já nem sei onde e decidi tentar). Tenho outras pastas maiores mas para essas só deixei acesso ftp caso necessite aceder remotamente.
Após fazer isto, deixei indexar de um dia para o outro e tem estado estável desde aí. Penso que o problema está no acesso cloud. Se forem muitos ficheiros e thumbnails parece que se passa um bocado.

1 Like

My system has gone completely to the wall since putting os5 on my cloud device, system worked perfectly till I put this ■■■■ downgrade on now I can get an hour out of it tops before the thing locks up and I’m unable to use it, there best be a fix soon as I’ve got 1000’s of images for my photography work stored on it. Messaged customer services and they were worse than useless telling me my device was broken and I needed to replace it, the thing worked before the downgrade and now it doesn’t. Getting really hesitant now about buying anymore WD products in the future

This is exactly the same issue I’m having

@SuzukiBluey has your collected the system logs and sent to support? If not, please do so and let me know your case number.

How to Collect My Cloud System Logs

Answer ID 18374

@SBrown hi I’ve already sent in my logs about 2 weeks ago, they said they were elevating my case but I’m yet to hear back off anyone. My case number is 210627000617

I removed cloud access to all shares, then only activated it to small shares that I thought would be more important to access from the phone app/web app. (bigger folders i use mainly locally or by ftp if I’m away).
Left it indexing and it’s been up until now.
By the look of it, it seems that the system goes nuts indexing for the cloud access the big shares with a lot of folders, files and specially thumbnails.

I’m pretty sure I’ve turned all cloud access off on mine, it helped briefly then fell over again

Oh… I don’t have any other idea then :confused:
I was thinking of buying a better WD NAS (maybe a Pro) when my gets older, but after all this, I’m not sure if I won’t look for another brand.
Good luck with yours.

I checked your case and there’s a note that you where informed the HDD has media errors and the device is Out Of Warranty. Here are the errors from your system logs.

[ 422.896684] EXT4-fs (sda2): error count since last fsck: 3
[ 422.902210] EXT4-fs (sda2): initial error at time 1580661384: ext4_readdir:172: inode 144446696
[ 422.910993] EXT4-fs (sda2): last error at time 1580661831: ext4_find_entry:1309: inode 144442581
[ 540.699069] perf: interrupt took too long (3937 > 3932), lowering kernel.perf_event_max_sample_rate to 50800
[ 942.297319] perf: interrupt took too long (4944 > 4921), lowering kernel.perf_event_max_sample_rate to 40400
[ 3327.542544] ata1.00: qc timeout (cmd 0x47)
[ 3327.546735] ata1.00: READ LOG DMA EXT failed, trying PIO
[ 3327.552088] ata1: failed to read log page 10h (errno=-5)
[ 3327.557455] ata1.00: exception Emask 0x1 SAct 0x10 SErr 0x0 action 0x6 frozen
[ 3327.564645] ata1.00: edma_err_cause=00000084 pp_flags=00000003, dev error, EDMA self-disable
[ 3327.573149] ata1.00: failed command: READ FPDMA QUEUED
[ 3327.578352] ata1.00: cmd 60/a0:20:00:dc:20/03:00:01:00:00/40 tag 4 ncq dma 475136 in
res 41/40:24:00:dc:20/40:00:01:00:00/40 Emask 0x9 (media error)
[ 3327.593922] ata1.00: status: { DRDY ERR }
[ 3327.597991] ata1.00: error: { UNC }
[ 3327.601513] ata1: hard resetting link
[ 3328.106721] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 3328.120389] ata1.00: configured for UDMA/133
[ 3328.124759] sd 0:0:0:0: [sda] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 3328.133048] sd 0:0:0:0: [sda] tag#4 Sense Key : 0x3 [current]
[ 3328.138944] sd 0:0:0:0: [sda] tag#4 ASC=0x11 ASCQ=0x4
[ 3328.144115] sd 0:0:0:0: [sda] tag#4 CDB: opcode=0x88 88 00 00 00 00 00 01 20 dc 00 00 00 03 a0 00 00
[ 3328.153316] print_req_error: I/O error, dev sda, sector 18930688
[ 3328.159521] ata1: EH complete
[ 3573.728984] ata1.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x6
[ 3573.735463] ata1.00: edma_err_cause=00000084 pp_flags=00000003, dev error, EDMA self-disable
[ 3573.743973] ata1.00: failed command: READ FPDMA QUEUED
[ 3573.749160] ata1.00: cmd 60/08:08:b8:de:20/00:00:01:00:00/40 tag 1 ncq dma 4096 in
res 41/40:00:b8:de:20/00:00:01:00:00/40 Emask 0x409 (media error)
[ 3573.765082] ata1.00: status: { DRDY ERR }
[ 3573.769118] ata1.00: error: { UNC }
[ 3573.772634] ata1: hard resetting link
[ 3574.276713] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 3574.288053] ata1.00: configured for UDMA/133
[ 3574.292384] sd 0:0:0:0: [sda] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 3574.300636] sd 0:0:0:0: [sda] tag#1 Sense Key : 0x3 [current]
[ 3574.306501] sd 0:0:0:0: [sda] tag#1 ASC=0x11 ASCQ=0x4
[ 3574.311694] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x88 88 00 00 00 00 00 01 20 de b8 00 00 00 08 00 00
[ 3574.320884] print_req_error: I/O error, dev sda, sector 18931384
[ 3574.327021] ata1: EH complete
[ 3577.768984] ata1.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x6
[ 3577.775551] ata1.00: edma_err_cause=00000084 pp_flags=00000003, dev error, EDMA self-disable
[ 3577.784070] ata1.00: failed command: READ FPDMA QUEUED
[ 3577.789261] ata1.00: cmd 60/08:30:b8:de:20/00:00:01:00:00/40 tag 6 ncq dma 4096 in
res 41/40:00:b8:de:20/00:00:01:00:00/40 Emask 0x409 (media error)
[ 3577.805177] ata1.00: status: { DRDY ERR }
[ 3577.809220] ata1.00: error: { UNC }
[ 3577.812736] ata1: hard resetting link
[ 3578.316724] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)

Right so what exactly does this mean? Does this mean my HDD is failing. I’ll be honest the drive worked perfectly fine and has worked flawlessly for the past 2-3 years of me having it, its literally been since this update that I’ve been having issues surely I would have been having problems before this?