jasonbstanding

Members
  • Posts

    5
  • Joined

  • Last visited

Converted

  • Location
    Bristol, UK

jasonbstanding's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi there. This question looks fairly similar to one asked v. recently but I'm not savvy enough to know if it's the same... The other day one of my drives reported errors and is flagged as "disabled": I've run SMART short and extended tests on it which both returned without error, as well as the array Read Check - I'm not sure where to look to see more about these errors. In the syslog I can see a load of these: Jul 1 03:06:34 Beehouse kernel: blk_update_request: I/O error, dev sde, sector 1845904344 op 0x1:(WRITE) flags 0x800 phys_seg 94 prio class 0 Jul 1 03:06:34 Beehouse kernel: md: disk3 write error, sector=1845904280 Jul 1 03:06:34 Beehouse kernel: md: disk3 write error, sector=1845904288 Jul 1 03:06:34 Beehouse kernel: md: disk3 write error, sector=1845904296 Jul 1 03:06:34 Beehouse kernel: md: disk3 write error, sector=1845904304 Jul 1 03:06:34 Beehouse kernel: md: disk3 write error, sector=1845904312 Jul 1 03:06:34 Beehouse kernel: md: disk3 write error, sector=1845904320 Jul 1 03:06:34 Beehouse kernel: md: disk3 write error, sector=1845904328 Jul 1 03:06:34 Beehouse kernel: md: disk3 write error, sector=1845904336 Jul 1 03:06:34 Beehouse kernel: md: disk3 write error, sector=1845904344 Jul 1 03:06:34 Beehouse kernel: md: disk3 write error, sector=1845904352 Jul 1 03:06:34 Beehouse kernel: md: disk3 write error, sector=1845904360 Jul 1 03:06:34 Beehouse kernel: md: disk3 write error, sector=1845904368 Jul 1 03:06:34 Beehouse kernel: md: disk3 write error, sector=1845904376 Jul 1 03:06:34 Beehouse kernel: md: disk3 write error, sector=1845904384 Jul 1 03:06:34 Beehouse kernel: md: disk3 write error, sector=1845904392 Diagnostics attached. The drive in question is mainly just used as my TimeMachine backup. The box doesn't have anything non-standard in it (controller cards, etc) - it's just a Lenovo TS140 using the mainboard connectors, that's been ticking away nicely for years. Any ideas what I should try next? diagnostics-20220707-1631.zip
  2. That seems to have cheered it up - thanks a million! My new parity drive appears to be off happily building, and I can access my data again!
  3. Hi there, I've been really excited playing about with my new unraid setup these past few days since moving to it over Christmas, and I just took delivery of a couple of new drives after discovering how the unraid parity drive setup works. So, I just powered down by box, installed the new drives, then spun everything up again, and very worryingly for me the "main" 4TB drive that's got the bulk of my data on it has shown as unmountable. It showed as unmountable, so I put the array into maintenance mode and ran a check on it - which returned all OK and told me life was fine. So then I started the array again, and it showed as unmountable. I repeated the process, but now the check's returning: `Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error` I noticed the drive assignment go from sdc before the installation to sdg afterwards - but from what I can tell in this forum that's a red herring. My thoughts were: 1) power down & check all the cables are seated properly in case I knocked something 2) try unplugging the new drives & see if it sorts itself out But I wondered if there's anything else I can do? Predictably, this would happen to my main data drive on the exact same day the new drive arrives that I was planning to use as a parity drive. Many thanks!