Results 1 to 2 of 2

Thread: N2100: JBOD resize fail(umount fail).

  1. #1
    Registered+
    Join Date
    Mar 2008
    Posts
    25
    Thanks
    0
    Thanked
    0 times in 0 posts

    N2100: JBOD resize fail(umount fail).

    1:---------------------------------------------------------------------------
    Came home today and noticed the Blinking " ! "
    Rebooted my NAS and here is what the Log says.....

    2008/04/02 19:40:27 N2100 JBOD resize fail(umount fail).
    2008/04/02 19:40:00 N2100 : N2100 boot successfully.
    2008/04/02 19:39:52 N2100 : RAID status is HEALTHY now.
    2008/04/02 19:38:15 N2100 : The system N2100 shutdown.

    2:---------------------------------------------------------------------------
    Everything apears to be working still, I can access my nas and read/write files to it....


    3:---------------------------------------------------------------------------
    FIRMWARE:
    Manufacturer Thecus
    Product No. N2100
    Firmware Version 2.01.09
    Up Time 21 minutes

    4:---------------------------------------------------------------------------
    Logged in via ssh here is a dmesg.

    N2100:~# dmesg
    h table entries: 4096 (order: 12, 65536 bytes)
    Console: colour dummy device 80x30
    Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    Memory: 512MB = 512MB total
    Memory: 473600KB available (2075K code, 509K data, 72K init)
    Calibrating delay loop... 593.10 BogoMIPS (lpj=2965504)
    Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
    CPU: Testing write buffer coherency: ok
    Freeing initrd memory: 43008K
    NET: Registered protocol family 16
    PCI: bus0: Fast back to back transfers disabled
    SCSI subsystem initialized
    Enable CCNT succ
    Intel IOP3XX DMA Copyright(c) 2004 Intel Corporation
    NetWinder Floating Point Emulator V0.97 (double precision)
    Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
    NTFS driver 2.1.20 [Flags: R/W DEBUG].
    JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
    Initializing Cryptographic API
    RAMDISK driver initialized: 16 RAM disks of 40960K size 1024 blocksize
    loop: loaded (max 203 devices)
    Thecus : Init thecus event proc entry .
    PPP generic driver version 2.4.2
    PPP Deflate Compression module registered
    PPP BSD Compression module registered
    ipddp.c:v0.01 8/28/97 Bradford W. Johnson <johns393@maroon.tc.umn.edu>
    ipddp0: Appletalk-IP Encap. mode by Bradford W. Johnson <johns393@maroon.tc.umn.edu>
    Using anticipatory io scheduler
    mice: PS/2 mouse device common for all mice
    md: linear personality registered as nr 1
    md: raid0 personality registered as nr 2
    md: raid1 personality registered as nr 3
    md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
    NET: Registered protocol family 2
    IP: routing cache hash table of 4096 buckets, 32Kbytes
    TCP: Hash tables configured (established 131072 bind 65536)
    NET: Registered protocol family 1
    NET: Registered protocol family 17
    NET: Registered protocol family 5
    md: Autodetecting RAID arrays.
    md: autorun ...
    md: ... autorun DONE.
    RAMDISK: Compressed image found at block 0
    VFS: Mounted root (ext2 filesystem).
    Freeing init memory: 72K
    Warning: unable to open an initial console.
    cloop: Initializing cloop v2.01
    cloop: loaded (max 8 devices)
    cloop: losetup_file: 129 blocks, 65536 bytes/block, largest block is 62364 bytes.
    cloop: losetup_file: 65 blocks, 65536 bytes/block, largest block is 24937 bytes.
    cloop: losetup_file: 407 blocks, 65536 bytes/block, largest block is 59484 bytes.
    CFI: cfi_probe_chip qry_present failed
    IOP3xx Flash: Found 1 x16 devices at 0x0 in 16-bit bank
    Intel/Sharp Extended Query Table at 0x0031
    cfi_cmdset_0001: Erase suspend on write enabled
    0: offset=0x0,size=0x20000,blocks=128
    Using buffer write method
    6 RedBoot partitions found on MTD device IOP3xx Flash
    Creating 6 MTD partitions on "IOP3xx Flash":
    0x00000000-0x00040000 : "RedBoot"
    0x00040000-0x00d40000 : "ramdisk"
    0x00d40000-0x00ea0000 : "kernel"
    0x00ea0000-0x00fc0000 : "user"
    0x00fc0000-0x00fe0000 : "RedBoot config"
    0x00fe0000-0x01000000 : "FIS directory"
    r8169 Gigabit Ethernet driver 2.2LK loaded
    eth0: Identified chip type is 'RTL8169s/8110s'.
    eth0: RTL8169 at 0xfe000000, 00:14:fd:10:43:d2, IRQ 27
    eth1: Identified chip type is 'RTL8169s/8110s'.
    eth1: RTL8169 at 0xfe000400, 00:14:fd:10:43:d3, IRQ 30
    Probing F75373
    Allocating memory for F75373
    client=c30ebc00 client.id=61442 Attaching F75373
    Data[0]=0x19
    F75373 Vendor ID=19F75373 Try count 1 ,Probe result=0
    F75373 Time 1 rtc_rs372_probe try success !!
    In Read Mode Addr Change to 0x2D
    In Read Mode Addr Change to 0x2E
    f75373_rw Read try 3 time
    Read F75375 register 0xF0 value = 0x80
    Set F75375 register 0xF0 value to 0x02
    Read F75375 register 0xF0 value = 0x82
    Probing rs372
    rtc_rs372_probe Try count 1 ,Probe result=0
    rtc_rs372_probe Time 1 rtc_rs372_probe try success !!
    Probing pca9532
    Probe result=0
    libata version 1.11 loaded.
    sata_sil version 0.9
    SFISCFG0: 0x10401554
    SFISCFG1: 0x10401554
    ata1: SATA max UDMA/100 cmd 0xE09E0080 ctl 0xE09E008A bmdma 0xE09E0000 irq 29
    ata2: SATA max UDMA/100 cmd 0xE09E00C0 ctl 0xE09E00CA bmdma 0xE09E0008 irq 29
    ata1: dev 0 cfg 49:2f00 82:746b 83:7f61 84:4123 85:7469 86:bc41 87:4123 88:007f
    ata1: dev 0 ATA, max UDMA/133, 1465149168 sectors: lba48
    ata1: dev 0 configured for UDMA/100
    scsi0 : sata_sil
    ata2: dev 0 cfg 49:2f00 82:746b 83:7f61 84:4123 85:7469 86:bc41 87:4123 88:007f
    ata2: dev 0 ATA, max UDMA/133, 1953525168 sectors: lba48
    ata2: dev 0 configured for UDMA/100
    scsi1 : sata_sil
    Vendor: ATA Model: WDC WD7500AAKS-0 Rev: 30.0
    Type: Direct-Access ANSI SCSI revision: 05
    Thecus Tray: 1, sda
    SCSI device sda: 1465149168 512-byte hdwr sectors (750156 MB)
    SCSI device sda: drive cache: write back
    sda: sda1 sda2 sda3
    Attached scsi disk sda at scsi0, channel 0, id 0, lun 0, devfs scsi/host0/bus0/target0/lun0
    criticalevent_user: disk_add sda
    Vendor: ATA Model: WDC WD10EACS-00Z Rev: 01.0
    Type: Direct-Access ANSI SCSI revision: 05
    Thecus Tray: 2, sdb
    SCSI device sdb: 1953525168 512-byte hdwr sectors (1000205 MB)
    SCSI device sdb: drive cache: write back
    sdb: sdb1 sdb2 sdb3
    Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0, devfs scsi/host1/bus0/target0/lun0
    criticalevent_user: disk_add sdb
    port=0x02,val=0x31
    port=0x04,val=0x97
    Write reg 0=80
    Write reg 0=1
    Set F75375 register 0xF0 value to 0x02
    1 VAL1=50
    1 VAL1=50
    1 VAL1(0x60)=50
    2 VAL1=50
    2 VAL1=50
    2 VAL1(0x60)=50
    Write reg A0=32
    Write reg B0=32
    Write reg A1=2D
    Write reg B1=2D
    Write reg A2=23
    Write reg B2=23
    Write reg A3=19
    Write reg B3=19
    r8169: eth0: link up
    ip_tables: (C) 2000-2002 Netfilter core team
    ip_conntrack version 2.1 (4096 buckets, 32768 max) - 308 bytes per conntrack
    Clear Critical Queue.
    DEBUG STOP_ARRAY...
    do_md_stop: NO raid ...
    md: md1 stopped.
    criticalevent_user: raid_create md1
    md: bind<sdb1>
    md: bind<sda1>
    raid1: raid set md1 active with 2 out of 4 mirrors
    criticalevent_user: raid_degrade md1
    RAID1 run(): mddev->recovery=0
    do_md_run: END ...mddev->recovery=32
    DEBUG STOP_ARRAY...
    do_md_stop: NO raid ...
    md: md0 stopped.
    criticalevent_user: raid_create md0
    md: bind<sdb2>
    md: bind<sda2>
    criticalevent_user: raid_healthy md0
    do_md_run: END ...mddev->recovery=32
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on md0, internal journal
    EXT3-fs: mounted filesystem with writeback data mode.
    usbcore: registered new driver usbfs
    usbcore: registered new driver hub
    ehci_hcd 0000:00:04.2: EHCI Host Controller
    ehci_hcd 0000:00:04.2: irq 29, pci mem 0x800a0400
    ehci_hcd 0000:00:04.2: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:04.2: USB 2.0 initialized, EHCI 1.00, driver 26 Oct 2004
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 4 ports detected
    USB Universal Host Controller Interface driver v2.2
    uhci_hcd 0000:00:04.0: UHCI Host Controller
    uhci_hcd 0000:00:04.0: irq 28, io base 0xfe000800
    uhci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 2
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 2 ports detected
    uhci_hcd 0000:00:04.1: UHCI Host Controller
    uhci_hcd 0000:00:04.1: irq 27, io base 0xfe000820
    uhci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 3
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 2 ports detected
    Initializing USB Mass Storage driver...
    Adding 1003896k swap on /dev/md1. Priority:-1 extents:1
    usbcore: registered new driver usb-storage
    USB Mass Storage support registered.
    usbcore: registered new driver usblp
    drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
    zd1211 - SourceForge.net: zd1211 &#187; home - r83
    Based on Wireless,computer,Zydas ZD-1211 driver,Wireless Usb Adapter, driver version 2.5.0.0
    usbcore: registered new driver zd1211
    ZD1211B - SourceForge.net: zd1211 &#187; home - r83
    Based on Wireless,computer,Zydas ZD-1211 driver,Wireless Usb Adapter, driver version 2.5.0.0
    usbcore: registered new driver zd1211b
    N2100:~#

  2. #2
    Registered+
    Join Date
    Mar 2008
    Posts
    25
    Thanks
    0
    Thanked
    0 times in 0 posts

    Re: N2100: JBOD resize fail(umount fail).

    UPDATE:

    I Installed the [Thecus]FSCK Module from onbeat, ran it, then clicked reboot when told.
    Upon reboot the N2100 Raid tab displayed Checking Disk &#37;. When complete my "!" went away.

    LOG:
    2008/04/03 11:43:14 NASBOX : User admin logged in from 192.168.0.123.
    2008/04/03 11:41:32 NASBOX : NASBOX boot successfully.
    2008/04/03 11:41:26 NASBOX : RAID status is HEALTHY now.
    2008/04/03 11:40:04 NASBOX : NASBOX reboot.
    2008/04/03 11:39:57 NASBOX : The log file has been created successfully.


    When the blinking "!" is displayed I wish the Log would tell you why it is blinking.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. NAS Hardware Advice Needed - Considering Thecus N2100
    By chooky78 in forum PC Hardware and Components
    Replies: 6
    Last Post: 18-01-2007, 04:12 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •