General NAS-Central Forums

Welcome to the NAS community
It is currently Sun Apr 23, 2017 1:46 pm

All times are UTC




Post new topic Reply to topic  [ 7 posts ] 
Author Message
 Post subject: NAS bricched?
PostPosted: Fri Jan 25, 2013 6:21 pm 
Offline

Joined: Fri Jan 25, 2013 6:15 pm
Posts: 5
Hi to everyone,
i bought last week a second hand Sitecom MD254.
I received it and connected to power and lan does nothing...
The disk are not detectd, the led are red

from the website, the website "works" but i can open only the frontend
I know that the firmware is the "SitecomNas_v2.4.21"
but i cannot do nothing...
if the nas reply, i can see only the info page

The installer inside the CD does not find the nas...

Solutions?


Top
 Profile  
 
 Post subject: Re: NAS bricched?
PostPosted: Fri Jan 25, 2013 6:23 pm 
Offline

Joined: Fri Jan 25, 2013 6:15 pm
Posts: 5
ah, something happend that quering the nas with

http://sitecomnas/system_reboot.htm

was rebooting.. :shock:


Top
 Profile  
 
PostPosted: Fri Jan 25, 2013 6:27 pm 
Offline

Joined: Fri Jan 25, 2013 6:15 pm
Posts: 5
Jan 1 00:00:23 (none) kernel: klogd 1.5.0, log source = /proc/kmsg started. Jan 1 00:00:23 (none) kernel: Linux version 2.6.24.4 (root@localhost) (gcc version 4.2.4) #211 Wed Sep 21 16:52:20 CST 2011 Jan 1 00:00:23 (none) kernel: CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177 Jan 1 00:00:23 (none) kernel: Machine: Oxsemi NAS Jan 1 00:00:23 (none) kernel: Ignoring unrecognised tag 0x00000000 Jan 1 00:00:23 (none) kernel: Memory policy: ECC disabled, Data cache writeback Jan 1 00:00:23 (none) kernel: On node 0 totalpages: 16384 Jan 1 00:00:23 (none) kernel: DMA zone: 128 pages used for memmap Jan 1 00:00:23 (none) kernel: DMA zone: 0 pages reserved Jan 1 00:00:23 (none) kernel: DMA zone: 16256 pages, LIFO batch:3 Jan 1 00:00:23 (none) kernel: Normal zone: 0 pages used for memmap Jan 1 00:00:23 (none) kernel: Movable zone: 0 pages used for memmap Jan 1 00:00:23 (none) kernel: CPU0: D VIVT write-back cache Jan 1 00:00:23 (none) kernel: CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets Jan 1 00:00:23 (none) kernel: CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets Jan 1 00:00:23 (none) kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 Jan 1 00:00:23 (none) kernel: Kernel command line: console=ttyS0,115200 root=/dev/ram0 rw init= initrd=0x4a000000,4M elevator=cfq mtdparts=physmap-flash.0:0x20000(Uboot),0x200000@0x20000(Kernel),0x90000@0x220000(Bootfs),0x4F0000@0x2B0000(Rootfs),0x50000@0x7A0000(Config),-(ENV) mem=64M poweroutage=yes Jan 1 00:00:23 (none) kernel: PID hash table entries: 256 (order: 8, 1024 bytes) Jan 1 00:00:23 (none) kernel: console [ttyS0] enabled Jan 1 00:00:23 (none) kernel: Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Jan 1 00:00:23 (none) kernel: Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Jan 1 00:00:23 (none) kernel: Memory: 64MB = 64MB total Jan 1 00:00:23 (none) kernel: Memory: 56960KB available (3504K code, 163K data, 108K init) Jan 1 00:00:23 (none) kernel: Calibrating delay loop... 183.09 BogoMIPS (lpj=915456) Jan 1 00:00:23 (none) kernel: Security Framework initialized Jan 1 00:00:23 (none) kernel: Mount-cache hash table entries: 512 Jan 1 00:00:23 (none) kernel: CPU: Testing write buffer coherency: ok Jan 1 00:00:23 (none) kernel: net_namespace: 64 bytes Jan 1 00:00:23 (none) kernel: NET: Registered protocol family 16 Jan 1 00:00:23 (none) kernel: Number of DMA channels = 5, version = 4 Jan 1 00:00:23 (none) kernel: Allocating 891 SRAM generic DMA descriptors Jan 1 00:00:23 (none) kernel: Chip Id: die-id 0x0b75356d6700 read back 0xbeefcafe Jan 1 00:00:23 (none) kernel: SCSI subsystem initialized Jan 1 00:00:23 (none) kernel: libata version 3.00 loaded. Jan 1 00:00:23 (none) kernel: usbcore: registered new interface driver usbfs Jan 1 00:00:23 (none) kernel: usbcore: registered new interface driver hub Jan 1 00:00:23 (none) kernel: usbcore: registered new device driver usb Jan 1 00:00:23 (none) kernel: NET: Registered protocol family 2 Jan 1 00:00:23 (none) kernel: IP route cache hash table entries: 1024 (order: 0, 4096 bytes) Jan 1 00:00:23 (none) kernel: TCP established hash table entries: 2048 (order: 2, 16384 bytes) Jan 1 00:00:23 (none) kernel: TCP bind hash table entries: 2048 (order: 1, 8192 bytes) Jan 1 00:00:23 (none) kernel: TCP: Hash tables configured (established 2048 bind 2048) Jan 1 00:00:23 (none) kernel: TCP reno registered Jan 1 00:00:23 (none) kernel: checking if image is initramfs...it isn't (no cpio magic); looks like an initrd Jan 1 00:00:23 (none) kernel: Freeing initrd memory: 4096K Jan 1 00:00:23 (none) kernel: Probing for Synopsis GMAC, unit 0 Jan 1 00:00:23 (none) kernel: eth0: PHY is LSI ET1011C Jan 1 00:00:23 (none) kernel: eth0: GMAC ver = 51, vendor ver = 17 at 0xe8000000, IRQ 8 Jan 1 00:00:23 (none) kernel: eth0: Found PHY at address 1, type 0x0282f014 -> 10/100/1000 Jan 1 00:00:23 (none) kernel: eth0: Ethernet addr: 00:30:e0:00:00:00 Jan 1 00:00:23 (none) kernel: thermAndFan: initializing - ox810 Jan 1 00:00:23 (none) kernel: mp_leds: Module loaded. Jan 1 00:00:23 (none) kernel: mp_power_button: Power button driver registered Jan 1 00:00:23 (none) kernel: mp_reset_button: Reset button driver registered Jan 1 00:00:23 (none) kernel: mp_otb_button: otb button driver registered Jan 1 00:00:23 (none) kernel: squashfs: version 3.4 (2008/08/26) Jan 1 00:00:23 (none) kernel: NTFS driver 2.1.29 [Flags: R/W]. Jan 1 00:00:23 (none) kernel: JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc. Jan 1 00:00:23 (none) kernel: fuse init (API version 7.9) Jan 1 00:00:23 (none) kernel: SGI XFS with large block numbers, no debug enabled Jan 1 00:00:23 (none) kernel: SGI XFS Quota Management subsystem Jan 1 00:00:23 (none) kernel: io scheduler noop registered Jan 1 00:00:23 (none) kernel: io scheduler anticipatory registered Jan 1 00:00:23 (none) kernel: io scheduler deadline registered Jan 1 00:00:23 (none) kernel: io scheduler cfq registered (default) Jan 1 00:00:23 (none) kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled Jan 1 00:00:23 (none) kernel: serial8250: ttyS0 at MMIO 0x44900000 (irq = 29) is a 16550A Jan 1 00:00:23 (none) kernel: RAMDISK driver initialized: 16 RAM disks of 6144K size 1024 blocksize Jan 1 00:00:23 (none) kernel: loop: module loaded Jan 1 00:00:23 (none) kernel: Driver 'sd' needs updating - please use bus_type methods Jan 1 00:00:23 (none) kernel: ox810sata: OX810 sata core. Jan 1 00:00:23 (none) kernel: scsi0 : oxnassata Jan 1 00:00:23 (none) kernel: ata1: SATA max UDMA/133 irq 18 Jan 1 00:00:23 (none) kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 1 00:00:23 (none) kernel: ata1.00: qc timeout (cmd 0xec) Jan 1 00:00:23 (none) kernel: ox810sata_bmdma_stop - aborting DMA Jan 1 00:00:23 (none) kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) Jan 1 00:00:23 (none) kernel: ata1: failed to recover some devices, retrying in 5 secs Jan 1 00:00:23 (none) kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 1 00:00:23 (none) kernel: ata1.00: ATA-8: Hitachi HTS543232L9A300, FB4OC40C, max UDMA/133 Jan 1 00:00:23 (none) kernel: ata1.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 0/32) Jan 1 00:00:23 (none) kernel: ata1.00: Drive reports diagnostics failure. This may indicate a drive Jan 1 00:00:23 (none) kernel: ata1.00: fault or invalid emulation. Contact drive vendor for information. Jan 1 00:00:23 (none) kernel: ata1.00: configured for UDMA/133 Jan 1 00:00:23 (none) kernel: scsi 0:0:0:0: Direct-Access ATA Hitachi HTS54323 FB4O PQ: 0 ANSI: 5 Jan 1 00:00:23 (none) kernel: sd 0:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB) Jan 1 00:00:23 (none) kernel: sd 0:0:0:0: [sda] Write Protect is off Jan 1 00:00:23 (none) kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Jan 1 00:00:23 (none) kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 1 00:00:23 (none) kernel: sd 0:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB) Jan 1 00:00:23 (none) kernel: sd 0:0:0:0: [sda] Write Protect is off Jan 1 00:00:23 (none) kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Jan 1 00:00:23 (none) kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 1 00:00:23 (none) kernel: sda: sda1 Jan 1 00:00:23 (none) kernel: sd 0:0:0:0: [sda] Attached SCSI disk Jan 1 00:00:23 (none) kernel: ox810sata: OX810 sata core. Jan 1 00:00:23 (none) kernel: scsi1 : oxnassata Jan 1 00:00:23 (none) kernel: ata2: SATA max UDMA/133 irq 18 Jan 1 00:00:23 (none) kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 1 00:00:23 (none) kernel: ata2.00: HPA detected: current 625140335, native 625142448 Jan 1 00:00:23 (none) kernel: ata2.00: ATA-8: ST3320613AS, SD22, max UDMA/133 Jan 1 00:00:23 (none) kernel: ata2.00: 625140335 sectors, multi 0: LBA48 NCQ (depth 0/32) Jan 1 00:00:23 (none) kernel: ata2.00: configured for UDMA/133 Jan 1 00:00:23 (none) kernel: scsi 1:0:0:0: Direct-Access ATA ST3320613AS SD22 PQ: 0 ANSI: 5 Jan 1 00:00:23 (none) kernel: sd 1:0:0:0: [sdb] 625140335 512-byte hardware sectors (320072 MB) Jan 1 00:00:23 (none) kernel: sd 1:0:0:0: [sdb] Write Protect is off Jan 1 00:00:23 (none) kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jan 1 00:00:23 (none) kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 1 00:00:23 (none) kernel: sd 1:0:0:0: [sdb] 625140335 512-byte hardware sectors (320072 MB) Jan 1 00:00:23 (none) kernel: sd 1:0:0:0: [sdb] Write Protect is off Jan 1 00:00:23 (none) kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jan 1 00:00:23 (none) kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 1 00:00:23 (none) kernel: sdb: sdb1 < sdb5 > Jan 1 00:00:23 (none) kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Jan 1 00:00:23 (none) kernel: physmap platform flash device: 00800000 at 41000000 Jan 1 00:00:23 (none) kernel: physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank Jan 1 00:00:23 (none) kernel: Amd/Fujitsu Extended Query Table at 0x0040 Jan 1 00:00:23 (none) kernel: physmap-flash.0: Swapping erase regions for broken CFI table. Jan 1 00:00:23 (none) kernel: number of CFI chips: 1 Jan 1 00:00:23 (none) kernel: cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness. Jan 1 00:00:23 (none) kernel: 6 cmdlinepart partitions found on MTD device physmap-flash.0 Jan 1 00:00:23 (none) kernel: Creating 6 MTD partitions on "physmap-flash.0": Jan 1 00:00:23 (none) kernel: 0x00000000-0x00020000 : "Uboot" Jan 1 00:00:23 (none) kernel: 0x00020000-0x00220000 : "Kernel" Jan 1 00:00:23 (none) kernel: 0x00220000-0x002b0000 : "Bootfs" Jan 1 00:00:23 (none) kernel: 0x002b0000-0x007a0000 : "Rootfs" Jan 1 00:00:23 (none) kernel: 0x007a0000-0x007f0000 : "Config" Jan 1 00:00:23 (none) kernel: 0x007f0000-0x00800000 : "ENV" Jan 1 00:00:23 (none) kernel: 10 Dec 2004 USB 2.0 'Enhanced' Host Controller (EHCI) Driver@e7000000 Device ID register 42fa05 Jan 1 00:00:23 (none) kernel: oxnas-ehci oxnas-ehci.0: OXNAS EHCI Host Controller Jan 1 00:00:23 (none) kernel: oxnas-ehci oxnas-ehci.0: new USB bus registered, assigned bus number 1 Jan 1 00:00:23 (none) kernel: oxnas-ehci oxnas-ehci.0: irq 7, io mem 0x00000000 Jan 1 00:00:23 (none) kernel: oxnas-ehci oxnas-ehci.0: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004 Jan 1 00:00:23 (none) kernel: usb usb1: configuration #1 chosen from 1 choice Jan 1 00:00:23 (none) kernel: hub 1-0:1.0: USB hub found Jan 1 00:00:23 (none) kernel: hub 1-0:1.0: 3 ports detected Jan 1 00:00:23 (none) kernel: usbcore: registered new interface driver usbtest Jan 1 00:00:23 (none) kernel: md: linear personality registered for level -1 Jan 1 00:00:23 (none) kernel: md: raid0 personality registered for level 0 Jan 1 00:00:23 (none) kernel: md: raid1 personality registered for level 1 Jan 1 00:00:23 (none) kernel: md: faulty personality registered for level -5 Jan 1 00:00:23 (none) kernel: device-mapper: uevent: version 1.0.3 Jan 1 00:00:23 (none) kernel: device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-devel@redhat.com Jan 1 00:00:23 (none) kernel: TCP cubic registered Jan 1 00:00:23 (none) kernel: NET: Registered protocol family 1 Jan 1 00:00:23 (none) kernel: NET: Registered protocol family 17 Jan 1 00:00:23 (none) kernel: NET: Registered protocol family 5 Jan 1 00:00:23 (none) kernel: md: Autodetecting RAID arrays. Jan 1 00:00:23 (none) kernel: md: Scanned 0 and added 0 devices. Jan 1 00:00:23 (none) kernel: md: autorun ... Jan 1 00:00:23 (none) kernel: md: ... autorun DONE. Jan 1 00:00:23 (none) kernel: RAMDISK: Compressed image found at block 0 Jan 1 00:00:23 (none) kernel: VFS: Mounted root (ext2 filesystem). Jan 1 00:00:23 (none) kernel: Freeing init memory: 108K Jan 1 00:00:23 (none) kernel: Failed to execute . Attempting defaults... Jan 1 00:00:23 (none) kernel: md: md1 stopped. Jan 1 00:00:23 (none) kernel: md: md1 stopped. Jan 1 00:00:24 (none) kernel: attempt to access beyond end of device Jan 1 00:00:24 (none) kernel: sdb1: rw=0, want=8, limit=2 Jan 1 00:00:24 (none) kernel: Adding 1052k swap on /home/.swap. Priority:-1 extents:6 across:1072k Jan 1 00:00:24 (none) kernel: eth0: PHY is LSI ET1011C Jan 1 00:00:24 (none) kernel: CoPro: Programming start address as 0x9801e000 (basic adr = 0x9801e000) Jan 1 00:00:24 (none) kernel: eth0: LSI ET1011C PHY no Rx clk workaround start Jan 1 00:00:24 (none) kernel: Resetting GMAC Jan 1 00:00:24 (none) kernel: eth0: LSI ET1011C PHY no Rx clk workaround end Jan 1 00:00:24 (none) kernel: GMAC reset complete Jan 1 00:00:25 (none) kernel: eth0: PHY is LSI ET1011C Jan 1 00:00:25 (none) kernel: CoPro: Programming start address as 0x9801e000 (basic adr = 0x9801e000) Jan 1 00:00:25 (none) kernel: eth0: LSI ET1011C PHY no Rx clk workaround start Jan 1 00:00:25 (none) kernel: Resetting GMAC Jan 1 00:00:25 (none) kernel: eth0: LSI ET1011C PHY no Rx clk workaround end Jan 1 00:00:25 (none) kernel: GMAC reset complete Jan 1 00:00:26 (none) kernel: eth0: PHY is LSI ET1011C Nov 26 14:59:00 (none) kernel: eth0: link down Nov 26 14:59:00 (none) kernel: usbcore: registered new interface driver usblp Nov 26 14:59:00 (none) kernel: Initializing USB Mass Storage driver... Nov 26 14:59:00 (none) kernel: usbcore: registered new interface driver usb-storage Nov 26 14:59:00 (none) kernel: USB Mass Storage support registered. Nov 26 14:59:02 (none) kernel: eth0: link up, 1000Mbps, full-duplex, using pause, lpa 0xCDE1


Top
 Profile  
 
 Post subject: Re: NAS bricched?
PostPosted: Sat Jan 26, 2013 9:39 am 
Offline

Joined: Fri Jan 25, 2013 6:15 pm
Posts: 5
If i ping the NAS this is the output:

Code:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
ping sitecomnas -t

Pinging sitecomnas.fritz.box [192.168.178.23] with 32 bytes of data:
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time=1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time=1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time=1ms TTL=64
Request timed out.
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time=3ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.178.23: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.


In this part the website "works", (i have the request of the login and sometimes if i am sync with the reply i can go inside menu)
then the nas reply every time, but the web interface is down...


Top
 Profile  
 
 Post subject: Re: NAS bricched?
PostPosted: Sat Jan 26, 2013 11:17 am 
Offline

Joined: Sat Jan 26, 2013 10:11 am
Posts: 3
Hi,
I had more or less the same problem.
This is what I did:
- Power off the unit and extract the disk(s)
- Powe on the unit and press the reset (that is the little hole orer the power connector) for a long time (till the fan will startup again) mai be 20 or 30 seconds.
Now the unit will restart and you will be able to see the http interface and all things.
I uptated again the unit to the last firmware (SitecomNas.2.4.21.bin) from file (no internet update)

Now is time to plug again your disk and see if the unit works.
In order to have all correctly working I needed to reformat the hard disk with a windows PC then when I restarted the Media Center I needed to reformat again the disk with "Disk Settings" in the "Setup" menu.

Now all is working fine.

Let me know if all is working.

See you!

Ga


Top
 Profile  
 
 Post subject: Re: NAS bricched?
PostPosted: Sat Jan 26, 2013 12:34 pm 
Offline

Joined: Fri Jan 25, 2013 6:15 pm
Posts: 5
I don't know why but today i got it working...
i re-install the last firmware.. SitecomNas.2.4.21.bin
and i give the correct NTP server..
I used before another router (Linksys) and was working, now (magic) works also with my fritzbox :)

I installed two HD and format them with the format button in the web interface... :D

Do you know how to format again a devices?
I mean, if is already inside the nas service, i would like to erase completely the disk and have it as blank...


Top
 Profile  
 
 Post subject: Re: NAS bricched?
PostPosted: Sat Jan 26, 2013 3:57 pm 
Offline

Joined: Sat Jan 26, 2013 10:11 am
Posts: 3
The only way I found is to format the disk previously with a PC and after reinstall it on the bay of the NAS and then format with the utility of the SitecomNas.

Ga


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 7 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 7 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group