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.

shooga

Members
  • Joined

  • Last visited

Everything posted by shooga

  1. Thanks for the reply on my slow preclear Joe. I am seeing the following errors: This one is repeated over and over again: Feb 26 21:46:17 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Feb 26 21:46:17 Bunker kernel: ata4.00: BMDMA2 stat 0xd0009 Feb 26 21:46:17 Bunker kernel: ata4.00: failed command: READ DMA Feb 26 21:46:17 Bunker kernel: ata4.00: cmd c8/00:00:20:a2:ed/00:00:00:00:00/e0 tag 0 dma 131072 in Feb 26 21:46:17 Bunker kernel: res 51/40:df:3c:a2:ed/00:00:00:00:00/f0 Emask 0x9 (media error) Feb 26 21:46:17 Bunker kernel: ata4.00: status: { DRDY ERR } Feb 26 21:46:17 Bunker kernel: ata4.00: error: { UNC } Feb 26 21:46:25 Bunker kernel: ata4.00: configured for UDMA/100 Feb 26 21:46:25 Bunker kernel: ata4: EH complete This one shows up less frequently: Feb 26 21:46:39 Bunker kernel: end_request: I/O error, dev sdd, sector 15573615 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946701 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946702 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946703 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946704 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946705 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946706 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946707 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946708 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946709 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946710 Strangely though, it looks like later in the log those errors are showing for a different drive: complete Feb 27 16:10:51 Bunker kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Feb 27 16:10:51 Bunker kernel: ata2.00: BMDMA2 stat 0x6c0009 Feb 27 16:10:51 Bunker kernel: ata2: SError: { BadCRC } Feb 27 16:10:51 Bunker kernel: ata2.00: failed command: READ DMA Feb 27 16:10:51 Bunker kernel: ata2.00: cmd c8/00:00:e8:10:0a/00:00:00:00:00/e1 tag 0 dma 131072 in Feb 27 16:10:51 Bunker kernel: res 51/40:00:2b:11:0a/00:00:00:00:00/11 Emask 0x9 (media error) Feb 27 16:10:51 Bunker kernel: ata2.00: status: { DRDY ERR } Feb 27 16:10:51 Bunker kernel: ata2.00: error: { UNC } Feb 27 16:10:51 Bunker kernel: ata2.00: configured for UDMA/100 Feb 27 16:10:51 Bunker kernel: ata2: EH complete Feb 27 16:10:54 Bunker kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Feb 27 16:10:54 Bunker kernel: ata2.00: BMDMA2 stat 0x6c0009 Feb 27 16:10:54 Bunker kernel: ata2: SError: { BadCRC } Feb 27 16:10:54 Bunker kernel: ata2.00: failed command: READ DMA Feb 27 16:10:54 Bunker kernel: ata2.00: cmd c8/00:00:e8:10:0a/00:00:00:00:00/e1 tag 0 dma 131072 in Feb 27 16:10:54 Bunker kernel: res 51/40:00:2b:11:0a/00:00:00:00:00/11 Emask 0x9 (media error) Feb 27 16:10:54 Bunker kernel: ata2.00: status: { DRDY ERR } Feb 27 16:10:54 Bunker kernel: ata2.00: error: { UNC } Feb 27 16:10:54 Bunker kernel: ata2.00: configured for UDMA/100 Feb 27 16:10:54 Bunker kernel: ata2: EH complete Feb 27 16:10:57 Bunker kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Feb 27 16:10:57 Bunker kernel: ata2.00: BMDMA2 stat 0x6c0009 Feb 27 16:10:57 Bunker kernel: ata2: SError: { BadCRC } Feb 27 16:10:57 Bunker kernel: ata2.00: failed command: READ DMA Feb 27 16:10:57 Bunker kernel: ata2.00: cmd c8/00:00:e8:10:0a/00:00:00:00:00/e1 tag 0 dma 131072 in Feb 27 16:10:57 Bunker kernel: res 51/40:00:2b:11:0a/00:00:00:00:00/11 Emask 0x9 (media error) Feb 27 16:10:57 Bunker kernel: ata2.00: status: { DRDY ERR } Feb 27 16:10:57 Bunker kernel: ata2.00: error: { UNC } Feb 27 16:10:57 Bunker kernel: ata2.00: configured for UDMA/100 Feb 27 16:10:57 Bunker kernel: sd 1:0:0:0: [sdb] Unhandled sense code Feb 27 16:10:57 Bunker kernel: sd 1:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 Feb 27 16:10:57 Bunker kernel: sd 1:0:0:0: [sdb] Sense Key : 0x3 [current] [descriptor] Feb 27 16:10:57 Bunker kernel: Descriptor sense data with sense descriptors (in hex): Feb 27 16:10:57 Bunker kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Feb 27 16:10:57 Bunker kernel: 01 0a 11 2b Feb 27 16:10:57 Bunker kernel: sd 1:0:0:0: [sdb] ASC=0x11 ASCQ=0x4 Feb 27 16:10:57 Bunker kernel: sd 1:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 01 0a 10 e8 00 01 00 00 Feb 27 16:10:57 Bunker kernel: end_request: I/O error, dev sdb, sector 17436971 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179621 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179622 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179623 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179624 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179625 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179626 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179627 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179628 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179629 Feb 27 16:10:57 Bunker kernel: ata2: EH complete Feb 27 16:11:00 Bunker kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Feb 27 16:11:00 Bunker kernel: ata2.00: BMDMA2 stat 0x6c0009 Feb 27 16:11:00 Bunker kernel: ata2: SError: { BadCRC } Feb 27 16:11:00 Bunker kernel: ata2.00: failed command: READ DMA Feb 27 16:11:00 Bunker kernel: ata2.00: cmd c8/00:08:28:11:0a/00:00:00:00:00/e1 tag 0 dma 4096 in Feb 27 16:11:00 Bunker kernel: res 51/40:00:2b:11:0a/00:00:00:00:00/11 Emask 0x9 (media error) Feb 27 16:11:00 Bunker kernel: ata2.00: status: { DRDY ERR } Feb 27 16:11:00 Bunker kernel: ata2.00: error: { UNC } Feb 27 16:11:00 Bunker kernel: ata2.00: configured for UDMA/100 Feb 27 16:11:00 Bunker kernel: ata2: EH complete Feb 27 16:11:03 Bunker kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Feb 27 16:11:03 Bunker kernel: ata2.00: BMDMA2 stat 0x6c0009 Feb 27 16:11:03 Bunker kernel: ata2: SError: { BadCRC } Feb 27 16:11:03 Bunker kernel: ata2.00: failed command: READ DMA Feb 27 16:11:03 Bunker kernel: ata2.00: cmd c8/00:08:28:11:0a/00:00:00:00:00/e1 tag 0 dma 4096 in Feb 27 16:11:03 Bunker kernel: res 51/40:00:2b:11:0a/00:00:00:00:00/11 Emask 0x9 (media error) Feb 27 16:11:03 Bunker kernel: ata2.00: status: { DRDY ERR } Feb 27 16:11:03 Bunker kernel: ata2.00: error: { UNC } Feb 27 16:11:03 Bunker kernel: ata2.00: configured for UDMA/100 Feb 27 16:11:03 Bunker kernel: ata2: EH complete Advice? Are these drives hosed?
  2. I posted this previously, but have a feeling it was either not specific enough or got lost because the thread went to the next page. Trying one more time just in case: I have a WD15EADS that a friend gave me from his old stash. It's preclearing MUCH slower than other drives I've been preclearing and adding to my new server. After 9 hours it's only 40% through pre-reading the first of two cycles - unMenu is showing 18MB/s (now 12MB/s) but it started out at 3MB/s. Besides this one, the slowest drives I've pre-read have gone at more like 40MB/s and the first drives were liike 2-3x that even. Is this just a sign that it's a very old slow drive? Or would this mean that something is wrong? I can post the preclear results when the drive is finished, but at this rate it's going to take another 5 days to finish the 2 cycles I'm running.
  3. I have a WD15EADS that a friend gave me from his old stash. It's preclearing MUCH slower than other drives I've been preclearing and adding to my new server. After 9 hours it's only 40% through pre-reading the first of two cycles - unMenu is showing 18MB/s but it started out at 3MB/s. Besides this one, the slowest drives I've precleared have gone at more like 40MB/s and the first drives were liike 2-3x that even. Is this just a sign that it's a very old slow drive? Or would this mean that something is wrong? I can post the preclear results when the drive is finished, but at this rate it's going to take another 5 days to finish the 2 cycles I'm running.

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.