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.

Lots of errors, is my controller failing?

Featured Replies

Been running the same hardware for a long time now.  Started getting errors on all drives.  Shut down and did a fresh boot.  Here's the complete syslog.  Is my AOC-SAS2LP-MV8 failing??

 

 

syslog.zip

It looks like most of the errors are relating to ST3500630AS, (your cache drive).

 

I'm seeing three different things here:

 

1 - ata11.00: failed command: READ FPDMA QUEUED

 

These errors are usually (but not necessarily always) related to bad / loose cabling and/or power to the drive

 

2 - ata11.00: device reported invalid CHS sector 0

 

This could be a bad drive, but the only time I've ever seen it on one of my drives, it always went hand in hand with #1 and was narrowed down to a cabling issue

 

3 - BTRFS info (device sdh1): no csum found for inode 2928556 start 662118400

 

Looks like the file system on your cache is corrupted.  Possibly caused by cabling

 

 

You could have a bad drive, or a bad port but right now initially, I would go with bad or loose sas cables or a power problem (weak supply, too many splitters, etc)

 

If you're using hotswap bays, I would also definitely reseat the caddy

 

After you fix the hardware issues, then I would run a scrub on the drive

  • Author

Running a corsair 750 watt power supply with not splitters.

 

Gonna go swap out my 8087 SAS cables and see if that does the trick

Just noticed that you've got an issue with ata12.00: ATA-8: ST3000DM001-1CH166,            Z1F2XP1C.

 

ata12.00: failed to IDENTIFY (I/O error, err_mask=0x4)  Probably the same cabling issue.

 

Once we get rid of those hardware errors (1 & 2), then you can deal with the scrub (and/or save everything on the cache and reformat it)

 

 

Archived

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

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.