July 16Jul 16 Community Expert The I put/outputerror message suggest the drive is going offline or something similar when trying to write to the drive. The diagnostics might give more information. Since it is an emulated drive I wonder if the error is elsewhere. It is also a bit strange as the previous attempts to fix the file system successfully read the (emulated) superblock.
July 16Jul 16 Author 21 minutes ago, itimpi said:The I put/outputerror message suggest the drive is going offline or something similar when trying to write to the drive. The diagnostics might give more information. Since it is an emulated drive I wonder if the error is elsewhere. It is also a bit strange as the previous attempts to fix the file system successfully read the (emulated) superblock.Yea, it makes no sence to me what so ever Newest diag:tdk-diagnostics-20260716-1608.zipI hate beeing this dumb to unraid, but on the otherhand, I feel like its a big thing to learn atm So I really appreciate all the help here.
July 16Jul 16 Community Expert Parity disk is having read/write errors it looks like which explains why you cant correct the emulated disk filesystemJul 16 15:41:30 TDK kernel: md: disk0 write error, sector=19327536304 Jul 16 15:41:30 TDK kernel: sd 5:0:2:0: [sde] tag#1785 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=3s Jul 16 15:41:30 TDK kernel: sd 5:0:2:0: [sde] tag#1785 CDB: opcode=0x88 88 00 00 00 00 04 80 02 e0 f8 00 00 04 00 00 00 Jul 16 15:41:30 TDK kernel: md: disk0 read error, sector=19327541432Might want to check the connection on this disk or try another cable? Edited July 16Jul 16 by MowMdown
July 16Jul 16 Community Expert Imput/output error is typically a device problem, like the diags show, SMART for parity looks good, so follow the advice above and then try again.
July 16Jul 16 Author 4 hours ago, MowMdown said:Parity disk is having read/write errors it looks like which explains why you cant correct the emulated disk filesystemJul 16 15:41:30 TDK kernel: md: disk0 write error, sector=19327536304 Jul 16 15:41:30 TDK kernel: sd 5:0:2:0: [sde] tag#1785 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=3s Jul 16 15:41:30 TDK kernel: sd 5:0:2:0: [sde] tag#1785 CDB: opcode=0x88 88 00 00 00 00 04 80 02 e0 f8 00 00 04 00 00 00 Jul 16 15:41:30 TDK kernel: md: disk0 read error, sector=19327541432Might want to check the connection on this disk or try another cable?Thanks! I have unplugged all connections, and now it went well Here is the diag:tdk-diagnostics-20260716-2059.zip Edited July 16Jul 16 by Cololate
July 17Jul 17 Community Expert Post new diags with the array started to see if the emulated disk is mounting
July 18Jul 18 Author 7 minutes ago, MowMdown said:Parity disk is having read/write errors it looks like which explains why you cant correct the emulated disk filesystemJul 16 15:41:30 TDK kernel: md: disk0 write error, sector=19327536304 Jul 16 15:41:30 TDK kernel: sd 5:0:2:0: [sde] tag#1785 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=3s Jul 16 15:41:30 TDK kernel: sd 5:0:2:0: [sde] tag#1785 CDB: opcode=0x88 88 00 00 00 00 04 80 02 e0 f8 00 00 04 00 00 00 Jul 16 15:41:30 TDK kernel: md: disk0 read error, sector=19327541432Might want to check the connection on this disk or try another cable?On 7/17/2026 at 8:42 AM, JorgeB said:Post new diags with the array started to see if the emulated disk is mountingI will do so I just hit another vacation, so it wont be until next saturday. Until then, it has been turned off :)
July 25Jul 25 Author On 7/17/2026 at 8:42 AM, JorgeB said:Post new diags with the array started to see if the emulated disk is mountingBack from vacation - and ready to move on Started the server, paused the data-rebuild, made this diag:tdk-diagnostics-20260725-1455.zipHope I did the right thing of pausing it, otherwise, I know you will let me know ;)
July 25Jul 25 Community Expert 40 minutes ago, Cololate said:Back from vacation - and ready to move on Started the server, paused the data-rebuild, made this diag:tdk-diagnostics-20260725-1455.zipHope I did the right thing of pausing it, otherwise, I know you will let me know ;)You can resume the data-rebuild, disks are mounted.
July 25Jul 25 Author 11 minutes ago, MowMdown said:You can resume the data-rebuild, disks are mounted.Ill get right on it - thank you so much :) Hope it gets better this time around :)
July 26Jul 26 Author Ok, so it ran fine, full rebuild, no errors.tdk-diagnostics-20260726-1843.zipThis is from when it finished.I have changed the cables and raidcard before, as I have had this error before, many times. (before I had help here, and just swapped the disks DOH)Could this be a PSU thing? I feel like thats the only thing I have not changed over the years.Its a CoolerMaster G650M - and I would swap it in a heartbeat, if that could be the reason over the years, to the many errors.Thanks agian guys - you are all awsome as always, and I am so happy to be back on track (it seams)
July 27Jul 27 Community Expert No ATA errors during the rebuild, which is good news.14 hours ago, Cololate said:Could this be a PSU thing?It's possible, and I don't remember if I asked before, but if there are any power splitters in use it could also be the problem
July 27Jul 27 Author 6 hours ago, JorgeB said:No ATA errors during the rebuild, which is good news.It's possible, and I don't remember if I asked before, but if there are any power splitters in use it could also be the problemAight - might just go get a new one then, as I dont wanna be in this situation agian, if I can help it :)*There are no splitters. Just 3 disk's and a SSD for cache, and the get power directly from the PSU. Though it is an older one, so I just might think that it could have some issues.I am gonna go out and find a top tier PSU for this one, and see how it goes
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.