Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Need help for my unraid

ncaamac
in General Support (V5 and Older)

Featured Replies

Since you have given up on recovering anything from those disks, try this.

 

Stop the array.

 

Unassign both of the problem disks.

 

Start the array and do a parity sync without those disks.

 

Preclear the problem disks. See here for preclear script and make sure you have the latest version.

 

If the preclears come out OK:

 

Add one of the disks and start the array. It should offer to format the disk.

 

If successful, repeat with other disk.

  • Quote
    • Author

    i don't can do this....

     

    when i remove both disks..it gives me a error that the config is bad

     

    i don't can unassign....it call always " no device "...

    Zwischenablage02.jpg.9749ac0473faeec61eaf9e80be6d68ef.jpg

  • Quote

    Sorry, try it this way:

     

    Make sure you know what drive belongs in each slot, especially the parity drive.

     

    Stop the array.

     

    Do New Config from the Tools page.

     

    Assign all disks to their original slots, but leave the problem disks unassigned.

     

    Start the array and let it do a parity sync.

     

    Preclear each of the problem disks. See here for preclear script and make sure you have the latest version.

     

    If the preclears come out OK:

     

    Add one of the disks and start the array. It should offer to format the disk.

     

    If successful, repeat with other disk.

  • Quote
    • Author

    woohooo.....i'm very happy.....the server make all what i want....without an error.... ;D

     

    sry...but alwys..errors...bad massages....and now it does what i say :-)

     

    parrity is running now....i say when its ready

     

    thx a lot

    Zwischenablage02.jpg.1bf03814689d804f5260841209cc280c.jpg

  • Quote
    • Author

    lol...we talk in a  week  :o

     

    current 4% ... i'm waiting...at this speed ....next weekend

     

    and disk 5 gives errors ???......is that because the other disks are missing?

    Zwischenablage02.jpg.49cc6d95ed9d861a634bec282b6d7c0e.jpg

  • Quote

    Probably still have some sort of problem going on if parity is taking that long. What is your hardware?

  • Quote
    • Author

    no, no new errors...

     

    but very very slow....current 7%...

     

    syslog this time:

     

     

     

     

    Jan  5 16:25:25 NAS kernel: ata7.00: error: { ABRT } (Errors)

    Jan  5 16:25:25 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:25:25 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:25:26 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

    Jan  5 16:25:26 NAS kernel: ata7.00: BMDMA2 stat 0x616d0009 (Drive related)

    Jan  5 16:25:26 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:25:26 NAS kernel: ata7.00: cmd 25/00:00:27:2b:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:25:26 NAS kernel:          res 51/04:60:c7:2b:b2/00:03:10:00:00/e0 Emask 0x1 (device error) (Errors)

    Jan  5 16:25:26 NAS kernel: ata7.00: status: { DRDY ERR } (Drive related)

    Jan  5 16:25:26 NAS kernel: ata7.00: error: { ABRT } (Errors)

    Jan  5 16:25:26 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:25:26 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:25:26 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

    Jan  5 16:25:26 NAS kernel: ata7.00: BMDMA2 stat 0x616d0009 (Drive related)

    Jan  5 16:25:26 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:25:26 NAS kernel: ata7.00: cmd 25/00:00:27:33:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:25:26 NAS kernel:          res 51/04:b0:77:34:b2/00:02:10:00:00/e0 Emask 0x1 (device error) (Errors)

    Jan  5 16:25:26 NAS kernel: ata7.00: status: { DRDY ERR } (Drive related)

    Jan  5 16:25:26 NAS kernel: ata7.00: error: { ABRT } (Errors)

    Jan  5 16:25:26 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:25:26 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:25:56 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors)

    Jan  5 16:25:56 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:25:56 NAS kernel: ata7.00: cmd 25/00:00:27:3b:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:25:56 NAS kernel:          res 40/00:b0:77:34:b2/00:02:10:00:00/e0 Emask 0x4 (timeout) (Errors)

    Jan  5 16:25:56 NAS kernel: ata7.00: status: { DRDY } (Drive related)

    Jan  5 16:25:56 NAS kernel: ata7: hard resetting link (Minor Issues)

    Jan  5 16:25:56 NAS kernel: ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 310) (Drive related)

    Jan  5 16:25:56 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:25:56 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:25:56 NAS kernel: ata7: drained 65536 bytes to clear DRQ (Drive related)

    Jan  5 16:25:56 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors)

    Jan  5 16:25:56 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:25:56 NAS kernel: ata7.00: cmd 25/00:00:27:3b:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:25:56 NAS kernel:          res ff/ff:ff:ff:ff:ff/ff:ff:ff:ff:ff/ff Emask 0x2 (HSM violation) (Errors)

    Jan  5 16:25:56 NAS kernel: ata7.00: status: { Busy } (Drive related)

    Jan  5 16:25:56 NAS kernel: ata7.00: error: { ICRC UNC IDNF ABRT } (Errors)

    Jan  5 16:25:56 NAS kernel: ata7: hard resetting link (Minor Issues)

    Jan  5 16:25:57 NAS kernel: ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 310) (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

    Jan  5 16:25:57 NAS kernel: ata7.00: BMDMA2 stat 0x616d0009 (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:25:57 NAS kernel: ata7.00: cmd 25/00:00:27:47:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:25:57 NAS kernel:          res 51/04:a0:87:49:b2/00:01:10:00:00/e0 Emask 0x1 (device error) (Errors)

    Jan  5 16:25:57 NAS kernel: ata7.00: status: { DRDY ERR } (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7.00: error: { ABRT } (Errors)

    Jan  5 16:25:57 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

    Jan  5 16:25:57 NAS kernel: ata7.00: BMDMA2 stat 0x696d0009 (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:25:57 NAS kernel: ata7.00: cmd 25/00:00:27:4f:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:25:57 NAS kernel:          res 51/04:60:c7:4f:b2/00:03:10:00:00/e0 Emask 0x1 (device error) (Errors)

    Jan  5 16:25:57 NAS kernel: ata7.00: status: { DRDY ERR } (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7.00: error: { ABRT } (Errors)

    Jan  5 16:25:57 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

    Jan  5 16:25:57 NAS kernel: ata7.00: BMDMA2 stat 0x616d0009 (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:25:57 NAS kernel: ata7.00: cmd 25/00:00:27:53:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:25:57 NAS kernel:          res 51/04:f0:37:53:b2/00:03:10:00:00/e0 Emask 0x1 (device error) (Errors)

    Jan  5 16:25:57 NAS kernel: ata7.00: status: { DRDY ERR } (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7.00: error: { ABRT } (Errors)

    Jan  5 16:25:57 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

    Jan  5 16:25:57 NAS kernel: ata7.00: BMDMA2 stat 0x686d0009 (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:25:57 NAS kernel: ata7.00: cmd 25/00:00:27:57:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:25:57 NAS kernel:          res 51/04:60:c7:5a:b2/00:00:10:00:00/e0 Emask 0x1 (device error) (Errors)

    Jan  5 16:25:57 NAS kernel: ata7.00: status: { DRDY ERR } (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7.00: error: { ABRT } (Errors)

    Jan  5 16:25:57 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:25:57 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: BMDMA2 stat 0x616d0009 (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:25:58 NAS kernel: ata7.00: cmd 25/00:00:27:63:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:25:58 NAS kernel:          res 51/04:f0:37:64:b2/00:02:10:00:00/e0 Emask 0x1 (device error) (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: status: { DRDY ERR } (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: error: { ABRT } (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: BMDMA2 stat 0x686d0009 (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:25:58 NAS kernel: ata7.00: cmd 25/00:00:27:63:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:25:58 NAS kernel:          res 51/04:f0:37:64:b2/00:02:10:00:00/e0 Emask 0x1 (device error) (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: status: { DRDY ERR } (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: error: { ABRT } (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: BMDMA2 stat 0x686d0009 (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:25:58 NAS kernel: ata7.00: cmd 25/00:00:27:63:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:25:58 NAS kernel:          res 51/04:00:27:66:b2/00:01:10:00:00/e0 Emask 0x1 (device error) (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: status: { DRDY ERR } (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: error: { ABRT } (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: BMDMA2 stat 0x616d0009 (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:25:58 NAS kernel: ata7.00: cmd 25/00:00:27:6f:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:25:58 NAS kernel:          res 51/04:50:d7:6f:b2/00:03:10:00:00/e0 Emask 0x1 (device error) (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: status: { DRDY ERR } (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: error: { ABRT } (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: BMDMA2 stat 0x616d0009 (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:25:58 NAS kernel: ata7.00: cmd 25/00:00:27:7b:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:25:58 NAS kernel:          res 51/04:30:f7:7e:b2/00:00:10:00:00/e0 Emask 0x1 (device error) (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: status: { DRDY ERR } (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: error: { ABRT } (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7: drained 65536 bytes to clear DRQ (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:25:58 NAS kernel: ata7.00: cmd 25/00:00:27:7f:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:25:58 NAS kernel:          res ff/ff:ff:ff:ff:ff/ff:ff:ff:ff:ff/ff Emask 0x2 (HSM violation) (Errors)

    Jan  5 16:25:58 NAS kernel: ata7.00: status: { Busy } (Drive related)

    Jan  5 16:25:58 NAS kernel: ata7.00: error: { ICRC UNC IDNF ABRT } (Errors)

    Jan  5 16:25:58 NAS kernel: ata7: hard resetting link (Minor Issues)

    Jan  5 16:25:59 NAS kernel: ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 310) (Drive related)

    Jan  5 16:25:59 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:25:59 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:25:59 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

    Jan  5 16:25:59 NAS kernel: ata7.00: BMDMA2 stat 0x686d0009 (Drive related)

    Jan  5 16:25:59 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:25:59 NAS kernel: ata7.00: cmd 25/00:00:27:83:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:25:59 NAS kernel:          res 51/04:a0:87:83:b2/00:03:10:00:00/e0 Emask 0x1 (device error) (Errors)

    Jan  5 16:25:59 NAS kernel: ata7.00: status: { DRDY ERR } (Drive related)

    Jan  5 16:25:59 NAS kernel: ata7.00: error: { ABRT } (Errors)

    Jan  5 16:25:59 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:25:59 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:26:29 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors)

    Jan  5 16:26:29 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:26:29 NAS kernel: ata7.00: cmd 25/00:00:27:83:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:26:29 NAS kernel:          res 40/00:a0:87:83:b2/00:03:10:00:00/e0 Emask 0x4 (timeout) (Errors)

    Jan  5 16:26:29 NAS kernel: ata7.00: status: { DRDY } (Drive related)

    Jan  5 16:26:29 NAS kernel: ata7: hard resetting link (Minor Issues)

    Jan  5 16:26:29 NAS kernel: ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 310) (Drive related)

    Jan  5 16:26:29 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:26:29 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:26:29 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

    Jan  5 16:26:29 NAS kernel: ata7.00: BMDMA2 stat 0x616d0009 (Drive related)

    Jan  5 16:26:29 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:26:29 NAS kernel: ata7.00: cmd 25/00:00:27:8b:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:26:29 NAS kernel:          res 51/04:20:07:8e:b2/00:01:10:00:00/e0 Emask 0x1 (device error) (Errors)

    Jan  5 16:26:29 NAS kernel: ata7.00: status: { DRDY ERR } (Drive related)

    Jan  5 16:26:29 NAS kernel: ata7.00: error: { ABRT } (Errors)

    Jan  5 16:26:29 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:26:29 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:26:29 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

    Jan  5 16:26:29 NAS kernel: ata7.00: BMDMA2 stat 0x686d0009 (Drive related)

    Jan  5 16:26:29 NAS kernel: ata7.00: failed command: READ DMA EXT (Minor Issues)

    Jan  5 16:26:29 NAS kernel: ata7.00: cmd 25/00:00:27:8b:b2/00:04:10:00:00/e0 tag 0 dma 524288 in (Drive related)

    Jan  5 16:26:29 NAS kernel:          res 51/04:c0:67:8b:b2/00:03:10:00:00/e0 Emask 0x1 (device error) (Errors)

    Jan  5 16:26:29 NAS kernel: ata7.00: status: { DRDY ERR } (Drive related)

    Jan  5 16:26:29 NAS kernel: ata7.00: error: { ABRT } (Errors)

    Jan  5 16:26:29 NAS kernel: ata7.00: configured for UDMA/33 (Drive related)

    Jan  5 16:26:29 NAS kernel: ata7: EH complete (Drive related)

    Jan  5 16:26:29 NAS kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

    Jan  5 16:26:29 NAS kernel: ata7.00: BMDMA2 stat 0x686d0009 (Drive related)

     

     

     

    hardware:

     

    Intel® Celeron® CPU        E1500  @ 2.20GHz

    3 sata controller 

    for more information i must look

     

    my hardware are collected the last years :-)....every year one new....when i have money

  • Quote

    Are the original problem disks and the one that is showing errors now on the same controller?

     

    Try reseating the controllers, SATA and power cables.

     

    Do you have a monitor and keyboard attached? You should do a memory test. You can select memtest from the unRAID boot menu.

  • Quote
    • Author

    ::)....cancel rebuild?

     

    yes monitor and keyboard ....and i know the memtet @ bootmenu

     

    hardware:

     

    Asus P5G41-M LE

    Promise 4x sata controller

    Ultron US-220 2x sata Controller

    SAS3082E-R PCI-Express SAS RAID Controller

  • Quote

    ::)....cancel rebuild?

     

    yes monitor and keyboard ....and i know the memtet @ bootmenu

    Since it is just a parity rebuild and it doesn't seem to be going well, go ahead and cancel and see if we can fix your hardware problems.

  • Quote
    • Author

    ok i cancel the data rebuild now  :-X

     

    and test the hardware......

     

    than i do a memtest...

  • Quote
    • Author

    ok...memtest was great..no errors....

     

    than i test the hardware.....i mean i have found the problem....every time i have an error on one disk and the same controller (Ultron US-220 2x sata Controller)

     

    i put it out of my server an the disks at the SAS Controller.

     

    and now i have the parity start with a nice speed :)

     

    look picture

     

    in the syslog only minor issues....is that ok?

     

    age 30, max trans age 30 (Routine)

    Jan  5 18:31:51 NAS kernel: REISERFS (device md11): checking transaction log (md11) (Routine)

    Jan  5 18:31:51 NAS kernel: REISERFS (device md11): replayed 2 transactions in 0 seconds (Minor Issues)

    Jan  5 18:31:51 NAS kernel: REISERFS (device md11): Using r5 hash to sort names (Routine)

    Jan  5 18:31:51 NAS emhttp: shcmd (47): mkdir /mnt/disk12 (Routine)

    Jan  5 18:31:51 NAS emhttp: shcmd (48): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md12 /mnt/disk12 |$stuff$ logger (Other emhttp)

    Jan  5 18:31:51 NAS kernel: REISERFS (device md12): found reiserfs format "3.6" with standard journal (Routine)

    Jan  5 18:31:51 NAS kernel: REISERFS (device md12): using ordered data mode (Routine)

    Jan  5 18:31:51 NAS kernel: reiserfs: using flush barriers

    Jan  5 18:31:51 NAS kernel: REISERFS (device md12): journal params: device md12, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 (Routine)

    Jan  5 18:31:51 NAS kernel: REISERFS (device md12): checking transaction log (md12) (Routine)

    Jan  5 18:31:51 NAS kernel: REISERFS (device md12): replayed 2 transactions in 0 seconds (Minor Issues)

    Jan  5 18:31:51 NAS kernel: REISERFS (device md12): Using r5 hash to sort names (Routine)

    Jan  5 18:31:51 NAS emhttp: shcmd (49): mkdir /mnt/disk14 (Routine)

    Jan  5 18:31:51 NAS emhttp: shcmd (50): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md14 /mnt/disk14 |$stuff$ logger (Other emhttp)

    Jan  5 18:31:51 NAS kernel: REISERFS (device md14): found reiserfs format "3.6" with standard journal (Routine)

    Jan  5 18:31:51 NAS kernel: REISERFS (device md14): using ordered data mode (Routine)

    Jan  5 18:31:51 NAS kernel: reiserfs: using flush barriers

    Jan  5 18:31:51 NAS kernel: REISERFS (device md14): journal params: device md14, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 (Routine)

    Jan  5 18:31:51 NAS kernel: REISERFS (device md14): checking transaction log (md14) (Routine)

    Jan  5 18:31:51 NAS kernel: REISERFS (device md14): replayed 2 transactions in 0 seconds (Minor Issues)

    Jan  5 18:31:51 NAS kernel: REISERFS (device md14): Using r5 hash to sort names (Routine)

    Jan  5 18:31:52 NAS emhttp: shcmd (51): mkdir /mnt/user (Other emhttp)

    Jan  5 18:31:52 NAS emhttp: shcmd (52): /usr/local/sbin/shfs /mnt/user -disks 16777214 -o noatime,big_writes,allow_other -o remember=330  |$stuff$ logger (Other emhttp)

    Jan  5 18:31:52 NAS emhttp: shcmd (53): crontab -c /etc/cron.d -d $stuff$> /dev/null (Other emhttp)

    Jan  5 18:31:52 NAS emhttp: shcmd (54): /usr/local/sbin/emhttp_event disks_mounted (Other emhttp)

    Jan  5 18:31:52 NAS emhttp_event: disks_mounted (Other emhttp)

    Jan  5 18:31:52 NAS kernel: mdcmd (55): check CORRECT (unRAID engine)

    Jan  5 18:31:52 NAS kernel: md: recovery thread woken up ... (unRAID engine)

    Jan  5 18:31:52 NAS kernel: md: recovery thread syncing parity disk ... (unRAID engine)

    Jan  5 18:31:52 NAS kernel: md: using 1536k window, over a total of 1953514552 blocks. (unRAID engine)

    Jan  5 18:31:53 NAS emhttp: shcmd (55): :>/etc/samba/smb-shares.conf (Other emhttp)

    Jan  5 18:31:53 NAS emhttp: shcmd (56): cp /etc/exports- /etc/exports (Other emhttp)

    Jan  5 18:31:53 NAS avahi-daemon[1304]: Files changed, reloading.

    Jan  5 18:31:53 NAS emhttp: Restart SMB... (Other emhttp)

    Jan  5 18:31:53 NAS emhttp: shcmd (57): killall -HUP smbd (Minor Issues)

    Jan  5 18:31:53 NAS emhttp: shcmd (58): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service (Other emhttp)

    Jan  5 18:31:53 NAS avahi-daemon[1304]: Files changed, reloading.

    Jan  5 18:31:53 NAS avahi-daemon[1304]: Service group file /services/smb.service changed, reloading.

    Jan  5 18:31:53 NAS emhttp: shcmd (59): ps axc | grep -q rpc.mountd (Other emhttp)

    Jan  5 18:31:53 NAS emhttp: Restart NFS... (Other emhttp)

    Jan  5 18:31:53 NAS emhttp: shcmd (60): exportfs -ra |$stuff$ logger (Other emhttp)

    Jan  5 18:31:53 NAS emhttp: shcmd (61): /usr/local/sbin/emhttp_event svcs_restarted (Other emhttp)

    Jan  5 18:31:53 NAS emhttp_event: svcs_restarted (Other emhttp)

    Jan  5 18:31:53 NAS emhttp: shcmd (62): /usr/local/sbin/emhttp_event started (Other emhttp)

    Jan  5 18:31:53 NAS emhttp_event: started (Other emhttp)

    Jan  5 18:31:54 NAS avahi-daemon[1304]: Service "NAS" (/services/smb.service) successfully established.

     

    Zwischenablage02.jpg.38cdaa6ecfa3cbc296b0b97cbc63c2d3.jpg

  • Quote
    • Author

    hello all :)

     

    i'm a little bit happy.....i have bring back my 2 disks in the array...clearing and mounting without problems!!

     

    why a little bit?-----i lost the data on the two disks :-X

     

    i say thx to all

  • Quote

    • Archived

    This topic is now archived and is closed to further replies.

    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.