Hi

 

I've been trying to get Suspend to RAM (S3?) working on my UnRaid 4.7 box. But so far I have trouble getting the disks back to a working state when I wake up the machine.

 

I have a total of 6 disks:

 

Parity: WDC WD20EARS-00M (2TB) (sda)

Cache: WDC WD10EADS-00L (1TB) (sdf)

Disk1-3: WDC WD10EADS-00L (1TB) (sdb, sdc, sdg)

Disk4: WDC WD20EARS-00M (2TB) (sdd)

 

 

For testing purpose, I wait for the disks to go to standby mode:

 

hdparm -C /dev/sda /dev/sdc /dev/sdg /dev/sdb /dev/sdd

 

and wait for them all to report "standby".

 

Then I issue the command

 

echo 3 > /proc/acpi/sleep

 

to put the server to sleep.

 

To wake it up again, I use etherwake from my linux PC. The server wakes up and responds to ping. I can also telnet back, so everything seems fine so far.

 

But... If I do a "mdcmd status", I get "DISK_DSBL" for my parity disk.

Also, when listing /dev, sda, sdb, sdc and sdd is missing completely!

 

output from "dmesg" after the resume from S3 is the following:

 

...

ata2: SATA link down (SStatus 0 SControl 300)

usb 1-6: reset high speed USB device using ehci_hcd and address 2

sd 3:0:0:0: [sdf] Starting disk

ata4: link is slow to respond, please be patient (ready=0)

ata3: link is slow to respond, please be patient (ready=0)

ata3.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out

ata3.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out

ata3.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded

ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out

ata3.00: configured for UDMA/133

ata3.00: configured for UDMA/133

ata3: EH complete

sd 4:0:0:0: [sdg] Starting disk

ata4.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out

ata4.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out

ata4.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded

ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out

ata1: softreset failed (device not ready)

ata4.00: configured for UDMA/133

ata4.00: configured for UDMA/133

ata4: EH complete

Restarting tasks ... done.

md: disk0 write error

handle_stripe write error: 128/0, count: 1

md: recovery thread woken up ...

md: recovery thread has nothing to resync

ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Hangcheck: hangcheck value past margin!

mdcmd (25): spindown 1

mdcmd (26): spindown 3

mdcmd (27): spindown 4

mdcmd (28): spindown 1

mdcmd (29): spindown 3

...

 

mount yields this:

fusectl on /sys/fs/fuse/connections type fusectl (rw)

usbfs on /proc/bus/usb type usbfs (rw)

/dev/sde1 on /boot type vfat (rw,noatime,nodiratime,umask=0,shortname=mixed)

/dev/sdf1 on /mnt/cache type reiserfs (rw,noatime,nodiratime,noacl,nouser_xattr)

/dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime,noacl,nouser_xattr)

/dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime,noacl,nouser_xattr)

/dev/md3 on /mnt/disk3 type reiserfs (rw,noatime,nodiratime,noacl,nouser_xattr)

/dev/md4 on /mnt/disk4 type reiserfs (rw,noatime,nodiratime,noacl,nouser_xattr)

shfs on /mnt/user type fuse.shfs (rw,nosuid,nodev,noatime,allow_other,default_permissions)

shfs on /mnt/user0 type fuse.shfs (rw,nosuid,nodev,noatime,allow_other,default_permissions)

 

 

 

What can I do from here? Any help is highly appreciated :-)

 

/Thomas

Further investigation seems to points towards this being an issue with my Zotac NM10 mainboard, not being able to re-activate the onboard raid controller. Fits perfectly into the scenario, where 4 disks are missing after resume from S3 (the raid controller supports 4 drives)

 

I'll try adding another raid controller to the system later this week.

Solved :-)

 

Luckily I didn't have to try a new raid controller. Turned out, that the onboard one wasn't set to wakeup after S3, so a simple addition to the GO script did the trick:

 

echo "enabled" >/sys/devices/pci0000\:00/0000\:00\:1c.0/power/wakeup

echo "enabled" >/sys/devices/pci0000\:00/0000\:00\:1c.3/power/wakeup

 

Where the device numbers were taken from

 

#lspci -tv
-[0000:00]-+-00.0  Intel Corporation Unknown device a000
           +-02.0  Intel Corporation Unknown device a001
           +-02.1  Intel Corporation Unknown device a002
           +-1b.0  Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller
           +-1c.0-[0000:01]--+-00.0  JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller
           |                 \-00.1  JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller
           +-1c.3-[0000:02]----00.0  Atheros Communications Inc. Unknown device 002b
           +-1d.0  Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1
           +-1d.1  Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2
           +-1d.2  Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3
           +-1d.3  Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4
           +-1d.7  Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller
           +-1e.0-[0000:03]----0b.0  Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet
           +-1f.0  Intel Corporation Unknown device 27bc
           +-1f.2  Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Controller
           \-1f.3  Intel Corporation 82801G (ICH7 Family) SMBus Controller

 

Now all I need is to figure out how to make the server wakeup when I need to access the storage