search for: bank0

I would like to pick the brains of the ZFS experts on this list: What would you do next to try and recover this zfs pool? I have a ZFS RAIDZ1 pool named bank0 that I cannot import. It was composed of 4 1.5 TiB disks. One disk is totally dead. Another had SMART errors, but using GNU ddrescue I was able to copy all the data off successfully. I have copied all 3 remaining disks as images using dd on to another another filesystem. Using the loopback fil...

I started to receive this kind of messages a few days ago on one of my servers: Message from syslogd@ at Mon Apr 29 08:02:55 2013 ... server1 kernel: EDAC MC0: UE row 0, channel-a= 0 channel-b= 1 labels "-": (Branch=0 DRAM-Bank=0 RDWR=Read RAS=0 CAS=0, UE Err=0x2 (Aliased Uncorrectable Non-Mirrored Demand Data ECC)) I've never had ECC memory to fail on me before, so now I am

...rved:58; + }; +}; + +struct mapped_regs { + union vac vac; + union vdc vdc; + unsigned long virt_env_vaddr; + unsigned long reserved1[29]; + unsigned long vhpi; + unsigned long reserved2[95]; + union { + unsigned long vgr[16]; + unsigned long bank1_regs[16]; /* bank1 regs (r16-r31) + when bank0 active */ + }; + union { + unsigned long vbgr[16]; + unsigned long bank0_regs[16]; /* bank0 regs (r16-r31) + when bank1 active */ + }; + unsigned long vnat; + unsigned long vbnat; + unsigned long vcpuid[5]; + unsigned long reserved3[11]; + unsigned long vpsr; + unsigned long vpr; + unsign...

...rved:58; + }; +}; + +struct mapped_regs { + union vac vac; + union vdc vdc; + unsigned long virt_env_vaddr; + unsigned long reserved1[29]; + unsigned long vhpi; + unsigned long reserved2[95]; + union { + unsigned long vgr[16]; + unsigned long bank1_regs[16]; /* bank1 regs (r16-r31) + when bank0 active */ + }; + union { + unsigned long vbgr[16]; + unsigned long bank0_regs[16]; /* bank0 regs (r16-r31) + when bank1 active */ + }; + unsigned long vnat; + unsigned long vbnat; + unsigned long vcpuid[5]; + unsigned long reserved3[11]; + unsigned long vpsr; + unsigned long vpr; + unsign...

Hi, I'm wondering if there's a method for doing any of these 1. Check what's the physical memory available. free -m shows ~768 mem but I was sure that I had 1G of memory in there. 2. I check the kernel and it seems like the 4G split is in effect so it should map / correctly recognise there's 1G of Mem there. Is there any way to check besides opening up the machine to look at it

Initially out there as #965245. I strongly prefer to build ARM64 packages on non-ARM systems. Something about my main build machine having twice the cores and twice the clock speed. As such after many builds I've managed to generate a set of patches which appear to mostly function to get functioning cross-builds of Xen. These are NOT a 100% solution. Some packaging hacks were needed. In

...------------------------ Intel(R) Pentium(R) Dual CPU E2160 @ 1.80GHz CPU 1 ==== Memory Device Sockets ================================ Type Status Set Device Locator Bank Locator ----------- ------ --- ------------------- ---------------- unknown empty 0 DIMM1 BANK0 unknown empty 0 DIMM2 BANK1 unknown empty 0 DIMM3 BANK2 SDRAM in use 0 DIMM4 BANK3 ==== On-Board Devices ===================================== To Be Filled By O.E.M. ==== Upgradeable Slots ==================================== ID...

...D1 CPU 1 CPU 2 ==== Memory Device Sockets ================================ Type Status Set Device Locator Bank Locator ----------- ------ --- ------------------- ---------------- Unknown in use 0 P1_DIMM1B BANK0 Unknown in use 0 P1_DIMM1A BANK1 Unknown in use 0 P1_DIMM2B BANK2 Unknown in use 0 P1_DIMM2A BANK3 Unknown in use 0 P1_DIMM3B BANK4 Unknown in use 0 P1_DIMM3A BANK5 Unknown in use 0 P1_DIMM4B BANK6 Unkno...

...re AMD Opteron(tm) Processor 270 CPU 1 Dual Core AMD Opteron(tm) Processor 270 CPU 2 ==== Memory Device Sockets ================================ Type Status Set Device Locator Bank Locator ------- ------ --- ------------------- -------------------- SDRAM in use 0 DIMM0 BANK0 SDRAM in use 0 DIMM1 BANK1 SDRAM in use 0 DIMM2 BANK2 SDRAM in use 0 DIMM3 BANK3 SDRAM in use 0 DIMM4 BANK4 SDRAM in use 0 DIMM5 BANK5 SDRAM in use 0 DIMM6 BANK6 SDRAM in use 0 DIMM7...

Is there a method to view the status of the rams ecc single or double bit errors? I would like to confirm that ecc on my xeon e5520 and ecc ram are performing their role since memtest is ambiguous. I am running memory test on a p6t6 ws, e5520 xeon, 2gb samsung ecc modules and this is what is on the screen: Chipset: Core IMC (ECC : Detect / Correct) However, further down "ECC" is

...768 MB Error Information Handle: Not Provided Number Of Devices: 3 Handle 0x001E, DMI type 17, 27 bytes Memory Device Array Handle: 0x001D Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: 1024 MB Form Factor: DIMM Set: None Locator: A0 Bank Locator: Bank0/1 Type: Unknown Type Detail: None Speed: Unknown Manufacturer: None Serial Number: None Asset Tag: None Part Number: None Handle 0x001F, DMI type 17, 27 bytes Memory Device Array Handle: 0x001D Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: No Mod...

This is my first post here, and i hope it is ok that i posted in this thread. I have been doing a bit of reading on the solaris platforms, and seem to be inclined to try out the open solaris os or solaris 10. My only worry is that my lack of knowledge with the command line may make this difficult regarding trouble shooting. It seems fairly straighforward creating zpools etc, but maybe nexenta is

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions which is necessary to

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions which is necessary to

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. Please review and comments. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. Please review and comments. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was already merged to linux ia64 test branch. This patch is for linux ia64 test branch. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor.

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was already merged to linux ia64 test branch. This patch is for linux ia64 test branch. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor.

...: 6 GB Physical Array Handle: 0x001E Partition Width: 0 Handle 0x0020, DMI type 17, 27 bytes Memory Device Array Handle: 0x001E Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 2048 MB Form Factor: DIMM Set: None Locator: PROC 1 DIMM 3A Bank Locator: BANK0 Type: <OUT OF SPEC> Type Detail: Synchronous Speed: 800 MHz (1.2 ns) Manufacturer: Kingston Serial Number: DBBF18D5 Asset Tag: AssetTagNum0 Part Number: 9965426-005.A00LF Handle 0x0021, DMI type 20, 19 bytes Memory Device Mapped Address Starting Address: 0x00000000000 Ending...

Hi. This patchset is ia64/xen domU patch take 8 which was updated following Tony's review. (Thank you very much, Tony.) This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. This patchset is for linux ia64 test branch and depends on some patches for xen common part I'll send separately. To compile, the changesets in x86/xen