Shutdown deamon not working on NAS326

Projektleiter: Mijzelf

Some daemon to control NAS operations, shutdown, FTPES and more
Supernils
Beiträge: 10
Registriert: Sa 19. Feb 2022, 12:33

Shutdown deamon not working on NAS326

Beitrag von Supernils »

Hello @Mijzelf,
I bought a used NAS326. Unfortunately, the NAS is not shut down by the shutdown daemon. I also have a NAS540 where it works.
I think it works one time after first installation of Tweaks, but then never again.

Is it a known issue? I would appreciate your help.

Best Regards
Nils

Mijzelf
Beiträge: 133
Registriert: Mi 14. Nov 2018, 19:50

Re: Shutdown deamon not working on NAS326

Beitrag von Mijzelf »

It's not a know bug.

What does the 'status' have to say when it should shutdown but doesn't?
shutdown-daemon.png
shutdown-daemon.png (41.99 KiB) 1816 mal betrachtet

Supernils
Beiträge: 10
Registriert: Sa 19. Feb 2022, 12:33

Re: Shutdown deamon not working on NAS326

Beitrag von Supernils »

Hello @Mijzelf,

Sorry for the late response.

These are my settings and the status
nas_shutdown.png
nas_shutdown.png (31.73 KiB) 1713 mal betrachtet
It seems like Disk0 is not going to sleep as long I am observing the status via the browser. For sure, both Disks are going to sleep.

Mijzelf
Beiträge: 133
Registriert: Mi 14. Nov 2018, 19:50

Re: Shutdown deamon not working on NAS326

Beitrag von Mijzelf »

Yes, it is possible that the webserver will keep the disk awake. It's also possible to read this status using ssh or telnet. Login as admin, and execute

Code: Alles auswählen

cd /tmp/.Tweaks/shutdown
(That is on a ramdisk) Leave the shell open, a new login can spin up the disks. Now your can see the status with

Code: Alles auswählen

cat status
The script which generates the status file is in the same directory, is auto generated by Tweaks, and is called 'script'. Further you have a script 'kernellogtarget', where the kernel log is piped through, to catch the disk spinup and -down messages.
You can execute dmesg to see those messages, it looks like

Code: Alles auswählen

[  993.140024] 
[  993.140026] ****** disk(2:0:0:0) spin down at 69311 ******
[ 1984.041334] 
[ 1984.041337] ****** disk(3:0:0:0) spin down at 168402 ******
[ 2162.093220] 
[ 2162.093223] ****** disk(3:0:0:0 0)(HD4) awaked by sshd (cmd: 28) ******
The result of the filtering is written to disk.log, for this sequence that is

Code: Alles auswählen

Tue Mar 8 10:39:57 CET 2022 Disk2: STANDBY
Tue Mar 8 10:56:28 CET 2022 Disk3: STANDBY
Tue Mar 8 10:59:26 CET 2022 Disk3: ACTIVE
The resulting status is in d_suspdtime:

Code: Alles auswählen

Disk2: STANDBY
Disk3: ACTIVE
If your disks indeed are sleeping, while it is not in the kernel log, then the script fails. If it is in the kernel log, but in a different way, I'd like to know how.

But honestly I think something is keeping your disk awake. If that is true, the Tweak 'Disk monitor' might tell what.

Supernils
Beiträge: 10
Registriert: Sa 19. Feb 2022, 12:33

Re: Shutdown deamon not working on NAS326

Beitrag von Supernils »

You are right. Disk0 is not sleeping according to your script. But the LEDs are indicating that both disks are sleeping :?
Should I not trust the LEDs?

I will check the Disk monitor tweak

Mijzelf
Beiträge: 133
Registriert: Mi 14. Nov 2018, 19:50

Re: Shutdown deamon not working on NAS326

Beitrag von Mijzelf »

Supernils hat geschrieben:
Mi 9. Mär 2022, 20:13
Should I not trust the LEDs?
I don't know. I haven't heard of this problem before. On the NAS5xx (and I think also on the 326) the leds are steered by hdidle. The ZyXEL version has one small patch, which sets the leds when hdidle issues a disk spindown, or detects a spinup.
I can't remember how the kernel detects disk spindown/up.
Don't know if hdparm is installed on your NAS, it is included in RandomTools. It can ask the status of the disk directly (as root):

Code: Alles auswählen

hdparm -C /dev/sda
hdparm -C /dev/sdb
Make sure you don't spinup the disk by logging in as root. Maybe you'd login and then leave the shell until the disk is sleeping again according to the leds.

Supernils
Beiträge: 10
Registriert: Sa 19. Feb 2022, 12:33

Re: Shutdown deamon not working on NAS326

Beitrag von Supernils »

Hello Mijzelf,

These are the results:

Code: Alles auswählen

root@NAS326:~# hdparm -C /dev/sdb

/dev/sdb:
 drive state is:  standby
root@NAS326:~# hdparm -C /dev/sda

/dev/sda:
 drive state is:  standby

admin@NAS326:/tmp/.Tweaks/shutdown$ cat status
Status of Sat Mar 12 11:00:01 CET 2022:
[ ] Disk0 is not asleep: ACTIVE
[X] Disk1 is asleep
btw. Disk0 is a 10tb wd100ezaz-11tdba0


Best Regards
Nils

Mijzelf
Beiträge: 133
Registriert: Mi 14. Nov 2018, 19:50

Re: Shutdown deamon not working on NAS326

Beitrag von Mijzelf »

Well, in that case the leds are right, and my script is wrong. Can you post the output of dmesg, and the corresponding disk.log, at the moment the problem is there?
(If you have troubles to do so, you can execute 'dmesg > dmesg.log' to create a file, and use WinSCP to pull it from the NAS.)

BTW, unfortunately it's not possible to use hdparm in the script, because asking it's status is enough to prevent it from sleeping. So for that reason I am dependent on the kernel logs.

Supernils
Beiträge: 10
Registriert: Sa 19. Feb 2022, 12:33

Re: Shutdown deamon not working on NAS326

Beitrag von Supernils »

Maybe this info is helpful. If the HDD is running then the state is 'unknown'.

Code: Alles auswählen

root@NAS326:~# hdparm -C /dev/sda

/dev/sda:
 drive state is:  unknown
dmesg.log

Code: Alles auswählen

Booting Linux on physical CPU 0x0
Linux version 3.10.39 (root@twsvnnt01652-01) (gcc version 4.8.5 20150209 (prerelease) (crosstool-NG 1.21.0) ) #1 Thu Apr 1 10:04:14 CST 2021
CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Marvell Armada 380/381/382/385/388 (Device Tree), model: Marvell Armada 380 STG-328
Memory policy: ECC disabled, Data cache writealloc
On node 0 totalpages: 131072
free_area_init_node: node 0, pgdat c0ec6024, node_mem_map c0f15000
  Normal zone: 1024 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 131072 pages, LIFO batch:31
CPU: All CPU(s) started in SVC mode.
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0 
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200 ubi.mtd=4,2048 rootfstype=ubifs root=ubi0:rootfs1 rw rootdelay=2
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 504252k/504252k available, 20036k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xe0800000 - 0xfff00000   ( 503 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc081c8a8   (8275 kB)
      .init : 0xc081d000 - 0xc0e6e55c   (6470 kB)
      .data : 0xc0e70000 - 0xc0ec70e0   ( 349 kB)
       .bss : 0xc0ec70e0 - 0xc0f14c70   ( 311 kB)
NR_IRQS:16 nr_irqs:16 16

  LSP version: linux-3.10.39-2014_T3.0p7

sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 171798ms
L310 cache controller enabled
l2x0: 16 ways, CACHE_ID 0x410054c9, AUX_CTRL 0x16070000, Cache size: 1048576 B
Console: colour dummy device 80x30
Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0xc063c590 - 0xc063c5e8
mvebu-pmsu: Initializing Power Management Service Unit
Initializing CPU Reset module
devtmpfs: initialized
mvebu-soc-id: MVEBU SoC ID=0x6810, Rev=0x4
xor: measuring software checksum speed
   arm4regs  :  2368.000 MB/sec
   8regs     :  1458.800 MB/sec
   32regs    :  1408.000 MB/sec
xor: using function: arm4regs (2368.000 MB/sec)
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
irq: Cannot allocate irq_descs @ IRQ194, assuming pre-allocated
irq: Cannot allocate irq_descs @ IRQ226, assuming pre-allocated
bio: create slab <bio-0> at 0
raid6: int32x1    203 MB/s
raid6: int32x2    270 MB/s
raid6: int32x4    283 MB/s
raid6: int32x8    323 MB/s
raid6: using algorithm int32x8 (323 MB/s)
raid6: using intx1 recovery algorithm
gpio-ms: gpio_dev = fe00000 (M: 254, m: 0)
[kernel] gpio_request for GPIO[24] failed with error number: -517
[kernel] gpio_request for GPIO[31] failed with error number: -517
[kernel] gpio_request for GPIO[44] failed with error number: -517
mvebu-pcie pcie-controller.3: PCIe0.0: link down
mvebu-pcie pcie-controller.3: PCIe1.0: link down
mvebu-pcie pcie-controller.3: PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io  0x1000-0xfffff]
pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe8000000]
pci_bus 0000:00: root bus resource [bus 00-ff]
pci 0000:00:01.0: [11ab:7846] type 01 class 0x060400
pci 0000:00:02.0: [11ab:7846] type 01 class 0x060400
PCI: bus0: Fast back to back transfers disabled
pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
PCI: bus1: Fast back to back transfers enabled
pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
PCI: bus2: Fast back to back transfers enabled
pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
pci 0000:00:01.0: PCI bridge to [bus 01]
pci 0000:00:02.0: PCI bridge to [bus 02]
PCI: enabling device 0000:00:01.0 (0140 -> 0143)
PCI: enabling device 0000:00:02.0 (0140 -> 0143)
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource armada_370_xp_clocksource
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 64 bytes, default 64
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
fuse init (API version 7.22)
bio: create slab <bio-1> at 1
Btrfs loaded
msgmni has been set to 984
async_tx: api initialized (async)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
armada-38x-pinctrl f1018000.pinctrl: registered pinctrl driver
****** turn off all LEDs that turned on in u-boot ******
****** blink SYS LED ******
mv_xor f1060800.xor: Marvell shared XOR driver
mv_xor f1060800.xor: Marvell XOR: ( xor cpy intr )
mv_xor f1060800.xor: freeing 1 in use descriptors!
mv_xor f1060800.xor: Marvell XOR: ( crc32c )
mv_xor f1060900.xor: Marvell shared XOR driver
mv_xor f1060900.xor: Marvell XOR: ( xor cpy intr )
mv_xor f1060900.xor: freeing 1 in use descriptors!
mv_xor f1060900.xor: Marvell XOR: ( crc32c )
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 44) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
ahci_mv f10a8000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl platform mode
ahci_mv f10a8000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs 
scsi0 : ahci_mv_platform
scsi1 : ahci_mv_platform
ata1: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x100 irq 58
ata2: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x180 irq 58
armada-nand f10d0000.nand: Initialize HAL based NFC in 8bit mode with DMA Disabled using BCH 4bit ECC
NAND device: Manufacturer ID: 0xc2, Chip ID: 0xda (Macronix NAND 256MiB 3,3V 8-bit), 256MiB, page size: 2048, OOB size: 64
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
nand_read_bbt: bad block at 0x000007640000
nand_read_bbt: bad block at 0x000007680000
7 ofpart partitions found on MTD device armada-nand
Creating 7 MTD partitions on "armada-nand":
0x000000000000-0x000000200000 : "U-Boot"
0x000000200000-0x000000400000 : "U-Boot env"
0x000000400000-0x000000e00000 : "Config"
0x000000e00000-0x000001d00000 : "Kernel-1"
0x000001d00000-0x000008700000 : "RootFS-1"
0x000008700000-0x000009600000 : "Kernel-2"
0x000009600000-0x000010000000 : "RootFS-2"
m25p80 spi0.0: unrecognized JEDEC id ffffff
SoC: model = 0x6810, revision = 0x4
  o 3 Giga ports supported
  o SKB recycle supported for SWF (Disabled)
  o NETA acceleration mode 1
  o RX Queue support: 8 Queues * 256 Descriptors
  o TX Queue support: 8 Queues * 532 Descriptors
  o GSO supported
  o GRO supported
  o Receive checksum offload supported
  o Transmit checksum offload supported
  o Driver ERROR statistics enabled
  o Driver INFO statistics enabled
  o Driver DEBUG statistics enabled

port #0: is_sgmii=0, is_rgmii=1, phy_addr=1
  o Loading network interface(s) for port #0: cpu_mask=0x1, tx_csum_limit=9800

  o Port 0 is connected to Linux netdevice
    o eth0, ifindex = 2, GbE port = 0
	giga p=0: mtu=1500, mac=00:50:43:02:02:01 (platform)

libphy: orion_mdio_bus: probed
e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
e1000: Copyright (c) 1999-2006 Intel Corporation.
e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd: block sizes: qh 64 qtd 96 itd 160 sitd 96
ehci-pci: EHCI PCI platform driver
ehci-orion: EHCI orion driver
Initializing Orion-SoC USB Host Controller
orion-ehci f1058000.usb: EHCI Host Controller
orion-ehci f1058000.usb: new USB bus registered, assigned bus number 1
orion-ehci f1058000.usb: reset hcs_params 0x10011 dbg=0 ind cc=0 pcc=0 ordered ports=1
orion-ehci f1058000.usb: reset hcc_params 0006 thresh 0 uframes 256/512/1024 park
orion-ehci f1058000.usb: park 0
orion-ehci f1058000.usb: reset command 0080b02  park=3 ithresh=8 period=1024 Reset HALT
orion-ehci f1058000.usb: irq 50, io mem 0xf1058000
orion-ehci f1058000.usb: init command 0010005 (park)=0 ithresh=1 period=512 RUN
orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00
usb usb1: default language 0x0409
usb usb1: udev 1, busnum 1, minor = 0
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 3.10.39 ehci_hcd
usb usb1: SerialNumber: f1058000.usb
usb usb1: usb_probe_device
usb usb1: configuration #1 chosen from 1 choice
usb usb1: adding 1-0:1.0 (config #1, interface 0)
hub 1-0:1.0: usb_probe_interface
hub 1-0:1.0: usb_probe_interface - got id
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
hub 1-0:1.0: standalone hub
hub 1-0:1.0: individual port power switching
hub 1-0:1.0: individual port over-current protection
hub 1-0:1.0: Single TT
hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)
hub 1-0:1.0: power on to power good time: 20ms
hub 1-0:1.0: local power source is good
hub 1-0:1.0: enabling power on all ports
xhci-hcd f10f0000.usb3: xHCI Host Controller
xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 2
xhci-hcd f10f0000.usb3: irq 48, io mem 0xf10f0000
usb usb2: default language 0x0409
usb usb2: udev 1, busnum 2, minor = 128
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: xHCI Host Controller
usb usb2: Manufacturer: Linux 3.10.39 xhci-hcd
usb usb2: SerialNumber: f10f0000.usb3
usb usb2: usb_probe_device
usb usb2: configuration #1 chosen from 1 choice
xHCI xhci_add_endpoint called for root hub
xHCI xhci_check_bandwidth called for root hub
usb usb2: adding 2-0:1.0 (config #1, interface 0)
hub 2-0:1.0: usb_probe_interface
hub 2-0:1.0: usb_probe_interface - got id
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
hub 2-0:1.0: standalone hub
hub 2-0:1.0: no power switching (usb 1.0)
hub 2-0:1.0: individual port over-current protection
hub 2-0:1.0: Single TT
hub 2-0:1.0: TT requires at most 8 FS bit times (666 ns)
hub 2-0:1.0: power on to power good time: 20ms
hub 2-0:1.0: local power source is good
hub 2-0:1.0: trying to enable port power on non-switchable hub
xhci-hcd f10f0000.usb3: xHCI Host Controller
xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 3
usb usb3: skipped 1 descriptor after endpoint
usb usb3: default language 0x0409
usb usb3: udev 1, busnum 3, minor = 256
usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: xHCI Host Controller
usb usb3: Manufacturer: Linux 3.10.39 xhci-hcd
usb usb3: SerialNumber: f10f0000.usb3
usb usb3: usb_probe_device
usb usb3: configuration #1 chosen from 1 choice
xHCI xhci_add_endpoint called for root hub
xHCI xhci_check_bandwidth called for root hub
usb usb3: adding 3-0:1.0 (config #1, interface 0)
hub 3-0:1.0: usb_probe_interface
hub 3-0:1.0: usb_probe_interface - got id
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 1 port detected
hub 3-0:1.0: standalone hub
hub 3-0:1.0: no power switching (usb 1.0)
hub 3-0:1.0: individual port over-current protection
hub 3-0:1.0: TT requires at most 8 FS bit times (666 ns)
hub 3-0:1.0: power on to power good time: 20ms
hub 3-0:1.0: local power source is good
hub 3-0:1.0: trying to enable port power on non-switchable hub
xhci-hcd f10f8000.usb3: xHCI Host Controller
xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 4
xhci-hcd f10f8000.usb3: irq 49, io mem 0xf10f8000
usb usb4: default language 0x0409
usb usb4: udev 1, busnum 4, minor = 384
usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: xHCI Host Controller
usb usb4: Manufacturer: Linux 3.10.39 xhci-hcd
usb usb4: SerialNumber: f10f8000.usb3
hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
usb usb4: usb_probe_device
usb usb4: configuration #1 chosen from 1 choice
xHCI xhci_add_endpoint called for root hub
xHCI xhci_check_bandwidth called for root hub
usb usb4: adding 4-0:1.0 (config #1, interface 0)
hub 4-0:1.0: usb_probe_interface
hub 4-0:1.0: usb_probe_interface - got id
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 1 port detected
hub 4-0:1.0: standalone hub
hub 4-0:1.0: no power switching (usb 1.0)
hub 4-0:1.0: individual port over-current protection
hub 4-0:1.0: Single TT
hub 4-0:1.0: TT requires at most 8 FS bit times (666 ns)
hub 4-0:1.0: power on to power good time: 20ms
hub 4-0:1.0: local power source is good
hub 4-0:1.0: trying to enable port power on non-switchable hub
xhci-hcd f10f8000.usb3: xHCI Host Controller
xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 5
usb usb5: skipped 1 descriptor after endpoint
usb usb5: default language 0x0409
usb usb5: udev 1, busnum 5, minor = 512
usb usb5: New USB device found, idVendor=1d6b, idProduct=0003
usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb5: Product: xHCI Host Controller
usb usb5: Manufacturer: Linux 3.10.39 xhci-hcd
usb usb5: SerialNumber: f10f8000.usb3
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0000
usb usb5: usb_probe_device
usb usb5: configuration #1 chosen from 1 choice
xHCI xhci_add_endpoint called for root hub
xHCI xhci_check_bandwidth called for root hub
usb usb5: adding 5-0:1.0 (config #1, interface 0)
hub 5-0:1.0: usb_probe_interface
hub 5-0:1.0: usb_probe_interface - got id
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 1 port detected
hub 5-0:1.0: standalone hub
hub 5-0:1.0: no power switching (usb 1.0)
hub 5-0:1.0: individual port over-current protection
hub 5-0:1.0: TT requires at most 8 FS bit times (666 ns)
hub 5-0:1.0: power on to power good time: 20ms
hub 5-0:1.0: local power source is good
hub 5-0:1.0: trying to enable port power on non-switchable hub
usbcore: registered new interface driver usblp
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
hub 3-0:1.0: state 7 ports 1 chg 0000 evt 0000
mvebu-rtc f10a3800.rtc: rtc core: registered f10a3800.rtc as rtc0
i2c /dev entries driver
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
hub 4-0:1.0: state 7 ports 1 chg 0000 evt 0000
device-mapper: ioctl: 4.24.0-ioctl (2013-01-15) initialised: dm-devel@redhat.com
dm_crypt using the OCF package.
cpuidle: using governor ladder
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
hub 5-0:1.0: state 7 ports 1 chg 0000 evt 0000
mmc0: SDHCI controller on f10d8000.sdhci [f10d8000.sdhci] using ADMA
sdhci-pltfm: SDHCI platform and OF driver helper
armada-cesa-ocf f109d000.crypto: mv_get_cesa_resources: Total CESA HW channels supported 2
armada-cesa-ocf f109d000.crypto: mv_get_cesa_resources: CESA feature: int_coalescing(1)
armada-cesa-ocf f109d000.crypto: mv_get_cesa_resources threshold 0x2, threshold_time 0xff
mvCesaInit: channels=2, session=640, queue=256
armada-cesa-ocf f109d000.crypto: cesa_ocf_probe: CESA driver operate in ocf(0) mode
ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
cesadev_init(c0836b3c)
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ata1.00: supports DRM functions and may not be fully accessible
ata1.00: ATA-9: WDC WD100EZAZ-11TDBA0, 83.H0A83, max UDMA/133
ata1.00: 19532873728 sectors, multi 0: LBA48 NCQ (depth 31/32)
TCP: cubic registered
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
ata1.00: supports DRM functions and may not be fully accessible
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      WDC WD100EZAZ-11 83.H PQ: 0 ANSI: 5
******** sd_probe: turn_off LED_HDD1 ********
******** sd_probe: turn_on LED_HDD1 WHITE********
UBI: attaching mtd4 to ubi0
sd 0:0:0:0: [sda] 19532873728 512-byte logical blocks: (10.0 TB/9.09 TiB)
sd 0:0:0:0: [sda] 4096-byte physical blocks
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
UBI: scanning is finished
UBI: attached mtd4 (name "RootFS-1", size 106 MiB) to ubi0
UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
UBI: good PEBs: 846, bad PEBs: 2, corrupted PEBs: 0
UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
UBI: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 3255924986
UBI: available PEBs: 0, total reserved PEBs: 846, PEBs reserved for bad PEB handling: 38
mvebu-rtc f10a3800.rtc: setting system clock to 2022-03-13 08:10:58 UTC (1647159058)
UBI: background thread "ubi_bgt0d" started, PID 1173
ata2: softreset failed (device not ready)
ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata2.00: supports DRM functions and may not be fully accessible
ata2.00: ATA-9: WDC WD101EDBZ-11B1DA0, 85.00A85, max UDMA/133
ata2.00: 19532873728 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata2.00: supports DRM functions and may not be fully accessible
ata2.00: configured for UDMA/133
scsi 1:0:0:0: Direct-Access     ATA      WDC WD101EDBZ-11 85.0 PQ: 0 ANSI: 5
******** sd_probe: turn_off LED_HDD2 ********
******** sd_probe: turn_on LED_HDD2 WHITE********
sd 1:0:0:0: [sdb] 19532873728 512-byte logical blocks: (10.0 TB/9.09 TiB)
sd 1:0:0:0: [sdb] 4096-byte physical blocks
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: sdb1 sdb2 sdb3
sd 1:0:0:0: [sdb] Attached SCSI disk
Freeing unused kernel memory: 6468K (c081d000 - c0e6e000)
eth0: mac address changed
bmPoolId = 0 has unknown buf_size
pool #0: pkt_size=1536, buf_size=1600 - 4096 of 4096 buffers added
egiga0: link up
egiga0: started
egiga0: link down
egiga0: link up, full duplex, speed 1 Gbps
egiga0: link down
egiga0: link up, full duplex, speed 1 Gbps
UBI: detaching mtd4 from ubi0
UBI: mtd4 is detached from ubi0
UBI: attaching mtd4 to ubi4
UBI: scanning is finished
UBI: attached mtd4 (name "RootFS-1", size 106 MiB) to ubi4
UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
UBI: good PEBs: 846, bad PEBs: 2, corrupted PEBs: 0
UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
UBI: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 3255924986
UBI: available PEBs: 0, total reserved PEBs: 846, PEBs reserved for bad PEB handling: 38
UBI: background thread "ubi_bgt4d" started, PID 1380
UBIFS: mounted UBI device 4, volume 0, name "ubi_rootfs1", R/O mode
UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS: FS size: 100691968 bytes (96 MiB, 793 LEBs), journal size 5079040 bytes (4 MiB, 40 LEBs)
UBIFS: reserved for root: 4755930 bytes (4644 KiB)
UBIFS: media format: w4/r0 (latest is w4/r0), UUID 0BFD27D2-6EE5-4B65-AA8F-18AC43453FD4, small LPT model
md: md0 stopped.
md: bind<sdb1>
md: bind<sda1>
md/raid1:md0: active with 2 out of 2 mirrors
md0: detected capacity change from 0 to 2045706240
md: md1 stopped.
md: bind<sdb2>
md: bind<sda2>
md/raid1:md1: active with 2 out of 2 mirrors
md1: detected capacity change from 0 to 2046754816
 md1: unknown partition table
Adding 1998780k swap on /dev/md1.  Priority:-1 extents:1 across:1998780k 
 md0: unknown partition table
EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (md0): re-mounted. Opts: (null)
EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem
EXT4-fs (loop0): mounted filesystem without journal. Opts: (null)
UBI: attaching mtd2 to ubi2
UBI: scanning is finished
UBI: attached mtd2 (name "Config", size 10 MiB) to ubi2
UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
UBI: good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
UBI: max/mean erase counter: 499/288, WL threshold: 4096, image sequence number: 23823181
UBI: available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 40
UBI: background thread "ubi_bgt2d" started, PID 1566
UBIFS: background thread "ubifs_bgt2_0" started, PID 1570
UBIFS: mounted UBI device 2, volume 0, name "ubi_config"
UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS: FS size: 3301376 bytes (3 MiB, 26 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
UBIFS: reserved for root: 155931 bytes (152 KiB)
UBIFS: media format: w4/r0 (latest is w4/r0), UUID 77371F71-46A3-4D59-9BDD-8521FF571312, small LPT model
NTFS driver 2.1.30 [Flags: R/O MODULE].
tntfs: module license 'Commercial. For support email ntfs-support@tuxera.com.' taints kernel.
Disabling lock debugging due to kernel taint
Tuxera NTFS driver 3015.1.29 [Flags: R/W MODULE].
PPP generic driver version 2.4.2
PPP MPPE Compression module registered
PPP Deflate Compression module registered
NET: Registered protocol family 24
PPP BSD Compression module registered
md: md2 stopped.
md: bind<sda3>
md/raid1:md2: active with 1 out of 1 mirrors
md2: detected capacity change from 0 to 9996600147968
md: md3 stopped.
md: bind<sdb3>
md/raid1:md3: active with 1 out of 1 mirrors
md3: detected capacity change from 0 to 9996600147968
 md2: unknown partition table
 md3: unknown partition table
EXT4-fs (md2): warning: mounting fs with errors, running e2fsck is recommended
EXT4-fs (md2): mounted filesystem with ordered data mode. Opts: usrquota,data=ordered,barrier=1
EXT4-fs (md3): warning: mounting fs with errors, running e2fsck is recommended
EXT4-fs (md3): mounted filesystem with ordered data mode. Opts: usrquota,data=ordered,barrier=1
NFSD: the nfsdcld client tracking upcall will be removed in 3.10. Please transition to using nfsdcltrack.
NFSD: starting 90-second grace period (net c0ebf8b0)
Rounding down aligned max_sectors from 4294967295 to 4294967288
NFSD: Unable to end grace period: -110
EXT4-fs (md2): error count: 38
EXT4-fs (md2): initial error at 1636743721: ext4_mb_generate_buddy:755
EXT4-fs (md2): last error at 1636839024: ext4_mb_generate_buddy:755
EXT4-fs (md3): error count: 3
EXT4-fs (md3): initial error at 1636897141: ext4_mb_generate_buddy:755
EXT4-fs (md3): last error at 1636897143: ext4_mb_generate_buddy:755

Mijzelf
Beiträge: 133
Registriert: Mi 14. Nov 2018, 19:50

Re: Shutdown deamon not working on NAS326

Beitrag von Mijzelf »

Supernils hat geschrieben:
So 13. Mär 2022, 10:55
dmesg.log
That is after a clean boot? The log contains no disk activity like

Code: Alles auswählen

[  993.140024] 
[  993.140026] ****** disk(2:0:0:0) spin down at 69311 ******
[ 1984.041334] 
[ 1984.041337] ****** disk(3:0:0:0) spin down at 168402 ******
[ 2162.093220] 
[ 2162.093223] ****** disk(3:0:0:0 0)(HD4) awaked by sshd (cmd: 28) ******
(And for some reason ZyXEL decided not to enable timestamps in 326 kernel log).

Antworten