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

Questions on new build with errors

Infotech
in unRAID Server 4.5 [No new topics]

Featured Replies

Hi

 

I just build my first Unraid 4.5.6 server last night after researching on this forum. I am currently running WHS but will be moving over to Unraid once everything has been tested and working. I took a quick look at the log before leaving to work and notice the build has been completed but with some errors in red. The screen showing all 5 drives blinking in blue. Been researching on this forum but could find any info on the error below. I don't have the full log with me right now but can provide it later if needed. Beside the error below I also notice some error on smart data not being pulled from Hard drives. Not sure if it related to the raid card. Any help would be appreciates. Thanks

 

Norco 4220 case

Areca 1260 16 ports Raid card in JBOD

8 (used) WD20EADS ( 5 being used for current unraid test build, 3 for scenario simulations testing later)

Gigabyte EG45-DS2H (not ideal for unraid but that's what I have laying around for testing)

4 gig Gskills

 

 

 

Sep 23 06:13:38 Tower kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:38 Tower kernel: mdcmd (5401): spindown 2

Sep 23 06:13:38 Tower kernel: md: disk2: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:38 Tower kernel: mdcmd (5402): spindown 3

Sep 23 06:13:38 Tower kernel: md: disk3: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:38 Tower kernel: mdcmd (5403): spindown 4

Sep 23 06:13:38 Tower kernel: md: disk4: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:39 Tower kernel: mdcmd (5405): spindown 0

Sep 23 06:13:39 Tower kernel: md: disk0: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:39 Tower kernel: mdcmd (5406): spindown 1

Sep 23 06:13:39 Tower kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:39 Tower kernel: mdcmd (5407): spindown 2

Sep 23 06:13:39 Tower kernel: md: disk2: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:39 Tower kernel: mdcmd (5408): spindown 3

Sep 23 06:13:39 Tower kernel: md: disk3: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:39 Tower kernel: mdcmd (5409): spindown 4

Sep 23 06:13:39 Tower kernel: md: disk4: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:48 Tower emhttp: Spinning up all drives...

Sep 23 06:13:48 Tower kernel: mdcmd (5410): spinup 0

Sep 23 06:13:48 Tower kernel: md: disk0: ATA_OP_SETIDLE1 ioctl error: -22

Sep 23 06:13:48 Tower kernel: mdcmd (5411): spinup 1

Sep 23 06:13:48 Tower kernel: md: disk1: ATA_OP_SETIDLE1 ioctl error: -22

Sep 23 06:13:48 Tower kernel: mdcmd (5412): spinup 2

Sep 23 06:13:48 Tower kernel: md: disk2: ATA_OP_SETIDLE1 ioctl error: -22

Sep 23 06:13:48 Tower kernel: mdcmd (5413): spinup 3

Sep 23 06:13:48 Tower kernel: md: disk3: ATA_OP_SETIDLE1 ioctl error: -22

Sep 23 06:13:48 Tower kernel: mdcmd (5414): spinup 4

Sep 23 06:13:48 Tower kernel: md: disk4: ATA_OP_SETIDLE1 ioctl error: -22

Sep 23 06:13:48 Tower emhttp: disk_temperature: ioctl (smart_enable): Invalid argument

 

Hi

 

I just build my first Unraid 4.5.6 server last night after researching on this forum. I am currently running WHS but will be moving over to Unraid once everything has been tested and working. I took a quick look at the log before leaving to work and notice the build has been completed but with some errors in red. The screen showing all 5 drives blinking in blue. Been researching on this forum but could find any info on the error below. I don't have the full log with me right now but can provide it later if needed. Beside the error below I also notice some error on smart data not being pulled from Hard drives. Not sure if it related to the raid card. Any help would be appreciates. Thanks

 

Norco 4220 case

Areca 1260 16 ports Raid card in JBOD

8 (used) WD20EADS ( 5 being used for current unraid test build, 3 for scenario simulations testing later)

Gigabyte EG45-DS2H (not ideal for unraid but that's what I have laying around for testing)

4 gig Gskills

 

 

 

Sep 23 06:13:38 Tower kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:38 Tower kernel: mdcmd (5401): spindown 2

Sep 23 06:13:38 Tower kernel: md: disk2: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:38 Tower kernel: mdcmd (5402): spindown 3

Sep 23 06:13:38 Tower kernel: md: disk3: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:38 Tower kernel: mdcmd (5403): spindown 4

Sep 23 06:13:38 Tower kernel: md: disk4: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:39 Tower kernel: mdcmd (5405): spindown 0

Sep 23 06:13:39 Tower kernel: md: disk0: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:39 Tower kernel: mdcmd (5406): spindown 1

Sep 23 06:13:39 Tower kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:39 Tower kernel: mdcmd (5407): spindown 2

Sep 23 06:13:39 Tower kernel: md: disk2: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:39 Tower kernel: mdcmd (5408): spindown 3

Sep 23 06:13:39 Tower kernel: md: disk3: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:39 Tower kernel: mdcmd (5409): spindown 4

Sep 23 06:13:39 Tower kernel: md: disk4: ATA_OP_STANDBYNOW1 ioctl error: -22

Sep 23 06:13:48 Tower emhttp: Spinning up all drives...

Sep 23 06:13:48 Tower kernel: mdcmd (5410): spinup 0

Sep 23 06:13:48 Tower kernel: md: disk0: ATA_OP_SETIDLE1 ioctl error: -22

Sep 23 06:13:48 Tower kernel: mdcmd (5411): spinup 1

Sep 23 06:13:48 Tower kernel: md: disk1: ATA_OP_SETIDLE1 ioctl error: -22

Sep 23 06:13:48 Tower kernel: mdcmd (5412): spinup 2

Sep 23 06:13:48 Tower kernel: md: disk2: ATA_OP_SETIDLE1 ioctl error: -22

Sep 23 06:13:48 Tower kernel: mdcmd (5413): spinup 3

Sep 23 06:13:48 Tower kernel: md: disk3: ATA_OP_SETIDLE1 ioctl error: -22

Sep 23 06:13:48 Tower kernel: mdcmd (5414): spinup 4

Sep 23 06:13:48 Tower kernel: md: disk4: ATA_OP_SETIDLE1 ioctl error: -22

Sep 23 06:13:48 Tower emhttp: disk_temperature: ioctl (smart_enable): Invalid argument

 

From what I can see, your RAID card does not support the command to spin down the disks.  Nor does it seems to support reading the disk temperatures.

 

If it is working otherwise, you'll probably be fine... just disable disk spin-down in the web-interface to keep your log from filling with those error messages.

  • Author

Thanks Joe for your quick reply. Feel more comfortable now moving forward with my testing. Do you know if there any tool/utility that can pulled temp/smart data for monitor purpose?

Thanks Joe for your quick reply. Feel more comfortable now moving forward with my testing. Do you know if there any tool/utility that can pulled temp/smart data for monitor purpose?

You can try

smartctl -d ata -a /dev/sdX

where sdX = the device you are testing.

  • Author

I went into Areca Bios and there is an HD spin down option (1-60 minute). My question: if I changed spin down to off in Unraid and set spin down to 60 minutes on Areca and when HD do spun down will Unraid trigger the spin up since it was set not to spin down?

 

 

I went into Areca Bios and there is an HD spin down option (1-60 minute). My question: if I changed spin down to off in Unraid and set spin down to 60 minutes on Areca and when HD do spun down will Unraid trigger the spin up since it was set not to spin down?

 

 

unRAID specifically does not spin up the drives, the OS driver does when a disk is accessed.  Therefore, an access should spin up a drive.

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.