I've been using the Duo NAS for some years now, and since a few weeks, I get a systematic fsck.ext2 at the boot time. I don't understand what's wrong with the filesystem. It is supposely repaired, I access files through many protocols, and then a few hours/days later, I shut the NAS down using the unix shutdown command. Also, I'm suprised by this ext2 check instead of ext3. The fsck command is pretty basic with -C4 -y options.
Can somebody give me indications of what's wrong in my process ?
Many thanks for your time. YanK
Here's dmesg and /var/log/fsck...
Linux version 2.6.17.14ReadyNAS (root@calzone) (gcc version 3.3.5 (Infrant 3.3.5-1)) #1 Wed Sep 22 04:42:09 PDT 2010 You system is PZERO. ASIC=IT3107 On node 0 totalpages: 16384 Normal zone: 15360 pages, LIFO batch:3 DMA zone: 1024 pages, LIFO batch:0 zlist 0 802ef15c zone 802eef14, name Normal zlist 1 802ef170 zone 802eeccc, name DMA zlist 2 802ef184 zone 802eef14, name Normal Built 1 zonelists Kernel command line: root=/dev/ram0 init=/linuxrc rw raid=noautodetect profile=2 kernel profiling enabled (shift: 2) PID hash table entries: 2048 (order: 11, 8192 bytes) Dentry cache hash table entries: 32768 (order: 3, 131072 bytes) Inode-cache hash table entries: 16384 (order: 2, 65536 bytes) Memory: 226176k/262144k available (2592k kernel code, 35872k reserved, 656k data, 96k init, 0k highmem) init_mm.pgd 8f0ff000 Calibrating delay loop... 186.36 BogoMIPS (lpj=931840) Mount-cache hash table entries: 2048 checking if image is initramfs...it isn't (no cpio magic); looks like an initrd Freeing initrd memory: 16384k freed NET: Registered protocol family 16 usbcore: registered new driver usbfs usbcore: registered new driver hub NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: -1, 8192 bytes) TCP established hash table entries: 8192 (order: 1, 32768 bytes) TCP bind hash table entries: 4096 (order: 0, 16384 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered audit: initializing netlink socket (disabled) audit(1070280003.190:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 4096 (order 0, 16384 bytes) Installing knfsd (copyright (C) 1996 okir@monad.swb.de). Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize loop: loaded (max 8 devices) nbd: registered device at major 43 tun: Universal TUN/TAP device driver, 1.6 tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> md: raid0 personality registered for level 0 md: raid1 personality registered for level 1 md: raid5 personality registered for level 5 md: raid4 personality registered for level 4 xor engine => SPARC. device-mapper: 4.6.0-ioctl (2006-02-17) initialised: dm-devel@redhat.com Serial: Padre driver $Revision: 1.1.1.1 $ 2 ports ttyS0 at I/O 0x0 (irq = 7) is a padre uart ttyS1 at I/O 0x0 (irq = 😎 is a padre uart oprofile: using timer interrupt. TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 NET: Registered protocol family 5 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com> All bugs added by David S. Miller <davem@redhat.com> md: Skipping autodetection of RAID arrays. (raid=noautodetect) RAMDISK: Compressed image found at block 0 VFS: Mounted root (ext2 filesystem). Freeing unused kernel memory: 96k freed padre_i2c: module license 'Infrant Technologies, Inc.' taints kernel. padre_i2c: no version for "udiv" found: kernel tainted. TWSI Initialize Padre NSPIO setup: 80353394... No argv, go to default. raid5: xor select to PADRE_RXA. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx padre chip scan,token=1 Scan the padre NSP IO hardware. Need memory for RTEngine 63680 PIO mode on chan 7 DMA mode on chan 0 DMA mode on chan 1 Padre IDE controller, sata start:1 No TLER on ST31500341AS € hdc: ST31500341AS (s/n:9VS3RFVY), ATA DISK drive (ATAEXT) No TLER on ST31500341AS € hde: ST31500341AS (s/n:9VS3RD0X), ATA DISK drive (ATAEXT) ide1 at 0x200-0x207,0x208 on irq 32 ide2 at 0x280-0x287,0x288 on irq 33 Update NSPIO settings 80353394. hdc: max request size: 512KiB hdc: use capacity 2930277168 sectors (1500301 MB) Drive support hpa, still should not change max addr. hdc: 2930256688 sectors (1500291 MB), CHS=65535/255/63 hdc: cache flushes supported hdc: hdc1 hdc2 hdc3 < hdc5 > hde: max request size: 512KiB hde: use capacity 2930277168 sectors (1500301 MB) Drive support hpa, still should not change max addr. hde: 2930256688 sectors (1500291 MB), CHS=65535/255/63 hde: cache flushes supported hde: unknown partition table Link to padre IO.
RAID disks check: ALL = 22/33/0/0/0/0/0/0, 2 IDE = 22/0/0/0/0/0/0/0, 1 MD = 0/0/0/0/0/0/0/0, 0 RAID rule check result: 0 md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 Disk protected mark = 1 x_raid_start: 1,current:0 BDL_count= 0, fw=SN04, model= BDL_count= 1, fw=SN04, model= GOT MEMORY FOR DJ: 128*4k Drive hdc SB at 2930263632(-sbs) CURRENT Drive hde SB at 2930263632(-sbs) CURRENT x_raid_start: 1,result:0 Find PHY: 0 Lookup PHY ID: 0x0141, 0x0c P0 GPIO initialization... BOARDID=1 Boot type/reason: normal/2/24M39C790101C Adjusting fan pwm................ I2C device 48 doesn't exist I2C device 49 doesn't exist I2C device 4a doesn't exist I2C device 4b doesn't exist The LM75 can not be found NAND device: Manufacture ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit) Samsung NAND flash rev C size of table 4096 table is there 0x8 bad block 2290 replacing by 4095 total bad block 1 bad 2290 = 4095 bad 4095 = -1 Total bad block number 1 retlen = 0x0200 VPD checksum = 0xc62 ECC is ON Creating 2 MTD partitions on "NAND 64MiB 3,3V 8-bit": 0x00000000-0x00100000 : "P0 flash partition 1" 0x00100000-0x03ffc000 : "P0 flash partition 2" NEON flash: probing 8-bit flash bus CFI: Found no NEON flash device at location zero NEON flash: unknown flash device, mfr id 0x1, dev id 0x0 NEON flash: Found no Atmel device at location zero This board is not supported. You can use parm_extport=X module parm. I2C device 1f doesn't exist I2C device 1b doesn't exist LCD device not found X_RAID_START startstop XRAID command = start, flash_cache=0 X_RAID clean shutdown indicator: 0x0. 0 2 2 0 0 0 0 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 Update time for sb 1 = 4bdbe9fd. Update time for sb 2 = 4bdbe9fd. Update time for sb 3 = 0. Update time for sb 4 = 0. recent_ID = 1, select_ID=1, most_ID=2 right_mac=2 Selected sb 1, ctime=4bdbe9fd, id=f2ce8770. Use this image: 1
VERSION/ID : SB=(V:0.1.0) ID=<f2ce8770.00000000.00000000.00000000> CT:4bdbe9fd RAID_INFO : DISKS(TOTAL:2 RAID:2 PARITY:1 ONL:2 WRK:2 FAILED:0 SPARE:0 BASE:0) SZ:2930256688 UT:00000000 STATE:0 LUNS:2 EXTCMD:1 LSZ:2930256686 LOGICAL_DRIVE : 0: B:0000000002 E:0004096000 R:1 O:1 I:1:000000000 DM:3 LOGICAL_DRIVE : 1: B:0004096002 E:2926160686 R:1 O:1 I:1:380407810 DM:3 PHYSICAL_DRIVE: 0: DISK<N:0/1,hdc(22,0),ID:0,PT:1,SZ:2930256688,ST: B:online> PHYSICAL_DRIVE: 1: DISK<N:1/2,hde(33,0),ID:1,PT:1,SZ:2930256688,ST:P :online> CURRENT_DRIVE : DISK<N:0/1,XXX(22,0),ID:0,PT:1,SZ:2930256688,ST: B:online> Need to do drives searching. Find p d at 1, chn 1 Total=2; raid=2; ready=0; work=2; failed=0 Check degraded mode, start_pos=1 No drive missing, X_RAID run in opt mode. Change X_RAID running mode from 0 to 1 ::Update backup SB. X_RAID: recovery thread got woken up ... New = 1, source drives = 3, current/active=2/2 :<6> hdc: hdc1 hdc2 hdc3 < hdc5 > :<6> hde: unknown partition table kjournald starting. Commit interval 5 seconds EXT3 FS on hdc1, internal journal EXT3-fs: mounted filesystem with ordered data mode. linked, 1000mbps mode ::::<4>EXT2-fs warning (device hdc1): ext2_fill_super: mounting ext3 filesystem as ext2 Adding 255968k swap on /dev/hdc2. Priority:0 extents:1 across:255968k enable_irq(11) unbalanced from f804059c :<6>hdc: cache flushes supported chn=0, statu/LP_S=0x(d0/d050)29, 32 :<6>hde: cache flushes supported chn=0, statu/LP_S=0x(d0/d050)29, 32 chn=0, statu/LP_S=0x(d0/d050)29, 32 :<6> hde:chn=1, statu/LP_S=0x(d0/d050)29, 16 unknown partition table ::::::::<4>EXT2-fs warning (device dm-0): ext2_fill_super: mounting ext3 filesystem as ext2 ::::NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory NFSD: starting 90-second grace period :<6>ehci_hcd 0000:00:17.2: EHCI Host Controller ehci_hcd 0000:00:17.2: new USB bus registered, assigned bus number 1 ehci_hcd 0000:00:17.2: irq 27, io mem 0x5c010000 ehci_hcd 0000:00:17.2: USB 2.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: 4 ports detected USB Universal Host Controller Interface driver v3.0 PCI: VIA IRQ fixup for 0000:00:17.0, from 0 to 11 uhci_hcd 0000:00:17.0: UHCI Host Controller uhci_hcd 0000:00:17.0: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:17.0: irq 27, io base 0x5c001000 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected PCI: VIA IRQ fixup for 0000:00:17.1, from 0 to 11 uhci_hcd 0000:00:17.1: UHCI Host Controller uhci_hcd 0000:00:17.1: new USB bus registered, assigned bus number 3 uhci_hcd 0000:00:17.1: irq 27, io base 0x5c001020 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected :<4>nfsd: last server has exited nfsd: unexporting all filesystems RPC: failed to contact portmap (errno -5). NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory NFSD: starting 90-second grace period :<6>hdc: cache flushes supported :<6>hde: cache flushes supported :<6> hde: unknown partition table ::::::::::X_RAID_SYNC_FORCE X_RAID: recovery thread got woken up ... New = 1, source drives = 3, current/active=2/2 Prepare sync raid 1, source_image=3, sync=2, ready=1 Start sync:0, source_image=1/1, between 2 to 4096002 sata_hotplug: /sbin/hotplug xraid_sync_started hdeUser mode helper start. done do_sata_hotplug :<6>hdc: cache flushes supported :<6>hde: cache flushes supported ::::chn=0, statu/LP_S=0x(d0/d050)29, 1 chn=0, statu/LP_S=0x(d0/d050)29, 4 chn=0, statu/LP_S=0x(d0/d050)29, 1 chn=0, statu/LP_S=0x(d0/d050)29, 1 chn=0, statu/LP_S=0x(d0/d050)29, 4 chn=0, statu/LP_S=0x(d0/d050)29, 4 chn=0, statu/LP_S=0x(d0/d050)29, 4 Sync:1, source_image=1/1, between 2 to 4096002,all_tgt=3
***** File system check performed at Wed Jun 15 22:26:47 CEST 2011 ***** fsck 1.40.11 (17-June-2008) e2fsck 1.40.11 (17-June-2008) c was not cleanly unmounted, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information c: 321103/45744128 files (2.3% non-contiguous), 36728413/91424768 blocks
***** File system check performed at Wed Jun 15 23:17:17 CEST 2011 ***** fsck 1.40.11 (17-June-2008) e2fsck 1.40.11 (17-June-2008) /dev/c/c is mounted. e2fsck: Cannot continue, aborting.
The NAS should be shutdown via Frontview so that services can be turned off properly and in the right order etc. as part of the shutdown process.
Edit: I did suggest "/etc/init.d/reboot" for rebooting before, but then changed my mind and removed it from my post. It seems for chirpa's post below referring to how to simply shutdown that this would work.
Thanks for your comments. They made me think on this painful subject. Tried all the above, and does not change anything. Manually or via Frontview. I still don't get what's going on. I realized also some strange things: - the frontview pretends I'm using 1395GB of the 1395GB - appleShare protocol says I'm using 886GB on the 1.49TB - df on the server shows a single /dev/hdc1 where 1.5GB are used on the 1.9GB available
To be honest, I don't feel super secure with the information I see, even though nothing really mean happened so far. Do you guys have the same disk filling information ?
