Hallo liebe qnap-Gemeinde.
Das Netzteil meines 12 Jahre alten Qnap TS-409U ist abgeraucht. Ich habe mir ein neues bestellt und war glücklich als das NAS wieder anlief.
Nur leider sind alle Einstellungen verloren gegangen (IP, Webinterface, shares) . Mir ist es aber gelungen wieder per SSH zuzugreifen.
Hier einige Info die vielleicht den Zustand des NAS beschreiben:
Code
[/] # cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext2 rw 0 0
/proc /proc proc rw 0 0
none /dev/pts devpts rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /tmp tmpfs rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0
/dev/sda4 /mnt/ext ext3 rw,data=ordered 0 0
tmpfs /.eaccelerator.tmp tmpfs rw 0 0
[/] # cat /proc/partitions
major minor #blocks name
8 0 1465138584 sda
8 1 530113 sda1
8 2 530145 sda2
8 3 1463987385 sda3
8 4 80325 sda4
8 16 1465138584 sdb
8 17 530113 sdb1
8 18 530145 sdb2
8 19 1463987385 sdb3
8 20 80325 sdb4
8 32 1465138584 sdc
8 33 530113 sdc1
8 34 530145 sdc2
8 35 1463987385 sdc3
8 36 80325 sdc4
8 48 1465138584 sdd
8 49 530113 sdd1
8 50 530145 sdd2
8 51 1463987385 sdd3
8 52 80325 sdd4
31 0 512 mtdblock0
31 1 2048 mtdblock1
31 2 4096 mtdblock2
31 3 1024 mtdblock3
31 4 128 mtdblock4
31 5 384 mtdblock5
31 6 4096 mtdblock6
9 13 71808 md13
[/] # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md13 : active raid1 sda4[0] sdd4[3] sdc4[2] sdb4[1]
71808 blocks [4/4] [UUUU]
[/] # dmesg
device sdb: 2930277168 512-byte hdwr sectors (1500302 MB)
SCSI device sdb: write cache: enabled, read cache: enabled, supports DPO and FUA
SCSI device sdb: 2930277168 512-byte hdwr sectors (1500302 MB)
SCSI device sdb: write cache: enabled, read cache: enabled, supports DPO and FUA
sdb: sdb1 sdb2 sdb3 sdb4
sd 1:0:0:0: Attached scsi disk sdb
SCSI device sdc: 2930277168 512-byte hdwr sectors (1500302 MB)
SCSI device sdc: write cache: enabled, read cache: enabled, supports DPO and FUA
SCSI device sdc: 2930277168 512-byte hdwr sectors (1500302 MB)
SCSI device sdc: write cache: enabled, read cache: enabled, supports DPO and FUA
sdc: sdc1 sdc2 sdc3 sdc4
sd 2:0:0:0: Attached scsi disk sdc
SCSI device sdd: 2930277168 512-byte hdwr sectors (1500302 MB)
SCSI device sdd: write cache: enabled, read cache: enabled, supports DPO and FUA
SCSI device sdd: 2930277168 512-byte hdwr sectors (1500302 MB)
SCSI device sdd: write cache: enabled, read cache: enabled, supports DPO and FUA
sdd: sdd1 sdd2 sdd3 sdd4
sd 3:0:0:0: Attached scsi disk sdd
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: Attached scsi generic sg2 type 0
sd 3:0:0:0: Attached scsi generic sg3 type 0
physmap platform flash device: 00800000 at ff800000
CFI: Found no physmap-flash.0 device at location zero
JEDEC: Found no physmap-flash.0 device at location zero
cmdlinepart partition parsing not available
RedBoot partition parsing not available
QNAP Set mtd partition
Using physmap partition information
cfi_flash: Found 1 x16 devices at 0x0 in 8-bit bank
Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
erase region 0: offset=0x0,size=0x20000,blocks=64
cmdlinepart partition parsing not available
Creating 6 MTD partitions on "cfi_flash":
0x00780000-0x00800000 : "U-Boot"
QNAP(ori): slave->mtd.flags = 800, <5>QNAP: slave->mtd.flags = 800
0x00000000-0x00200000 : "Kernel"
QNAP(ori): slave->mtd.flags = c00, <5>QNAP(MTD_WRITEABLE): slave->mtd.flags = c00
0x00200000-0x00600000 : "RootFS1"
QNAP(ori): slave->mtd.flags = c00, <5>QNAP(MTD_WRITEABLE): slave->mtd.flags = c00
0x00600000-0x00700000 : "RootFS2"
QNAP(ori): slave->mtd.flags = c00, <5>QNAP(MTD_WRITEABLE): slave->mtd.flags = c00
0x00760000-0x00780000 : "U-Boot Config"
QNAP(ori): slave->mtd.flags = c00, <5>QNAP(MTD_WRITEABLE): slave->mtd.flags = c00
0x00700000-0x00760000 : "NAS Config"
QNAP(ori): slave->mtd.flags = c00, <5>QNAP(MTD_WRITEABLE): slave->mtd.flags = c00
$Id: pmc551.h,v 1.1.1.1 2007-09-07 08:41:55 ricky Exp $
Ramix PMC551 PCI Mezzanine Ram Driver. (C) 1999,2000 Nortel Networks.
pmc551: not detected
block2mtd: version $Revision: 1.1.1.1 $
ehci_hcd: block sizes: qh 128 qtd 96 itd 192 sitd 96
feroceon-ehci feroceon-ehci.4523: EHCI Host Controller
feroceon-ehci feroceon-ehci.4523: new USB bus registered, assigned bus number 1
feroceon-ehci feroceon-ehci.4523: irq 17, io mem 0x00000000
feroceon-ehci feroceon-ehci.4523: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
USB Universal Host Controller Interface driver v3.0
usb 1-1: new high speed USB device using feroceon-ehci and address 2
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
usbcore: registered new interface driver libusual
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new interface driver pegasus
drivers/usb/net/rtl8150.c: rtl8150 based usb-ethernet driver v0.6.2 (2004/08/27)
usbcore: registered new interface driver rtl8150
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver gl620a
usbcore: registered new interface driver net1080
usbcore: registered new interface driver plusb
usbcore: registered new interface driver rndis_host
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver MOSCHIP usb-ethernet driver
usbcore: registered new interface driver mdc800
drivers/usb/image/mdc800.c: v0.7.5 (30/10/2000):USB Driver for Mustek MDC800 Digital Camera
usbcore: registered new interface driver microtekX6
mice: PS/2 mouse device common for all mice
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
raid6: int32x1 27 MB/s
raid6: int32x2 45 MB/s
raid6: int32x4 51 MB/s
raid6: int32x8 47 MB/s
raid6: using algorithm int32x4 (51 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
arm4regs : 429.600 MB/sec
8regs : 330.000 MB/sec
32regs : 513.600 MB/sec
raid5: using function: 32regs (513.600 MB/sec)
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 5
VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 0
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 128K
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdd1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdd1, internal journal
EXT3-fs: mounted filesystem with ordered 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
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: checktime reached, running e2fsck is recommended
EXT3 FS on md13, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Enable watchdog...
sysinfo: Module loaded.
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
ufsd: module license 'Commercial product' taints kernel.
ufsd: driver loaded
UFSD version 6.15 (Sep 30 2008, 18:35:51)
NTFS read/write support included
$Id: ufsdvfs.c,v 1.169 2008/09/30 13:59:55 shura Exp $
ufsd: address 0x9f028000
eth0: mac address changed
eth0: link down
eth0: link up, full duplex, speed 1 Gbps
EXT2-fs warning: mounting fs with errors, running e2fsck is recommended
EXT2-fs warning: mounting fs with errors, running e2fsck is recommended
Alles anzeigen
Im Netz bin ich auf folgende Lösungsansätze gestoßen:
Bei Einsatz von QNAP Legacy-Firmware:
- #> config_util 1 Do sanity-check by .conf and auto-assemble md9
- #> config_util 4 Auto-assemble md13 (sda4)
- #> storage_boot_init 1 Auto-mount md9 on /mnt/HDA_ROOT; assemble swap device
- #> storage_boot_init 2 Assemble data RAID device and mount filesystem
- #> /etc/init.d/mountall Mount sda4 on /mnt/ext and extract ext_root
Da ich mich zwar etwas mit Linux auskenne, aber nicht genau nachvollziehen kann, was die skripte oben machen
nun meine Frage : Könnte es helfen oder wird es meine Lage verschlimmern?
Gibt es bessere Lösungen?
Vielen Dank für eure Mühe
Rugrat