Hallo, hast du dein Problem lösen können ??? Ich habe das gleiche mit der 3. Festplatte, die LED leuchtet immer noch rot, obwohl ich eine neue gekauft und eingebaut habe....
Beiträge von marcuso
-
-
Hallo, also ich habe ein ähnliches Problem (sorry dass ich keine Lösung vorschlagen kann), seit ein paar Tagen leutest bei meinem QNAP-TS439 die LED der 3. Platte rot (r/w error), alle SMART checks enden mit einem GOOD (alle HDDs). Habe die HDD dann hotswappmässig rausgenommen und die Partitionen gelöscht, danach die HDD wieder rein und de rQNAP begann diese neu zu formatieren und initialisieren (wie es auch sein sollte). das dauerte viele Stunden, der LOG zeigt alles OK an, nur die LED leuchtet immer noch rot, auch nach einem booten. Ich vermute, dass der Controller sie immer noch als defekt ansieht. Hier der LOG::
Code17903,"Information","2010-12-21","02:04:53","System","127.0.0.1","localhost","[RAID5 Disk Volume: Drive 1 2 3 4] Rebuilding completed."17867,"Information","2010-12-20","16:01:20","System","127.0.0.1","localhost","[RAID5 Disk Volume: Drive 1 2 3 4] Start rebuilding."17866,"Information","2010-12-20","16:00:51","System","127.0.0.1","localhost","[RAID5 Disk Volume: Drive 1 2 3 4] Drive 3 added into volume 1."17865,"Information","2010-12-20","16:00:18","System","127.0.0.1","localhost","Drive 3 plugged in."17786,"Error","2010-12-20","10:34:19","System","127.0.0.1","localhost","Drive 3 plugged out."
Also ist jetzt die HDD defekt, trotz dem positiven SMART check ???
cheers
EDIT:
Hier noch der check mit der HDD drin (slot3):Code
Alles anzeigenHDD in [~] # dmesg r ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1 ehci_hcd 0000:00:1d.7: using broken periodic workaround ehci_hcd 0000:00:1d.7: debug port 1 ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfe83bc00 ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00 hub 1-0:1.0: USB hub found hub 1-0:1.0: 8 ports detected uhci_hcd: USB Universal Host Controller Interface driver uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23 uhci_hcd 0000:00:1d.0: setting latency timer to 64 uhci_hcd 0000:00:1d.0: UHCI Host Controller uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000bc00 hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 uhci_hcd 0000:00:1d.1: setting latency timer to 64 uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3 uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000b880 hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 uhci_hcd 0000:00:1d.2: setting latency timer to 64 uhci_hcd 0000:00:1d.2: UHCI Host Controller uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4 uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000b800 hub 4-0:1.0: USB hub found hub 4-0:1.0: 2 ports detected uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) -> IRQ 16 uhci_hcd 0000:00:1d.3: setting latency timer to 64 uhci_hcd 0000:00:1d.3: UHCI Host Controller uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5 uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000b480 hub 5-0:1.0: USB hub found hub 5-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-2: new low speed USB device using uhci_hcd and address 2 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 md: md9 stopped. md: bind<sdb1> md: bind<sdc1> md: bind<sdd1> md: bind<sda1> raid1: raid set md9 active with 4 out of 4 mirrors md9: bitmap initialized from disk: read 5/5 pages, set 75 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<sda4> raid1: raid set md13 active with 4 out of 4 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 input: USB Keyboard as /class/input/input2 generic-usb 0003:04D9:1603.0001: input: USB HID v1.10 Keyboard [ USB Keyboard] on usb-0000:00:1d.0-2/input0 input: USB Keyboard as /class/input/input3 generic-usb 0003:04D9:1603.0002: input: USB HID v1.10 Device [ USB Keyboard] on usb-0000:00:1d.0-2/input1 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 ICH7-M or ICH7-U 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 (Nov 10 2010 04:30:43) with acl LBD=OFF with ioctl loaded at f83d2000 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 md: bind<sda2> raid1: raid set md4 active with 1 out of 1 mirrors md4: detected capacity change from 0 to 542769152 md4: unknown partition table Adding 530040k swap on /dev/md4. 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 md4 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> active port 0 :139 active port 1 :445 active port 2 :20 md: md4: 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: md0 still in use. md: bind<sdb3> md: bind<sdc3> md: bind<sdd3> md: bind<sda3> raid5: device sda3 operational as raid disk 0 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 67552kB for md0 0: w=1 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0 3: w=2 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0 2: w=3 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0 1: w=4 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0 raid5: raid level 5 set md0 active with 4 out of 4 devices, algorithm 2 RAID5 conf printout: --- rd:4 wd:4 disk 0, o:1, dev:sda3 disk 1, o:1, dev:sdb3 disk 2, o:1, dev:sdc3 disk 3, o:1, dev:sdd3 md0: detected capacity change from 0 to 5996376883200 md0: unknown partition table EXT4-fs (md0): mounted filesystem with ordered data mode e1000e: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None 0000:02:00.0: eth1: 10/100 speed: disabling TSO e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None 0000:01:00.0: eth0: 10/100 speed: disabling TSO e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None 0000:01:00.0: eth0: 10/100 speed: disabling TSO e1000e: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None 0000:02:00.0: eth1: 10/100 speed: disabling TSO 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=1, num=14 Loading iSCSI transport class v2.0-871. iscsi: registered transport (tcp) nfsd: last server has exited, flushing export cache active port 0 :139 active port 1 :445 active port 2 :20 NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory NFSD: starting 90-second grace period EXT4-fs (md0): mounted filesystem with ordered data mode [~] #
-
-
-
Vielen Dank Lutz, aber mount.cifs funktioniert auch nicht (kommt mir auch komisch vor)...Schreibfehler????
Will nochmal klarstellen, die 192.168.1.11 ist der TS-439
mount -t nfs 192.168.1.11:/share/MD0_DATA/public/volumes/istgeo /mnt/nas/
danke nochmals -
Hallo an alle,
ich habe das gleiche Problem mit einem TS-439, (mount -t cifs -o username=user,password=pass //10.22.3.12/share /share/ShareOnNMT funktioniert bei mir nicht:
mount: fs type cifs not supported by kernel). Mein Kommando:root@istgeo:/# mount -t nfs 192.168.1.11:/share/MD0_DATA/public/volumes/istgeo /mnt/nas/
mount.nfs: access denied by server while mounting 192.168.1.11:/share/MD0_DATA/public/volumes/istgeo
root@istgeo:/#Habe die Directory mit dem Web File Manager erstellt, Access für alle und von allen Servern (*).
denke auch dass es ein Problem der Autentifizierung ist.Danke für die Hilfe
-
Hallo Leute, habe gestern einen TS-439 Pro erworben und muss ein heterogenes System sichern (Windows, Linux). Habe aber noch nicht durchschaut, wie ich inkrementale backups auf beiden Plattformen erstelle (vermute bei Linux muss ich das selbst organisieren mit cp datei1.txt /..../datei1.txt). Danke für die Nachsicht....