Jump to content

nexusmaniac

Members
  • Content Count

    237
  • Joined

  • Last visited

Community Reputation

6 Neutral

About nexusmaniac

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  • URL
    https://mnailor.wordpress.com/

Recent Profile Visitors

735 profile views
  1. Exactly the same here Jan 23 04:17:25 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3761, flush 0, corrupt 0, gen 0 Jan 23 04:17:30 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3762, flush 0, corrupt 0, gen 0 Jan 23 04:17:30 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3763, flush 0, corrupt 0, gen 0 Jan 23 04:17:30 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3764, flush 0, corrupt 0, gen 0 Jan 23 04:17:30 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3765, flush 0, corrupt 0, gen 0 Jan 23 04:17:30 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3766, flush 0, corrupt 0, gen 0 Jan 23 04:17:30 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3767, flush 0, corrupt 0, gen 0 Jan 23 04:17:30 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3768, flush 0, corrupt 0, gen 0 Jan 23 04:17:30 Raptor kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 3769, flush 0, corrupt 0, gen 0 raptor-diagnostics-20190123-0839.zip
  2. Is it possible to figure out the cause? Last thing I want to do is encounter the same issue again 'soon' Looks like I'd best get backing up in the meantime then
  3. Hmm... 2:16 Raptor kernel: loop: Write error at byte offset 2392465408, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 4672784 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32:16 Raptor kernel: loop: Write error at byte offset 4215803904, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 8233992 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32:16 Raptor kernel: loop: Write error at byte offset 2392465408, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 4672784 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32:16 Raptor kernel: loop: Write error at byte offset 2392473600, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 4672800 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 5, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32:16 Raptor kernel: loop: Write error at byte offset 2392608768, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 4673064 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 6, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32:16 Raptor kernel: loop: Write error at byte offset 2392465408, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 4672784 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 7, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32:16 Raptor kernel: loop: Write error at byte offset 4367192064, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 8529672 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 8, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32:16 Raptor kernel: loop: Write error at byte offset 2392465408, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 4672784 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 9, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32:16 Raptor kernel: loop: Write error at byte offset 2392469504, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 4672792 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 10, rd 0, flush 1, corrupt 0, gen 0 Nov 15 21:32:16 Raptor kernel: loop: Write error at byte offset 2392489984, length 4096. Nov 15 21:32:16 Raptor kernel: print_req_error: I/O error, dev loop2, sector 4672832 Nov 15 21:32:16 Raptor kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 11, rd 0 Crap? ------- Nov 15 21:31:57 Raptor kernel: BTRFS error (device sdl1): unable to find ref byte nr 2331165265920 parent 0 root 5 owner 18608628 offset 4014080 Nov 15 21:31:57 Raptor kernel: BTRFS: error (device sdl1) in __btrfs_free_extent:6950: errno=-2 No such entry Nov 15 21:31:57 Raptor kernel: BTRFS info (device sdl1): forced readonly Nov 15 21:31:57 Raptor kernel: BTRFS: error (device sdl1) in btrfs_run_delayed_refs:3057: errno=-2 No such entry Nov 15 21:31:57 Raptor kernel: BTRFS error (device sdl1): pending csums is 3751936 /dev/sdl
  4. I went to fire up Plex and my server was offline... I took a look at my NAS and it was true, Plex was stopped. In fact all of my containers had stopped! All of my disks were fine but my log was full of errors. I'm attaching the diagnostics if anybody wants to take a look. Latest version of Unraid (6.6.5) No idea what the cause was, I've just rebooted now so hopefully all is good 🤞 raptor-diagnostics-20181115-2127.zip
  5. sorted Just needed a balance in the end Ty
  6. Also got this email message this morning from my Unraid:
  7. btrfs fi show Label: none uuid: b5b7dc19-7d32-47df-be29-d6dd41e675d5 Total devices 2 FS bytes used 44.19GiB devid 4 size 111.79GiB used 69.09GiB path /dev/sdl1 *** Some devices missing My CACHE disk stays 'spun up' (SSD) but CACHE2 has no read / write activity and spins down when it hits the hour mark (the hour of disk inactivity). That command above shows device missing. CACHE is /dev/sdl & CACHE2 is /dev/sdk Both disks are there and showing without error... However the CACHE isn't treating them equally - How might I go about fixing this? Diagnostics attached. Thanks raptor-diagnostics-20181003-0836.zip
  8. Turns out it was two DOA WD's, after I ripped them out of the array and started prodding at them some more via Preclear & even Windows they started to show signs of badness! 😂 WD agreed and are shipping some brand new drives out to replace these, yay... Guess I can't close a thread here But 'problem solved' ... I'm incredibly unlucky and now I've got an LSI HBA card, win win I suppose 🤷‍♂️
  9. @johnnie.black Hey LSI card arrived, installed, flashed to IT mode, everything detected again... However I still get errors on Disk6 as soon as I stick it into the array 🤔 It passed a single preclear run with no errors but it hates being in the array - I'm doing another preclear but wanted to start my array and make it safe! So... I've set "No device" for disk6 - the contents will be emulated and thus if I experienced a REAL disk failure whilst in that state - I'd be screwed (right?) I had no data on disk6 so I'm not fussed about emulating an empty 3TB drive Am I correct in thinking I can take a screenshot now of the assignments, go to tools > New config and 'restart' with parity + disk1-5 and be in the green again? And let this preclear run in the background before I think about adding disk6 again? Cheers!!
  10. Oh, I was on the right lines? Excellent, I shall do so (yay more money to spend 😅) Cheers Johnnie! Fingers crossed! (Why me 😂😭)
  11. Considering buying this: https://smile.amazon.co.uk/10Gtek-Internal-Express-Controller-SAS2008/dp/B01M2AC40Y/ref=sr_1_1?ie=UTF8&qid=1537007716&sr=8-1&keywords=SAS+controller+HBA And flashing it to IT mode: ftp://ftp.supermicro.nl/driver/SAS/LSI/2008/IR_IT/Firmware/IT/ (Use supermicro's FTP site to flash the LSI 3008 to IT mode all the time at work) ------ I've got 4hrs left to get this on Prime tomorrow (Sunday 16th) along with a SAS to SATA breakout cable... I know the disks are fine, they're brand new and underwent a preclear. It's not impossible for it to have failed, sure... But I'm strongly leaning towards the cheapo SATA card (https://www.scan.co.uk/products/lycom-pe-120-ahci-sata-iii-6gbps-internal-4-port-low-profile-pcie-20-host-adapter) Based on this; the 3 disks connected to it had 'errors' on the Unraid Main tab the second that I began to `cp` from disk5 to disk6 (errors appeared on disk4/5/6) and now here I am, a vanished disk4 & a disabled disk6! I don't want to start mixing drives around... I have screenshots of the assignments so that's ok. There's no spare ports, that card has been running with 1 disk on it for a over a year - seems that the moment I add a 2nd and then 3rd drive that it's showing 'weakness' great... I only have 6 onboard SATA + the 4 from this card. I've got no other HBAs or SATA cards, etc. etc. Hence why I'm considering the LSI card so I can hook all the HDDs up to a (hopefully much more solid) card and get the array started again...
  12. So, not touching this damn array this time... I have had: Parity + 5 Data Disks for a while... I just pre-cleared 2 disks (one fine, added to array, the other not getting past the unraid signature step onto the post-read, left it alone). I now have Parity + 6 Data Disks. I ran: nohup cp -r /mnt/disk5 /mnt/disk6 & It started and then failed with a "segmentation fault" ... I look to the Main page and see disk missing (disabled, contents emulated) but there's nothing on it yet. I've rebooted a couple of times, all of the disks have been detected (i.e. show up in lsblk) but now I've got a missing disk and a disabled disk I'm suspecting a slightly dodgy PCIe to SATA card but can't be sure. Just don't want to screw up my array for obvious reasons (not twice in a couple of weeks 😧)... --------- I've attached a diag bundle, one where disk6 was disabled (after the attempt to cp data to it) that's 0843 And another one from now, where I've got a missing disk4 for some damn reason - Just checking what port it's plugged into RIGHT. 0941 So the crappy marvel 4 port has 3 HDDs: (serial ending) * E067 * C2L1 * JDJ3 That last one is fine.. But the first 2 connected to that card have gone tits up! raptor-diagnostics-20180915-0843.zip raptor-diagnostics-20180915-0941.zip
  13. I really have screwed myself here 😭😖 So my next thought. If I format sdf,disk3 so that it's readable. And do the parity restore again (3rd times the charm 🙈) I should be able to access my disk and then see my data?? 😅 Some of it at least (perhaps)
  14. Ok, I'll try that ------ I don't understand why the storage isn't being emulated in the way I've seen it before though? The parity should be able to calculate the missing 1's & 0's and 'reconstruct' the data missing from disk3, no? I should have the ability to see the emulated contents of the disk despite the disk being borked? I'm really lost here