Ati2

Members
  • Posts

    6
  • Joined

  • Last visited

Ati2's Achievements

Noob

Noob (1/14)

8

Reputation

  1. Thanks - showing read failure. Working on removing it from the array.
  2. This is my 8 year old WD Red drive, so pretty sure it's just going bad, but wanted to get a second opinion. Errors are below. As far as ejecting the disk out of the raid, what is the best way? Use unbalance or zero out the disk? May 31 07:34:11 FS kernel: md: disk2 read error, sector=1364635848 May 31 07:34:11 FS kernel: md: disk2 read error, sector=1364635856 May 31 07:34:11 FS kernel: md: disk2 read error, sector=1364635864 May 31 07:34:11 FS kernel: md: disk2 read error, sector=1364635872 May 31 07:34:11 FS kernel: md: disk2 read error, sector=1364635880 May 31 07:34:11 FS kernel: ata5: EH complete May 31 07:34:21 FS kernel: ata5.00: exception Emask 0x0 SAct 0x8079fd5d SErr 0x0 action 0x0 May 31 07:34:21 FS kernel: ata5.00: irq_stat 0x40000008 May 31 07:34:21 FS kernel: ata5.00: failed command: READ FPDMA QUEUED May 31 07:34:21 FS kernel: ata5.00: cmd 60/18:80:98:c3:56/03:00:51:00:00/40 tag 16 ncq dma 405504 in May 31 07:34:21 FS kernel: res 41/40:00:4f:c5:56/00:00:51:00:00/40 Emask 0x409 (media error) <F> May 31 07:34:21 FS kernel: ata5.00: status: { DRDY ERR } May 31 07:34:21 FS kernel: ata5.00: error: { UNC } May 31 07:34:21 FS kernel: ata5.00: configured for UDMA/133 May 31 07:34:21 FS kernel: sd 5:0:0:0: [sde] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=43s May 31 07:34:21 FS kernel: sd 5:0:0:0: [sde] tag#16 Sense Key : 0x3 [current] May 31 07:34:21 FS kernel: sd 5:0:0:0: [sde] tag#16 ASC=0x11 ASCQ=0x4 May 31 07:34:21 FS kernel: sd 5:0:0:0: [sde] tag#16 CDB: opcode=0x88 88 00 00 00 00 00 51 56 c3 98 00 00 03 18 00 00 May 31 07:34:21 FS kernel: I/O error, dev sde, sector 1364641103 op 0x0:(READ) flags 0x0 phys_seg 45 prio class 2 May 31 07:34:21 FS kernel: md: disk2 read error, sector=1364641032 May 31 07:34:21 FS kernel: md: disk2 read error, sector=1364641040 May 31 07:34:21 FS kernel: md: disk2 read error, sector=1364641048 May 31 07:34:21 FS kernel: md: disk2 read error, sector=1364641056 May 31 07:34:21 FS kernel: md: disk2 read error, sector=1364641064
  3. Good to hear that it helped you. It was such a pain to deal with as the issue would come up randomly a few days after reboot. I asked Unraid to fix it in the next version and set the idmap backend correctly. Hope they do.
  4. Incase anyone runs into this issue, it seems Unraid is using a deprecated idmap backend as the default. Check this thread as users have reported this multiple times in the past. The settings in the link did resolve my issue. Unraid- change the default idmap backend so more people don't have to waste their time.
  5. FYI - I ran into the same issue and changing the idmap backend to not use hash worked for me. Seems Unraid knows about this and should change their default as it's been unsupported by Samba for years. Unraid, change the default idmap backend so more people don't have to waste their time.
  6. I'm a new Unraid user, and this is the second time I've have this issue over the past 2-3 weeks. Basically, I can't mount any share as my domain administrator account due to the error in the subject line. However I can mount the same share using a different domain account. If do a wbinfo -i for the administrator, I get the following: wbinfo -i administator failed to call wbcGetpwnam: WBC_ERR_DOMAIN_NOT_FOUND Could not get info for user administator If I do it for another account, it works fine and I can mount a share under this account wbinfo -i userx userx:*:41101234:411012306:userx:/home/AD/userx:/bin/false If I check the status of the domain join, it's fine as well - net ads info and status both output as expected. The first time this happened I ended up rebooting and rejoining the domain. Obviously, this is not an acceptable solution and hopefully someone has a solution.. Thanks.