Also das hat mir der Support geantwortet, finde das auch nicht gerade professionell:
ZitatAlles anzeigen
Dear Customer,
thank you for contacting QNAP technical support Germany.
This is a known bug. Set this ticket to "need follow up" until the bug fix released.
Habe auch das gleiche Problem auf meiner 469L _hurted:
Hallo liebe QNAP-Clubber,
seit dem Update auf die Firmware 4.2 habe ich leider auf meinem TS-469L mit 4x2TB (WD20EZRX) im Raid10 das Problem eines unsauberen Filesystems. Diese Meldung tritt leider trotz abgeschlossenem File-System-Check nach jedem Reboot erneut auf. Zusätzlich muss mit jedem Boot das Raid10 neu synchronisiert werden.
Nun meine Frage; wie finde ich heraus, ob es sich hierbei um ein Software-Problem handelt (irgendetwas verhindert beim Herunterfahren das ordnungsgemäße aushängen der Platten) oder ob eine/mehrere HDDs defekt sind? Da fdisk -lu auf defekte Partitionstabellen deutet, gehe ich mal von einem Hardwaredefekt aus?
[~] # dmesgersion 140[ 28.330048] kjournald starting. Commit interval 5 seconds[ 28.330261] EXT3-fs (sda1): using internal journal[ 28.330267] EXT3-fs (sda1): mounted filesystem with ordered data mode[ 28.409035] kjournald starting. Commit interval 5 seconds[ 28.409219] EXT3-fs (sda1): using internal journal[ 28.409224] EXT3-fs (sda1): mounted filesystem with writeback data mode[ 28.573121] kjournald starting. Commit interval 5 seconds[ 28.573312] EXT3-fs (sdb1): using internal journal[ 28.573319] EXT3-fs (sdb1): mounted filesystem with writeback data mode[ 28.733476] kjournald starting. Commit interval 5 seconds[ 28.733670] EXT3-fs (sdc1): using internal journal[ 28.733676] EXT3-fs (sdc1): mounted filesystem with writeback data mode[ 28.888294] kjournald starting. Commit interval 5 seconds[ 28.888491] EXT3-fs (sdd1): using internal journal[ 28.888496] EXT3-fs (sdd1): mounted filesystem with writeback data mode[ 29.044842] md: md9 stopped.[ 29.047156] md: bind<sdb1>[ 29.047379] md: bind<sdc1>[ 29.047595] md: bind<sdd1>[ 29.047811] md: bind<sda1>[ 29.048929] bio: create slab <bio-1> at 1[ 29.049059] md/raid1:md9: active with 4 out of 4 mirrors[ 29.049187] created bitmap (65 pages) for device md9[ 29.052877] md9: bitmap initialized from disk: read 5/5 pages, set 1 of 132512 bits[ 29.063594] md9: detected capacity change from 0 to 542769152[ 30.079201] md9: unknown partition table[ 30.183043] kjournald starting. Commit interval 5 seconds[ 30.199584] EXT3-fs (md9): using internal journal[ 30.199591] EXT3-fs (md9): mounted filesystem with ordered data mode[ 30.452544] md: md13 stopped.[ 30.531659] md: bind<sdb4>[ 30.531873] md: bind<sdc4>[ 30.532067] md: bind<sdd4>[ 30.532295] md: bind<sda4>[ 30.533482] md/raid1:md13: active with 4 out of 4 mirrors[ 30.533600] created bitmap (57 pages) for device md13[ 30.536764] md13: bitmap initialized from disk: read 4/4 pages, set 0 of 114720 bits[ 30.562644] md13: detected capacity change from 0 to 469893120[ 37.348061] md: bind<sda2>[ 37.359801] md: bind<sdb2>[ 37.371666] md: bind<sdc2>[ 37.379047] md: bind<sdd2>[ 37.380228] md/raid1:md256: not clean -- starting background reconstruction[ 37.380234] md/raid1:md256: active with 2 out of 2 mirrors[ 37.380334] created bitmap (1 pages) for device md256[ 37.380441] md256: bitmap initialized from disk: read 1/1 pages, set 9 of 9 bits[ 37.403668] md256: detected capacity change from 0 to 542834688[ 37.403948] RAID1 conf printout:[ 37.403956] --- wd:2 rd:2[ 37.403963] disk 0, wo:0, o:1, dev:sda2[ 37.403969] disk 1, wo:0, o:1, dev:sdb2[ 37.403974] RAID1 conf printout:[ 37.403978] --- wd:2 rd:2[ 37.403983] disk 0, wo:0, o:1, dev:sda2[ 37.403988] disk 1, wo:0, o:1, dev:sdb2[ 37.404086] md: resync of RAID array md256[ 37.404091] md: minimum _guaranteed_ speed: 5000 KB/sec/disk.[ 37.404095] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync.[ 37.404099] md: Resyncing started: md256[ 37.404137] md: using 128k window, over a total of 530112k.[ 37.444789] md256: unknown partition table[ 37.530601] Adding 530108k swap on /dev/md256. Priority:-1 extents:1 across:530108k [ 37.656070] md13: unknown partition table[ 40.276693] md: md0 stopped.[ 40.283592] md: bind<sdb3>[ 40.283789] md: bind<sdc3>[ 40.283983] md: bind<sdd3>[ 40.284173] md: bind<sda3>[ 40.285351] md/raid10:md0: not clean -- starting background reconstruction[ 40.285357] md/raid10:md0: active with 4 out of 4 devices[ 40.285398] md0: detected capacity change from 0 to 3997584588800[ 40.285508] md: delaying resync of md0 until md256 has finished (they share one or more physical units)[ 40.289473] md0: unknown partition table[ 41.881190] EXT4-fs (md0): Mount option "noacl" will be removed by 3.5[ 41.881194] Contact linux-ext4@vger.kernel.org if you think we should keep it.[ 41.881197] [ 43.584268] ext4_init_reserve_inode_table0: md0, 29785[ 43.584275] ext4_init_reserve_inode_table2: md0, 29785, 0, 0, 4096[ 43.584307] EXT4-fs (md0): recovery complete[ 43.617449] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: usrjquota=aquota.user,jqfmt=vfsv0,user_xattr,data=ordered,delalloc,noacl[ 71.812433] kjournald starting. Commit interval 5 seconds[ 71.932368] EXT3-fs (md13): using internal journal[ 71.932376] EXT3-fs (md13): mounted filesystem with ordered data mode[ 91.308411] cryptodev: driver 0.9 loaded.[ 91.331081] Register ICH/PCH RTC driver.[ 91.333232] iTCO_vendor_support: vendor-support=0[ 91.335336] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07[ 91.335548] iTCO_wdt: Found a ICH10R TCO device (Version=2, TCOBASE=0x0460)[ 91.335701] iTCO_wdt: initialized. heartbeat=120 sec (nowayout=0)[ 91.414410] fnotify: Load file notify kernel module.[ 92.473917] snd_hda_intel 0000:00:1b.0: irq 55 for MSI/MSI-X[ 92.490141] usbcore: registered new interface driver snd-usb-audio[ 92.493363] usbcore: registered new interface driver snd-usb-caiaq[ 92.499147] Linux video capture interface: v2.00[ 92.514376] usbcore: registered new interface driver uvcvideo[ 92.514383] USB Video Class driver (1.1.1)[ 92.579342] 8021q: 802.1Q VLAN Support v1.8[ 96.324997] md: md256: resync done.[ 96.325003] md: Resyncing done: md256[ 96.344871] md: resync of RAID array md0[ 96.344877] md: minimum _guaranteed_ speed: 5000 KB/sec/disk.[ 96.344882] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync.[ 96.344886] md: Resyncing started: md0[ 96.344903] md: using 128k window, over a total of 3903891200k.[ 96.481137] RAID1 conf printout:[ 96.481144] --- wd:2 rd:2[ 96.481150] disk 0, wo:0, o:1, dev:sda2[ 96.481154] disk 1, wo:0, o:1, dev:sdb2[ 96.636643] RAID1 conf printout:[ 96.636650] --- wd:2 rd:2[ 96.636657] disk 0, wo:0, o:1, dev:sda2[ 96.636661] disk 1, wo:0, o:1, dev:sdb2[ 96.636665] RAID1 conf printout:[ 96.636668] --- wd:2 rd:2[ 96.636671] disk 0, wo:0, o:1, dev:sda2[ 96.636675] disk 1, wo:0, o:1, dev:sdb2[ 122.167533] 8021q: adding VLAN 0 to HW filter on device eth0[ 122.248511] 8021q: adding VLAN 0 to HW filter on device eth1[ 124.357203] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx[ 124.607327] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx[ 125.245212] IPv6: Loaded, but administratively disabled, reboot required to enable[ 125.270779] Bridge firewalling registered[ 125.349416] bonding: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)[ 125.349428] bonding: MII link monitoring set to 100 ms[ 160.019423] Bluetooth: Core ver 2.16[ 160.019544] NET: Registered protocol family 31[ 160.019550] Bluetooth: HCI device and connection manager initialized[ 160.019557] Bluetooth: HCI socket layer initialized[ 160.019561] Bluetooth: L2CAP socket layer initialized[ 160.019574] Bluetooth: SCO socket layer initialized[ 160.024967] usbcore: registered new interface driver btusb[ 180.169414] rule type=2, num=2[ 180.268849] Loading iSCSI transport class v2.0-871.[ 180.282535] iscsi: registered transport (tcp)[ 187.059623] Set msys_nodify as 6300[ 187.470072] tun: Universal TUN/TAP device driver, 1.6[ 187.470079] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>[ 188.531426] nf_conntrack version 0.5.0 (7881 buckets, 31524 max)[ 188.610041] ip_tables: (C) 2000-2006 Netfilter Core Team[ 219.988649] usbcore: registered new interface driver cp210x[ 219.988693] USB Serial support registered for cp210x[~] #[~] # fdisk -luDisk /dev/sda: 2000.3 GB, 2000398934016 bytes255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectorsUnits = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id System/dev/sda1 40 1060289 530125 83 Linux/dev/sda2 1060296 2120579 530142 83 Linux/dev/sda3 2120584 3906011969 1951945693 83 Linux/dev/sda4 3906011976 3907007999 498012 83 LinuxDisk /dev/sdb: 2000.3 GB, 2000398934016 bytes255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectorsUnits = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id System/dev/sdb1 40 1060289 530125 83 Linux/dev/sdb2 1060296 2120579 530142 83 Linux/dev/sdb3 2120584 3906011969 1951945693 83 Linux/dev/sdb4 3906011976 3907007999 498012 83 LinuxDisk /dev/sdc: 2000.3 GB, 2000398934016 bytes255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectorsUnits = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id System/dev/sdc1 40 1060289 530125 83 Linux/dev/sdc2 1060296 2120579 530142 83 Linux/dev/sdc3 2120584 3906011969 1951945693 83 Linux/dev/sdc4 3906011976 3907007999 498012 83 LinuxDisk /dev/sdd: 2000.3 GB, 2000398934016 bytes255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectorsUnits = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id System/dev/sdd1 40 1060289 530125 83 Linux/dev/sdd2 1060296 2120579 530142 83 Linux/dev/sdd3 2120584 3906011969 1951945693 83 Linux/dev/sdd4 3906011976 3907007999 498012 83 LinuxDisk /dev/sde: 515 MB, 515899392 bytes8 heads, 32 sectors/track, 3936 cylinders, total 1007616 sectorsUnits = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id System/dev/sde1 32 4351 2160 83 Linux/dev/sde2 * 4352 488959 242304 83 Linux/dev/sde3 488960 973567 242304 83 Linux/dev/sde4 973568 1007615 17024 5 Extended/dev/sde5 973600 990207 8304 83 Linux/dev/sde6 990240 1007615 8688 83 LinuxDisk /dev/md9: 542 MB, 542769152 bytes2 heads, 4 sectors/track, 132512 cylinders, total 1060096 sectorsUnits = sectors of 1 * 512 = 512 bytesDisk /dev/md9 doesn't contain a valid partition tableDisk /dev/md13: 469 MB, 469893120 bytes2 heads, 4 sectors/track, 114720 cylinders, total 917760 sectorsUnits = sectors of 1 * 512 = 512 bytesDisk /dev/md13 doesn't contain a valid partition tableDisk /dev/md256: 542 MB, 542834688 bytes2 heads, 4 sectors/track, 132528 cylinders, total 1060224 sectorsUnits = sectors of 1 * 512 = 512 bytesDisk /dev/md256 doesn't contain a valid partition tableDisk /dev/md0: 3997.5 GB, 3997584588800 bytes2 heads, 4 sectors/track, 975972800 cylinders, total 7807782400 sectorsUnits = sectors of 1 * 512 = 512 bytesDisk /dev/md0 doesn't contain a valid partition table[~] #[~] # mdadm --detail /dev/md0
/dev/md0:
Version : 0.90
Creation Time : Sat Jun 15 01:16:35 2013
Raid Level : raid10
Array Size : 3903891200 (3723.04 GiB 3997.58 GB)
Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Tue Oct 27 17:12:36 2015
State : active, resyncing
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : near=2
Chunk Size : 64K
Resync Status : 3% complete
UUID : 3b925d03:e60d2ea5:33a6b0bb:465ac504
Events : 0.78
Number Major Minor RaidDevice State
0 8 3 0 active sync set-A /dev/sda3
1 8 19 1 active sync set-B /dev/sdb3
2 8 35 2 active sync set-A /dev/sdc3
3 8 51 3 active sync set-B /dev/sdd3
[~] # mdadm --detail /dev/md9
/dev/md9:
Version : 0.90
Creation Time : Sat Jun 15 01:14:15 2013
Raid Level : raid1
Array Size : 530048 (517.71 MiB 542.77 MB)
Used Dev Size : 530048 (517.71 MiB 542.77 MB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 9
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Tue Oct 27 17:40:17 2015
State : active
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
UUID : 6af5216b:a05783b4:92eec8cd:baf14266
Events : 0.167
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
2 8 33 2 active sync /dev/sdc1
3 8 49 3 active sync /dev/sdd1
[~] # mdadm --detail /dev/md13
/dev/md13:
Version : 0.90
Creation Time : Sat Jun 15 01:14:24 2013
Raid Level : raid1
Array Size : 458880 (448.20 MiB 469.89 MB)
Used Dev Size : 458880 (448.20 MiB 469.89 MB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 13
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Tue Oct 27 17:25:06 2015
State : active
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
UUID : 8a4bef71:ad1a06b6:e03b3a05:55b5119a
Events : 0.585
Number Major Minor RaidDevice State
0 8 4 0 active sync /dev/sda4
1 8 20 1 active sync /dev/sdb4
2 8 36 2 active sync /dev/sdc4
3 8 52 3 active sync /dev/sdd4
[~] # mdadm --detail /dev/md256
/dev/md256:
Version : 1.0
Creation Time : Tue Oct 27 17:12:33 2015
Raid Level : raid1
Array Size : 530112 (517.77 MiB 542.83 MB)
Used Dev Size : 530112 (517.77 MiB 542.83 MB)
Raid Devices : 2
Total Devices : 4
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Tue Oct 27 17:42:27 2015
State : active
Active Devices : 2
Working Devices : 4
Failed Devices : 0
Spare Devices : 2
Name : 256
UUID : cb7dcd97:0e162a35:d3c49a22:54eb8e2a
Events : 22
Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 8 18 1 active sync /dev/sdb2
2 8 34 - spare /dev/sdc2
3 8 50 - spare /dev/sdd2
[~] #EDIT: Mhh, scheint wohl einige mit einem ähnlichen Problem zu geben; http://forum.qnapclub.de/viewt…&t=36744&p=210071#p210071
Wie würdet ihr nun weiter vorgehen, um das Problem näher zu identifizieren? Backup der (wichtigsten) Daten ist vorhanden.
Herzlichen Dank,
freddeh
Hallo erstmal,
Ich als absoluter Linux-Anfänger habe mich mal dran gemacht und wollte FHEM auf meinem
QNAP TS-469L mit Firmware Version 4.0.2 (2013/07/26)
und Linux version 3.4.6 (root@NasX86-12) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2))
installieren, das läuft jetzt auch soweit, findet aber logischerweise das CULv3 unter /dev/usb/ttyUSB0 nicht. dmesg sagt beim anschließen nur:
[ 7524.816227] usb 3-1: new full-speed USB device number 3 using uhci_hcdusbserial.ko und ftdi_sio.ko sind unter /lib/modules/others/ vorhanden, aber usbserial.ko lässt die Parameter vendor und product beim Laden nicht zu (unknown Parameter). Die pl2023.ko fehlt komplett, in einigen Foren wurde das Modul aber auch weggelassen, wird das für das CUL benötigt?
lsusb sagt:
Bus 003 Device 002: ID 03eb:204b Atmel Corp. LUFA USB to Serial Adapter ProjectIn einigen Foren wird geraten, den Kernel mit "CONFIG_USB_SERIAL_GENERIC=y" neu zu compilen und es nochmal zu versuchen, nur wie genau mache ich das?
Hat jemand vielleicht einen Tipp, wie man das Problem lösen könnte?
LG freddeh
dito.. +1