maric

Members
  • Posts

    12
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

maric's Achievements

Noob

Noob (1/14)

1

Reputation

  1. OK, I understand. Just looking through some old posts about rebuilding a disabled disk but the links seem to be dead. Also, I see now that the disk is disabled but I was just using the terminology from the GUI which, TBH, is a bit mixed.
  2. The SMART report looks ok (I think) but system still shows disk as failed. borg-smart-20231004-1252.zip
  3. Oh, ok thanks. I'll spin down and do just that but FYI this disk is in a hot plug 8 Bay HP Cage connected by 2 x SAS cables to an HP H240 controller so there are at least three other disks on the same cable. I'll do a reseat of the caddy as well though as that won't hurt. I'll be back with the SMART in a few minutes.
  4. So... I've been away from home for a week and on return noticed that my 6.12.3 system is reporting the following and that the parity disk is offline. I've checked the logs and found (from my own novice checks) that the disk looks to have had a hardware error, is that right? Kind of annoying considering it's only about 2 months old and still under warranty. before I do any shutdown/reboots etc I just wanted to check with the experts what my next steps should be as I'm thinking I'll have to RMA the faulty disk and when a replacement arrives re-install and let the parity rebuild. Am I ok to carry on using the (unprotected) system in the meantime, it's only really a media server? Is it ok to stop the array, pull the faulty physical disk and restart, I could use a spare 1.92 SSD as a temp parity but I was under the impression that spinners were better than SSD's hence my reason for the 4Gb in the first place? Thanks in advance. Diagnostics attached. Sep 29 19:03:10 Borg kernel: hpsa 0000:03:00.0: scsi 1:0:8:0: resetting physical Direct-Access ATA ST4000LM024-2AN1 PHYS DRV SSDSmartPathCap- En- Exp=1 Sep 29 19:03:16 Borg kernel: hpsa 0000:03:00.0: invalid command: LUN:0000000000800701 CDB:01030000000000000000000000000000 Sep 29 19:03:16 Borg kernel: hpsa 0000:03:00.0: probably means device no longer present Sep 29 19:03:16 Borg kernel: hpsa 0000:03:00.0: scsi 1:0:8:0: reset physical failed Direct-Access ATA ST4000LM024-2AN1 PHYS DRV SSDSmartPathCap- En- Exp=1 Sep 29 19:03:16 Borg kernel: sd 1:0:8:0: Device offlined - not ready after error recovery ### [PREVIOUS LINE REPEATED 2 TIMES] ### Sep 29 19:03:16 Borg kernel: sd 1:0:8:0: [sdi] tag#883 UNKNOWN(0x2003) Result: hostbyte=0x05 driverbyte=DRIVER_OK cmd_age=65s Sep 29 19:03:16 Borg kernel: sd 1:0:8:0: [sdi] tag#883 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 Sep 29 19:03:16 Borg kernel: I/O error, dev sdi, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 2 Sep 29 19:03:16 Borg kernel: sd 1:0:8:0: [sdi] tag#884 UNKNOWN(0x2003) Result: hostbyte=0x05 driverbyte=DRIVER_OK cmd_age=65s Sep 29 19:03:16 Borg kernel: sd 1:0:8:0: [sdi] tag#884 CDB: opcode=0x88 88 00 00 00 00 00 70 0c 9d 80 00 00 00 08 00 00 Sep 29 19:03:16 Borg kernel: I/O error, dev sdi, sector 1879874944 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Sep 29 19:03:16 Borg kernel: md: disk0 read error, sector=1879874880 Sep 29 19:03:16 Borg kernel: sd 1:0:8:0: [sdi] tag#885 UNKNOWN(0x2003) Result: hostbyte=0x05 driverbyte=DRIVER_OK cmd_age=65s Sep 29 19:03:16 Borg kernel: sd 1:0:8:0: [sdi] tag#885 CDB: opcode=0x8a 8a 00 00 00 00 00 70 0c 9d 78 00 00 00 08 00 00 Sep 29 19:03:16 Borg kernel: I/O error, dev sdi, sector 1879874936 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2 Sep 29 19:03:16 Borg kernel: md: disk0 write error, sector=1879874872 Sep 29 19:03:16 Borg kernel: sd 1:0:8:0: rejecting I/O to offline device Sep 29 19:03:16 Borg kernel: I/O error, dev sdi, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 2 Sep 29 19:03:16 Borg kernel: I/O error, dev sdi, sector 955866864 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 2 Sep 29 19:03:16 Borg kernel: md: disk0 read error, sector=955866800 Sep 29 19:03:16 Borg kernel: md: disk0 read error, sector=955866808 Sep 29 19:03:16 Borg kernel: md: disk0 read error, sector=955866816 Sep 29 19:03:16 Borg kernel: md: disk0 read error, sector=955866824 Sep 29 19:03:16 Borg kernel: md: disk0 read error, sector=955866832 Sep 29 19:03:16 Borg kernel: md: disk0 read error, sector=955866840 Sep 29 19:03:16 Borg kernel: md: disk0 read error, sector=955866848 Sep 29 19:03:16 Borg kernel: md: disk0 read error, sector=955866856 borg-diagnostics-20231004-1135.zip
  5. Running on an old HP Z820, way overkill for a home media server with a few docker containers and VM's but hey ho, we do like to play don't we. ☺️
  6. Thanks for this, I had an old HP Proliant ML310e G8 with a Quadro K2000 card which wasn't seen by Unraid when I upgraded to the latest Nvidia Driver. I even installed a Quadro K620 to see if that made any difference but I've since found that the ML310 doesn't support the K620 so I had to downgrade the driver back to the last stable Legacy and re-install the K2000. It's only used to do some transcoding for Plex/Jellyfin so no real loss but thanks for confirming.
  7. Way overkill I know but it's what the system came with...
  8. I've been pondering this and decided that I don't really need to run two machines, there's no real benefit for me at the moment, especially considering the giant leap in performance from my current machine to the new one. I already have a working backup solution to Google Drive using Duplicati (thanks SpaceinvaderOne) so I'm only really looking to port my current subscription which I would upgrade to Pro, to a totally new machine without transferring any hardware, is that possible?
  9. Excuse the noob question but I've been lucky enough to get my hands on an old server which only has SSD's, 26 x 2Tb in total. I'm in the process of building it and through a combination of ignorance and inexperience I've configured it as follows, From what I've understood am I right in thinking it would better if I used conventional disk(s) for parity and just had a huge cache? Unfortunately, the chassis only supports 2.5" drives with nothing available internally to jury rig (it's an HP DL380 G9) so I'll need to swap out some of the existing. I'm hoping to use this machine instead of my current old PC and would look to migrate everything across (or backup/restore, still learning that bit). The worry I have is that I've seen lots of comments about not supporting SSD's in an array or advice against it but also posts from people who've been doing it for years without issue. Not that I'm running any mission critical apps or whatever, just the usual Plex and downloaders etc. the important data is all in the cloud. Am I wasting my time or is it worth pursuing? TIA
  10. True, I did think about that as well, I was just trying to save the expense of a full Pro key on top of the Plus I already have is all.
  11. Hi, I have a similar situation in that I've been running a plus server for just under a year with no issues or complaints (it's been great) but I now want to migrate to a bigger machine with more capacity. I appreciate that I'll need to upgrade to the Pro license but I'm not sure how to go about it without trashing my current server or losing everything in the process. Is it just a case of Purchase upgrade from Plus to Pro on existing machine Register new machine with a trial key and once built and configured, transfer all data across Replace trial USB key with (now pro) licensed key? I won't be using any of the hardware between these machines, other than the licensed USB key. TIA.