[RAID1] Need some advice on setting up a second disk

Re: [RAID1] Need some advice on setting up a second disk

Postby Jocko » Tue Dec 22, 2015 6:13 pm

Yes it is safe and you need it as it fixes a bug in the not chrooted environment (so not linked with your version 16.1)
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: [RAID1] Need some advice on setting up a second disk

Postby danyboy666 » Tue Dec 22, 2015 7:01 pm

Jocko wrote:Yes it is safe and you need it as it fixes a bug in the not chrooted environment (so not linked with your version 16.1)


I've applied the patch but still same issue when rebooting with the front LED blinking. But after waiting for about 10 minutes the blinking does not occure anymore(front LED is completely shut down so does the HDD stauts LEDs) but i do not have acces to the NAS anymore. :/ just my luck i was in the process of moving stuff to it.

edit: I've regained acces to the NAS after unplugging from the sector. the fron LED light up Blue everything is back to normal for now i guess.
Last edited by danyboy666 on Tue Dec 22, 2015 7:10 pm, edited 1 time in total.
danyboy666
 
Posts: 22
Joined: Sun Dec 06, 2015 4:06 am

Re: [RAID1] Need some advice on setting up a second disk

Postby Jocko » Tue Dec 22, 2015 7:10 pm

but i do not have acces to the NAS anymore
This is not related with the patch...
Do you use fvdw-sl assistant to find the NAS ?

---edit---
the fron LED light up Blue everything is back to normal for now i guess.
Yes I assume but maybe you should end the process of moving.
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: [RAID1] Need some advice on setting up a second disk

Postby danyboy666 » Tue Dec 22, 2015 7:21 pm

Jocko wrote:
but i do not have acces to the NAS anymore
This is not related with the patch...
Do you use fvdw-sl assistant to find the NAS ?

---edit---
the fron LED light up Blue everything is back to normal for now i guess.
Yes I assume but maybe you should end the process of moving.


Yes this was a mistake but i needed to free up some space in one of my VM HDD. It's a temporary mesure since i did not have anymore 1TB HDD available. I have to install a NEW 4TB disk in my VM. Once i'm done I'll transfer back the stuff from the NAS and as a precautionary mesure. At least until we've ironed out the bugs.

I think the worst bug right now is when i try to reboot or shutdown the NAS. For some reasons i have to completely unplug it from the sector to be sure the reboot process is completed.
The other bug is the toggle switch in the back on the NAS. It does not respond at all. Also If i do not toggle it off when sending a shutdown command from the web interface the NAS will reboot instead of shuting down.

edit: yes I tried with the fvdw assistant. I've recovered the NAS once i've unplugged it from the sector though. They call this a "power cycle" hahaha. Geez i'm starting to hate this NAS.
danyboy666
 
Posts: 22
Joined: Sun Dec 06, 2015 4:06 am

Re: [RAID1] Need some advice on setting up a second disk

Postby Jocko » Tue Dec 22, 2015 7:34 pm

danyboy666 wrote:I think the worst bug right now is when i try to reboot or shutdown the NAS. For some reasons i have to completely unplug it from the sector to be sure the reboot process is completed.
The other bug is the toggle switch in the back on the NAS. It does not respond at all. Also If i do not toggle it off when sending a shutdown command from the web interface the NAS will reboot instead of shuting down.
It seems you don't have the common platform (64MB), so as shutdown command (and switchoff button) are set with the known platform, I think these binaries can not run properly.

So the first think to do it is to find information about this undocumented version...


---edit---
at least in 2009, RAM size was 128MB
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: [RAID1] Need some advice on setting up a second disk

Postby danyboy666 » Tue Dec 22, 2015 7:48 pm

Jocko wrote:
danyboy666 wrote:I think the worst bug right now is when i try to reboot or shutdown the NAS. For some reasons i have to completely unplug it from the sector to be sure the reboot process is completed.
The other bug is the toggle switch in the back on the NAS. It does not respond at all. Also If i do not toggle it off when sending a shutdown command from the web interface the NAS will reboot instead of shuting down.
It seems you don't have the common platform (64MB), so as shutdown command (and switchoff button) are set with the known platform, I think these binaries can not run properly.

So the first think to do it is to find information about this undocumented version...


---edit---
at least in 2009, RAM size was 128MB


I'll be able to give any information you guys need. I know for now how to recover it if anything happens.

For now you guys at least have a dmesg and initial boot.log. I won't be far if you guys need anything. Altough i won't expect any real fix for this now since were so close to the holidays. (Joyeuses Fêtes à la France de la part du Canada). Anywais I'm not doing anything the holidays btw so i'm always available if needed.
danyboy666
 
Posts: 22
Joined: Sun Dec 06, 2015 4:06 am

Re: [RAID1] Need some advice on setting up a second disk

Postby danyboy666 » Tue Dec 22, 2015 10:02 pm

Another issue with the NAS. It only transfer at 10Mb/s over my Gigabit network where i am usually able to reach speed close to 100Mb/s from my other samba shares. The WD disk have 7200 RPM do that is not an issue.

Another thing is i get the error "No space left on device" on random file transfer. I was able to transfer file which were over 2GB each but i get that error with file which are less than 1GB. This is becoming a real pain tbh i should have stuck with my external SATA 3.0.

Code: Select all
root@NAS-fvdwsl:/ # df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root               226.2M    148.3M     65.4M  69% /
/dev/sda2               226.2M    148.3M     65.4M  69% /
/dev/sda5               786.9M      1.2M    777.6M   0% /rw_fs
tmpfs                     4.9M    704.0K      4.2M  14% /rw_fs/tmp/usr/var
/dev/md0                913.7G     40.7G    863.7G   4% /share/1100
/dev/root               226.2M    167.9M     45.7M  79% /lacie-boot
root@NAS-fvdwsl:/ # hdparm -tT /dev/sda

/dev/sda:
 Timing cached reads:   244 MB in  2.00 seconds = 121.74 MB/sec
 Timing buffered disk reads:  158 MB in  3.03 seconds =  52.15 MB/sec
root@NAS-fvdwsl:/ # hdparm -tT /dev/md0

/dev/md0:
 Timing cached reads:   242 MB in  2.01 seconds = 120.69 MB/sec
 Timing buffered disk reads:  128 MB in  3.02 seconds =  42.39 MB/sec


and yet network speed is equivalent to 100Mbps network.

http://imgur.com/QCU2cTy

Vmware-pfLAN is the vm on which the NAS is mounted

fstab from my VM share:

Code: Select all
//192.168.121.85/fvdw      /mnt/fvdw   cifs           guest,uid=nobody,gid=nogroup,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0


The HDD on the vm is

Code: Select all
UUID=531b311c-4657-446b-b0b5-30a51ea59d05     /samba/anonymous/user          ext4  defaults 0 0


Transfer are made directly from the vm on the mount. I'm not using my windows PC in this case altough i have the same issue when trying to transfer rom my win PC to the NAS.

Anywais i have the same setup for every share on my network and all of them are able to achieve about 100Mb/s speed over samba on my local network. Even my older Atom is able to reach 100Mb/s on my Gigabit network. To give you an idea i'm able to watch full HD content mounted over samba without any speed issues whatsoever.

I'm really doubting this NAS after checking some other post on the internet there are at least two full google pages of network issues related to LaCie. What a crap this turned out to be. I'm kind of hoping this is a kernel issue but i really doubt it. I'll give it another try and debug this but the more I think of this and the more I think I'll recover my files from the NAS and put it where it belongs. In the recycle bin. I gave it all the chances it deserves.

edit: The network speed seem to be improving (I,m currently at around 20Mb/s) after playing with cifs mount options but i'm still getting that "No space left on device" error. Using cp instead of mv down not change a thing.
danyboy666
 
Posts: 22
Joined: Sun Dec 06, 2015 4:06 am

Re: [RAID1] Need some advice on setting up a second disk

Postby danyboy666 » Wed Dec 23, 2015 1:10 am

You were right i shoudn't have use it at all to transfer stuff to it.

Code: Select all
[2015/12/22 20:01:36, 0] smbd/reply.c:send_file_readX(2614)
  send_file_readX: sendfile failed for file temp/blahblah.iso. Terminating
[2015/12/22 20:01:36, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.121.101. Error Broken pipe
[2015/12/22 20:01:36, 0] lib/util_sock.c:send_smb(761)
  Error writing 75 bytes to client. -1. (Broken pipe)


I can't even retreive my content now ffs. Going to unplug one disk and mount it on a linux box to get my stuff back.

What a journey this has been. Thanks for all but i'm good this nas is nothing but trouble and trying to use an alternate fw just worsten its case.

Here's a breakdown so far for what's goign wrong with this:

can't use official crappy software from lacie
can't power down properly
can't transfer files to it
can't retreive files from it (lets at least hope i can mount the freaking md device on another unix box)
can't use network at full speed
can't set clock???

This box will meet my sledge hammer real soon trust me i've been patient enough with it.

Thanks for your support.
danyboy666
 
Posts: 22
Joined: Sun Dec 06, 2015 4:06 am

Re: [RAID1] Need some advice on setting up a second disk

Postby Jocko » Wed Dec 23, 2015 9:56 am

Hi danyboy666,

danyboy666 wrote:[2015/12/22 20:01:36, 0] smbd/reply.c:send_file_readX(2614)
send_file_readX: sendfile failed for file temp/blahblah.iso. Terminating
[2015/12/22 20:01:36, 0] lib/util_sock.c:write_data(562)
write_data: write failure in writing to client 192.168.121.101. Error Broken pipe
[2015/12/22 20:01:36, 0] lib/util_sock.c:send_smb(761)
Error writing 75 bytes to client. -1. (Broken pipe)
hahaaa, that confirms that 2big1 do not support sendfile. So you can try to install this patch which disable this support on samba server. viewtopic.php?f=29&t=2377&p=21186#p21186

Code: Select all
can't set clock???
Just use the Internet clock option in the main setup menu
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: [RAID1] Need some advice on setting up a second disk

Postby fvdw » Wed Dec 23, 2015 1:08 pm

In the meantime I got a reply from another user (Uelpenich) with a 2big1 running the same kernel.
This is his dmesg output, pretty similar with your but with difference that yours has 128MB ram and rtc doesn't work.
The rtc works ok on Uelpenich's box.

I could nowhere find that a 2big1 has 128 MB of ram, so either yours is modified, or your isn't a 2big1, can you post pictures of the exterior look and if possible from the main board.

PS About the rtc , if it is a 2big1 I think your rtc must be broken, but as said this 128MB ram is strange..
The fact that this kernel runs on it doesn't mean it is a 2big1, it has the same cpu and therefor this kernel might run but could need a different setup file used when compiling the kernel (for instance for the rtc)



Code: Select all
~ # dmesg (Uelpenich 2big1)
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.2 (root@fvdwsl-5big2.local) (gcc version 4.8.1 (GCC) ) #6 Sat Nov 29 22:15:32 CET 2014
[    0.000000] CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: LaCie 2Big Network
[    0.000000] Clearing invalid memory bank 0KB@0xffffffff
[    0.000000] Clearing invalid memory bank 0KB@0xffffffff
[    0.000000] Clearing invalid memory bank 0KB@0xffffffff
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x41000403
[    0.000000] Memory policy: Data cache writeback
[    0.000000] On node 0 totalpages: 16384
[    0.000000] free_area_init_node: node 0, pgdat c03f0934, node_mem_map c3f7b000
[    0.000000]   Normal zone: 128 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 16384 pages, LIFO batch:3
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda7 ro reset=0
[    0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
[    0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Memory: 60688K/65536K available (2863K kernel code, 158K rwdata, 852K rodata, 125K init, 206K bss, 4848K reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xc4800000 - 0xff000000   ( 936 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc4000000   (  64 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc03a8fec   (3716 kB)
[    0.000000]       .init : 0xc03a9000 - 0xc03c862c   ( 126 kB)
[    0.000000]       .data : 0xc03ca000 - 0xc03f1ac0   ( 159 kB)
[    0.000000]        .bss : 0xc03f1ac0 - 0xc0425680   ( 207 kB)
[    0.000000] NR_IRQS:64
[    0.000023] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 25769803770ns
[    8.411848] Console: colour dummy device 80x30
[    8.411898] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
[    8.481478] pid_max: default: 32768 minimum: 301
[    8.481760] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    8.481797] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    8.482951] CPU: Testing write buffer coherency: ok
[    8.483620] Setting up static identity map for 0x2d1678 - 0x2d16b4
[    8.488267] VFP support v0.3: not present
[    8.489514] NET: Registered protocol family 16
[    8.490647] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    8.495168] Orion ID: MV88F5182-A2. TCLK=166666667.
[    8.496164] initial MPP regs: 00000003 55000000 03ff0000
[    8.496221]   final MPP regs: 00000003 55000000 03ff5555
[    8.501627] net2big: Flash writing is not yet supported.
[    8.546655] bio: create slab <bio-0> at 0
[    8.548447] vgaarb: loaded
[    8.550280] SCSI subsystem initialized
[    8.551622] libata version 3.00 loaded.
[    8.554202] usbcore: registered new interface driver usbfs
[    8.554718] usbcore: registered new interface driver hub
[    8.555305] usbcore: registered new device driver usb
[    8.559665] Switched to clocksource orion_clocksource
[    8.599913] NET: Registered protocol family 2
[    8.601300] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    8.601376] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    8.601483] TCP: Hash tables configured (established 1024 bind 1024)
[    8.601637] TCP: reno registered
[    8.601680] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    8.601743] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    8.602151] NET: Registered protocol family 1
[    8.602234] PCI: CLS 0 bytes, default 32
[    8.605906] futex hash table entries: 256 (order: -1, 3072 bytes)
[    8.607142] VFS: Disk quotas dquot_6.5.2
[    8.607283] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    8.607605] msgmni has been set to 118
[    8.611388] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    8.611466] io scheduler noop registered
[    8.611491] io scheduler deadline registered
[    8.611560] io scheduler cfq registered (default)
[    8.612144] mv_xor mv_xor.0: Marvell shared XOR driver
[    8.651551] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[    8.691553] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[    8.708205] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    8.730866] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3, base_baud = 10416666) is a 16550A
[    9.122871] console [ttyS0] enabled
[    9.152970] brd: module loaded
[    9.168958] loop: module loaded
[    9.172980] Uniform Multi-Platform E-IDE driver
[    9.178354] ide-gd driver 1.18
[    9.183901] sata_mv sata_mv.0: version 1.28
[    9.184071] sata_mv sata_mv.0: cannot get optional clkdev
[    9.190402] sata_mv sata_mv.0: slots 32 ports 2
[    9.204811] scsi0 : sata_mv
[    9.209168] scsi1 : sata_mv
[    9.213177] ata1: SATA max UDMA/133 irq 29
[    9.217283] ata2: SATA max UDMA/133 irq 29
[    9.222739] tun: Universal TUN/TAP device driver, 1.6
[    9.227790] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    9.234524] ipddp.c:v0.01 8/28/97 Bradford W. Johnson <johns393@maroon.tc.umn.edu>
[    9.244048] ipddp0: Appletalk-IP Encap. mode by Bradford W. Johnson <johns393@maroon.tc.umn.edu>
[    9.261076] libphy: orion_mdio_bus: probed
[    9.265747] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    9.354542] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:d0:4b:84:39:ef
[    9.366555] aoe: cannot create debugfs directory
[    9.371524] aoe: AoE v85 initialised.
[    9.375823] mousedev: PS/2 mouse device common for all mice
[    9.382692] i2c /dev entries driver
[    9.392044] rtc-rs5c372 0-0032: rs5c372b found, 24hr, driver version 0.6
[    9.404160] rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
[    9.413107] at24 0-0050: 1024 byte 24c08 EEPROM, writable, 1 bytes/write
[    9.428416] Netfilter messages via NETLINK v0.30.
[    9.433727] ipip: IPv4 over IPv4 tunneling driver
[    9.440398] TCP: cubic registered
[    9.443772] NET: Registered protocol family 17
[    9.448245] NET: Registered protocol family 5
[    9.455104] console [netcon0] enabled
[    9.458770] netconsole: network logging started
[    9.464969] rtc-rs5c372 0-0032: setting system clock to 2015-10-18 22:18:14 UTC (1445206694)
[    9.731497] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    9.771552] ata1.00: ATA-8: TOSHIBA DT01ACA200, MX4OABB0, max UDMA/133
[    9.778075] ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    9.841574] ata1.00: configured for UDMA/133
[    9.846577] scsi 0:0:0:0: Direct-Access     ATA      TOSHIBA DT01ACA2 MX4O PQ: 0 ANSI: 5
[    9.856016] fvdw1 disk index before get_sd_name = 0
[    9.860887] device-name= sata_mv
[    9.864153] fvdw2 disk index after get_sd_name = 1
[    9.868938] fvdw3 prefix[0]=s  prefix[1]=d
[    9.873049] fvdw4 diskname = sdb
[    9.877592] sd 0:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[    9.885380] sd 0:0:0:0: [sdb] 4096-byte physical blocks
[    9.893124] sd 0:0:0:0: [sdb] Write Protect is off
[    9.897937] sd 0:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    9.898352] sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    9.950725]  sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 >
[    9.964440] sd 0:0:0:0: [sdb] Attached SCSI disk
[   10.401493] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   10.441552] ata2.00: ATA-8: ST2000DM001-9YN164, CC4G, max UDMA/133
[   10.447736] ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   10.511576] ata2.00: configured for UDMA/133
[   10.516554] scsi 1:0:0:0: Direct-Access     ATA      ST2000DM001-9YN1 CC4G PQ: 0 ANSI: 5
[   10.526012] fvdw1 disk index before get_sd_name = 1
[   10.530884] device-name= sata_mv
[   10.534148] fvdw2 disk index after get_sd_name = 0
[   10.538927] fvdw3 prefix[0]=s  prefix[1]=d
[   10.543039] fvdw4 diskname = sda
[   10.547592] sd 1:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[   10.555376] sd 1:0:0:0: [sda] 4096-byte physical blocks
[   10.562436] sd 1:0:0:0: [sda] Write Protect is off
[   10.567243] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   10.567655] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   10.623070]  sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
[   10.636924] sd 1:0:0:0: [sda] Attached SCSI disk
[   10.665452] kjournald starting.  Commit interval 5 seconds
[   10.670990] EXT3-fs (sda7): mounted filesystem with ordered data mode
[   10.677512] VFS: Mounted root (ext3 filesystem) readonly on device 8:23.
[   10.685185] Freeing unused kernel memory: 124K (c03a9000 - c03c8000)
[   10.973220] EXT3-fs (sda7): warning: maximal mount count reached, running e2fsck is recommended
[   10.982389] EXT3-fs (sda7): using internal journal
[   12.091771] kjournald starting.  Commit interval 5 seconds
[   12.097319] EXT3-fs (sda1): warning: checktime reached, running e2fsck is recommended
[   12.105584] EXT3-fs (sda1): using internal journal
[   12.141635] EXT3-fs (sda1): recovery complete
[   12.145998] EXT3-fs (sda1): mounted filesystem with ordered data mode
[   14.391773] kjournald starting.  Commit interval 5 seconds
[   14.397761] EXT3-fs (sda5): using internal journal
[   14.421630] EXT3-fs (sda5): recovery complete
[   14.425991] EXT3-fs (sda5): mounted filesystem with ordered data mode
[   14.599544] random: nonblocking pool is initialized
[   14.678024] Adding 524284k swap on /dev/sda3.  Priority:-1 extents:1 across:524284k
[   14.819377] NET: Registered protocol family 10
[   17.543023] NTFS driver 2.1.30 [Flags: R/W MODULE].
[   17.602026] fuse init (API version 7.22)
[   17.656800] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   17.664989] ehci-orion: EHCI orion driver
[   17.669163] orion-ehci orion-ehci.0: EHCI Host Controller
[   17.674675] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   17.682595] orion-ehci orion-ehci.0: irq 17, io mem 0xf1050000
[   17.701484] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   17.709000] hub 1-0:1.0: USB hub found
[   17.712909] hub 1-0:1.0: 1 port detected
[   17.717592] orion-ehci orion-ehci.1: EHCI Host Controller
[   17.723086] orion-ehci orion-ehci.1: new USB bus registered, assigned bus number 2
[   17.730974] orion-ehci orion-ehci.1: irq 12, io mem 0xf10a0000
[   17.751485] orion-ehci orion-ehci.1: USB 2.0 started, EHCI 1.00
[   17.758895] hub 2-0:1.0: USB hub found
[   17.762781] hub 2-0:1.0: 1 port detected
[   17.821559] usbcore: registered new interface driver usb-storage
[   17.875248] usbcore: registered new interface driver usblp
[   17.950299] RPC: Registered named UNIX socket transport module.
[   17.956257] RPC: Registered udp transport module.
[   17.960954] RPC: Registered tcp transport module.
[   17.965674] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   18.061811] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   18.124980] Loading iSCSI transport class v2.0-870.
[   18.146856] iscsi: registered transport (tcp)
[   18.208549] Linux video capture interface: v2.00
[   18.328021] uvcvideo: Unable to create debugfs directory
[   18.333643] usbcore: registered new interface driver uvcvideo
[   18.339376] USB Video Class driver (1.1.1)
[   18.465061] md: raid0 personality registered for level 0
[   18.520157] md: raid1 personality registered for level 1
[   18.742122] raid6: int32x1     19 MB/s
[   18.912971] raid6: int32x2     29 MB/s
[   19.081893] raid6: int32x4     30 MB/s
[   19.252936] raid6: int32x8     36 MB/s
[   19.256689] raid6: using algorithm int32x8 (36 MB/s)
[   19.261681] raid6: using intx1 recovery algorithm
[   19.273520] async_tx: api initialized (async)
[   19.280846] xor: measuring software checksum speed
[   19.381470]    arm4regs  :   308.800 MB/sec
[   19.481462]    8regs     :   206.800 MB/sec
[   19.581455]    32regs    :   263.200 MB/sec
[   19.585635] xor: using function: arm4regs (308.800 MB/sec)
[   19.617755] md: raid6 personality registered for level 6
[   19.623118] md: raid5 personality registered for level 5
[   19.628424] md: raid4 personality registered for level 4
[   19.685627] md: raid10 personality registered for level 10
[   32.602990] udevd (717): /proc/717/oom_adj is deprecated, please use /proc/717/oom_score_adj instead.
[   32.612443] udev: starting version 130
[   42.277672] md: bind<sdb8>
[   42.281127] md: bind<sda8>
[   42.365458] md/raid1:md0: active with 2 out of 2 mirrors
[   42.371048] md0: detected capacity change from 0 to 1997430849536
[   42.387451]  md0: unknown partition table
[   51.841958] kjournald starting.  Commit interval 5 seconds
[   51.871357] EXT3-fs (md0): using internal journal
[   51.931652] EXT3-fs (md0): recovery complete
[   51.935929] EXT3-fs (md0): mounted filesystem with ordered data mode
[   53.862652] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   56.733227] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[   56.743136] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
~ #
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

PreviousNext

Return to Lacie 2Big Network vs1

Who is online

Users browsing this forum: No registered users and 8 guests