Ist es ein *piep*, mehrfaches *piepen* oder eher ein *beepbeep* bzw. ein einfacher *beep* ?
Das hört sich ganz schön Scheibenkleister an... War auch nur ein Spässchen 
Also ich hatte so etwas auch mal beobachtet. Hatte mal einen User, bei dem sich die Konfigurations-Partitionen (gelegentlich neu gesynct haben). Dann "piept's" nämlich auch...
Kannst Du mal via ssh auf das NAS und ein:
dmesg
eingeben?
Eventuell steht da was über einen Resync.
Grüsse, David
Ist nur ein kurzer "beep" ... hatte lang an meinem PC gesucht bis ich ihn kürzlich aus hatte und es trotzdem beepte
Der DMESG sieht ganz gut aus ... denke ich.
[/var/log] # dmesg
irq 18, io base 0x0000a000
hub 8-0:1.0: USB hub found
hub 8-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb: create proc systemp successfully
usb: create proc systemp successfully
usb 2-1: new high speed USB device using ehci_hcd and address 2
Using EHCI controller.
scsi12 : usb-storage 2-1:1.0
scsi 12:0:0:0: Direct-Access USB DISK MODULE PMAP PQ: 0 ANSI: 0 CCS
sd 12:0:0:0: Attached scsi generic sg23 type 0
sd 12:0:0:0: [sdx] 1007616 512-byte logical blocks: (515 MB/492 MiB)
sd 12:0:0:0: [sdx] Write Protect is off
sd 12:0:0:0: [sdx] Mode Sense: 23 00 00 00
sd 12:0:0:0: [sdx] Assuming drive cache: write through
sd 12:0:0:0: [sdx] Assuming drive cache: write through
sdx: sdx1 sdx2 sdx3 sdx4 < sdx5 sdx6 >
sd 12:0:0:0: [sdx] Assuming drive cache: write through
sd 12:0:0:0: [sdx] Attached SCSI removable disk
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda1): mounted filesystem with writeback data mode
kjournald starting. Commit interval 5 seconds
EXT3-fs (sdb1): mounted filesystem with writeback data mode
kjournald starting. Commit interval 5 seconds
EXT3-fs (sdc1): mounted filesystem with writeback data mode
kjournald starting. Commit interval 5 seconds
EXT3-fs (sdd1): mounted filesystem with writeback data mode
kjournald starting. Commit interval 5 seconds
EXT3-fs (sde1): mounted filesystem with writeback data mode
kjournald starting. Commit interval 5 seconds
EXT3-fs (sdf1): mounted filesystem with writeback data mode
kjournald starting. Commit interval 5 seconds
EXT3-fs (sdg1): mounted filesystem with writeback data mode
kjournald starting. Commit interval 5 seconds
EXT3-fs (sdh1): mounted filesystem with writeback data mode
md: md9 stopped.
md: bind<sdb1>
md: bind<sdc1>
md: bind<sdd1>
md: bind<sde1>
md: bind<sdf1>
md: bind<sdg1>
md: bind<sdh1>
md: bind<sda1>
raid1: raid set md9 active with 8 out of 8 mirrors
md9: bitmap initialized from disk: read 5/5 pages, set 0 bits
created bitmap (65 pages) for device md9
md9: detected capacity change from 0 to 542769152
md9: unknown partition table
kjournald starting. Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
md: md13 stopped.
md: bind<sdb4>
md: bind<sdc4>
md: bind<sdd4>
md: bind<sde4>
md: bind<sdf4>
md: bind<sdg4>
md: bind<sdh4>
md: bind<sda4>
raid1: raid set md13 active with 8 out of 8 mirrors
md13: bitmap initialized from disk: read 4/4 pages, set 0 bits
created bitmap (57 pages) for device md13
md13: detected capacity change from 0 to 469893120
md13: unknown partition table
kjournald starting. Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
kjournald starting. Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
kjournald starting. Commit interval 5 seconds
EXT3-fs (md13): using internal journal
EXT3-fs (md13): mounted filesystem with writeback data mode
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ICH7/ICH9R rtc control driver.
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
iTCO_wdt: Found a ICH9R TCO device (Version=2, TCOBASE=0x0860)
iTCO_wdt: initialized. heartbeat=120 sec (nowayout=0)
usbcore: registered new interface driver usblp
ufsd: module license 'Commercial product' taints kernel.
Disabling lock debugging due to kernel taint
ufsd: driver U82 (Oct 19 2010 06:23:30) with acl LBD=OFF with ioctl loaded at f83c6000
NTFS read/write support included
Hfs+/HfsX read/write support included
kjournald starting. Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
md: bind<sda2>
raid1: raid set md8 active with 1 out of 1 mirrors
md8: detected capacity change from 0 to 542769152
md8: unknown partition table
Adding 530040k swap on /dev/md8. Priority:-1 extents:1 across:530040k
md: bind<sdb2>
RAID1 conf printout:
--- wd:1 rd:2
disk 0, wo:0, o:1, dev:sda2
disk 1, wo:1, o:1, dev:sdb2
md: recovery of RAID array md8
md: minimum _guaranteed_ speed: 5000 KB/sec/disk.
md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
md: using 128k window, over a total of 530048 blocks.
md: bind<sdc2>
md: bind<sdd2>
md: bind<sde2>
md: bind<sdf2>
md: bind<sdg2>
md: md8: recovery done.
RAID1 conf printout:
--- wd:2 rd:2
disk 0, wo:0, o:1, dev:sda2
disk 1, wo:0, o:1, dev:sdb2
md: bind<sdh2>
active port 0 :139
active port 1 :445
active port 2 :20
md: md0 still in use.
md: bind<sdb3>
md: bind<sdc3>
md: bind<sdd3>
md: bind<sde3>
md: bind<sdf3>
md: bind<sdg3>
md: bind<sdh3>
md: bind<sda3>
raid5: device sda3 operational as raid disk 0
raid5: device sdh3 operational as raid disk 7
raid5: device sdg3 operational as raid disk 6
raid5: device sdf3 operational as raid disk 5
raid5: device sde3 operational as raid disk 4
raid5: device sdd3 operational as raid disk 3
raid5: device sdc3 operational as raid disk 2
raid5: device sdb3 operational as raid disk 1
raid5: allocated 134304kB for md0
0: w=1 pa=0 pr=8 m=2 a=2 r=8 op1=0 op2=0
7: w=2 pa=0 pr=8 m=2 a=2 r=8 op1=0 op2=0
6: w=3 pa=0 pr=8 m=2 a=2 r=8 op1=0 op2=0
5: w=4 pa=0 pr=8 m=2 a=2 r=8 op1=0 op2=0
4: w=5 pa=0 pr=8 m=2 a=2 r=8 op1=0 op2=0
3: w=6 pa=0 pr=8 m=2 a=2 r=8 op1=0 op2=0
2: w=7 pa=0 pr=8 m=2 a=2 r=8 op1=0 op2=0
1: w=8 pa=0 pr=8 m=2 a=2 r=8 op1=0 op2=0
raid5: raid level 6 set md0 active with 8 out of 8 devices, algorithm 2
RAID5 conf printout:
--- rd:8 wd:8
disk 0, o:1, dev:sda3
disk 1, o:1, dev:sdb3
disk 2, o:1, dev:sdc3
disk 3, o:1, dev:sdd3
disk 4, o:1, dev:sde3
disk 5, o:1, dev:sdf3
disk 6, o:1, dev:sdg3
disk 7, o:1, dev:sdh3
md0: bitmap initialized from disk: read 11/11 pages, set 15 bits
created bitmap (175 pages) for device md0
md0: detected capacity change from 0 to 8992171622400
md0: unknown partition table
EXT4-fs (md0): mounted filesystem with ordered data mode
bonding: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
bonding: MII link monitoring set to 100 ms
bonding: bond0: enslaving eth0 as a backup interface with a down link.
bonding: bond0: enslaving eth1 as a backup interface with a down link.
e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
bonding: bond0: link status definitely up for interface eth1.
bonding: bond0: making interface eth1 the new active one.
bonding: bond0: first active interface up!
bonding: bond0: link status definitely down for interface eth1, disabling it
bonding: bond0: now running without any active interface !
e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
bonding: bond0: link status definitely up for interface eth1.
bonding: bond0: making interface eth1 the new active one.
bonding: bond0: first active interface up!
active port 0 :139
active port 1 :445
active port 2 :20
warning: `proftpd' uses 32-bit capabilities (legacy support in use)
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: starting 90-second grace period
Set Adpater:port=0:0 standby to 241 (1800 secs).
Set Adpater:port=0:1 standby to 241 (1800 secs).
Set Adpater:port=0:2 standby to 241 (1800 secs).
Set Adpater:port=0:3 standby to 241 (1800 secs).
rule type=2, num=0
Loading iSCSI transport class v2.0-871.
iscsi: registered transport (tcp)Bis auf dem md8 (der hat sich 1x gesynct) iss aber nix schlimmes. Sieht's echt normal aus.
Hm. Siehst Du was mit:
cat /proc/mdstat
heraus?
Ich glaube aber nicht dass da was ist. :?
Das wäre zumindest ein guter Ansatz.
Wäre auch eine Idee,
alternativ mal an den QNAP Support wenden. Da kannst Du auch ruhig auf deutsch schreiben.
Grüsse, David
Hallo,
ist hier eines der Signaltöne aufgeführt ?
http://docs.qnap.com/nas/ger/i…l?check_system_status.htm
Christian
Also wenn nichts auf der Liste bzw aus dem Handbuch überein stimmt und auch nichts im Log steht, dann ist der Support die richtige Wahl!
Vielleicht kannst du uns dann Feedback geben?!
Christian