Jump to content

JorgeB

Moderators
  • Posts

    67,696
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. You need to unmount the disk before removing, now a reboot will fix it.
  2. Search the forum, I never used one but there are some models mentioned where they mention the chipset.
  3. You can use ddrescue on disk7 to recover as much data as possible, if disk1 is really dead not much you can do about that.
  4. Logged is spammed with GPU related errors, reboot and post new diags after array start.
  5. I was looking at shares, not services, system was likely on cache, you need to re-create on the array, but note that docker and VMs will be empty, dockers can be easily restored if you have an appdata backup, for VMs you need backups of the vdisks and libvirt.img.
  6. User shares should be working, /mnt/user is mounted, but since the pool isn't mounting unassign al cache devices and start array to see if it makes a difference. P.S. syslog is included with the diags, no need to post it separately.
  7. Shares should still work, but we'd need the diagnostics to say more.
  8. This suggests the device was wiped/trimmed, only option would be a file recovery program, like UFS explorer, if the data wasn't discarded by the SSD.
  9. LSI also makes HBAs, and those are recommended:
  10. Sep 2 18:46:08 Pegasus nerdpack: Installing atop-2.2 package... This is known to do that, uninstall it.
  11. No ethernet NIC being detected, this is not a software issue, check/reset board BIOS to se if it's enable.
  12. There's also a Realtek NIC which is currently eth0, you can boot using the GUI mode and change that on Settings -> Network Settings -> Interface Rules (Reboot required)
  13. Post output of: fdisk -l /dev/sdl and blkid
  14. You can let the rebuild finish, there will be some/a lot of corrupt data on the rebuilt disk, but there are not many options, you can then rebuild disk5 but will also result in corrupt data, you can instead use ddrescue on disk5, there will also be corrupt data but at least you can find out which files are affected and need replacing, you can also try that on the old disk1, if not completely dead.
  15. Disk1 is likely dead and disk7 appears to be failing, if that's the case you can't rebuild disk1 with single parity, still and since there's no SMART report for disk7 can't see if a SMART test was run or not, try to run an extended test to confirm if the disk really failed.
  16. Would really avoid anything from VIA, look for a controller with an Asmedia or other chipset, also keep in mind that USB for array/pool drives is not recommended, it's fine for unassigned devices.
  17. You did the replacement correctly, there's a bug in Unraid, already reported it a long time ago but it's sill not fixed. Now that the old device was deleted from the pool you can just stop the array, add new pool device, start array and it should all be fine now, it will balance to raid1, one of the devices being 500GB and the other 480GB is not a problem, but only 480GB will be usable by the pool in raid1.
  18. Did you stop VM/Docker services as instructed in the wiki? If yes we'll needs diags after running the mover (with mover logging enable) to see the problem.
  19. OK, disks to be used in Unraid need to be formatted by Unraid or the UD plugin, or they won't be accepted, you can also use the UD plugin to mount the disks for the copy or add them to the array, without parity it will function similarly, though in the array you can already use user shares to split the data over multiple disks, if needed, copy will need to be done manually, but you can use Midnight Commander (mc on the console) or the Krusader docker, both have a GUI.
  20. What about them? They will be temporally moved to the array so you can replace cache.
×
×
  • Create New...