Z10 Autoloader failed/blocked, Device Bricked (110 Flash Pattern)

Duplicate:http://supportforums.blackberry.com/t5/BlackBerry-10-OS-Device-Software/Blink-Blink-Pause-Flashing-Red-Light-Autoloader-failed-blocked/m-p/3120514/highlight/false#M17049

Hello Everyone, Yesterday i began having issues with my z10. I had just updated to the recent OS and 5 minutes after turning on my z10 none of my apps would open (they would simply launch than close right away). I read a few CB forum posts and apparently this was a fairly common issue solved by performing a factory reset. So I connected my z10 to link and although the device was detected under "devices" the window read: "Can't communicate with device [Reconnect] or [Reload]" As suggested I took the reload option and a security wipe started. Sometime during the wipe something happened and the device stopped wiping and reloading. Now the device booted up displaying the error message "www.bberror.com/bb10-0015". I followed this error message to the KB and read through the steps to resolve. Again the suggestion was reloading the device. I attempted to power off the device as suggested (although it would simply boot back up to the bberror screen), and reload the device. I tried through the devices window and than through the preferences window (usually whats used when the device won't detect). Neither worked and I got "An error has occurred while updating your device's software. Unspecified error encountered [A:0x000000A2] ". So googling the error message I no longer found official blackberry help and went to forum solutions which suggested I download an use the autoloader command line.
https://supportforums.blackberry.com/t5/BlackBerry-10-OS-Device-Software/Upgrading-OS10-devices-usin... I attempted to download the file although it was being bottle necked by the server and going painfully slow. So a quick google search found an official BB site with autoloaders:http://developer.blackberry.com/blackberry10devalpha/allautoloaders.html I downloaded the most recent stable one (10.3.1) and after a few hours was ready to start. I tried again to power off the device (no luck - just reboots and says error message), and then plugged it into my PC. At first the autoloader just kept saying connecting to bootrom for about an hour so i closed it and removed the battery from the device.I launched the autoloader again and when "connecting to bootrom" came up I plugged in the device USB. A bunch of USB port "in" and "out" noises occured and the autoloader when to work. My device no longer displayed the error message and LED was a solid green. When the autoloader finished I managed to capture a screenshot of it saying "OS blocked". The device than began the flashing pattern "Blink, Blink, Pause" then the cycle begins again. I figured I'd try it again and did so about 8 times - battery in, battery out, different USB ports, different computers, different usb cables. still no luck. So I left it charging as someone suggested on another forum post for about 6hrs in hopes of something happening.nothing. I am now sitting on a bricked device with the Blink Blink pause flashing cycle and am not sure what my next moves are. Thank you for taking the time to read my issues and I would greatly appreciate ANY suggestions you might have to revive my z10 ! <img>http://i.imgur.com/CJbkxnT.png</img>

Similar Messages

Blink Blink Pause Flashing Red Light, Autoloader failed/blocked for this Device Z10.

Hello Everyone, Yesterday i began having issues with my z10. I had just updated to the recent OS and 5 minutes after turning on my z10 none of my apps would open (they would simply launch than close right away). I read a few CB forum posts and apparently this was a fairly common issue solved by performing a factory reset. So I connected my z10 to link and although the device was detected under "devices" the window read: "Can't communicate with device [Reconnect] or [Reload]" As suggested I took the reload option and a security wipe started. Sometime during the wipe something happened and the device stopped wiping and reloading. Now the device booted up displaying the error message "www.bberror.com/bb10-0015". I followed this error message to the KB and read through the steps to resolve. Again the suggestion was reloading the device. I attempted to power off the device as suggested (although it would simply boot back up to the bberror screen), and reload the device. I tried through the devices window and than through the preferences window (usually whats used when the device won't detect). Neither worked and I got "An error has occurred while updating your device's software. Unspecified error encountered [A:0x000000A2] ". So googling the error message I no longer found official blackberry help and went to forum solutions which suggested I download an use the autoloader command line.
https://supportforums.blackberry.com/t5/BlackBerry-10-OS-Device-Software/Upgrading-OS10-devices-using-Autoloader/td-p/2466747 I attempted to download the file although it was being bottle necked by the server and going painfully slow. So a quick google search found an official BB site with autoloaders:http://developer.blackberry.com/blackberry10devalpha/allautoloaders.html I downloaded the most recent stable one (10.3.1) and after a few hours was ready to start. I tried again to power off the device (no luck - just reboots and says error message), and then plugged it into my PC. At first the autoloader just kept saying connecting to bootrom for about an hour so i closed it and removed the battery from the device.I launched the autoloader again and when "connecting to bootrom" came up I plugged in the device USB. A bunch of USB port "in" and "out" noises occured and the autoloader when to work. My device no longer displayed the error message and LED was a solid green. When the autoloader finished I managed to capture a screenshot of it saying "OS blocked". The device than began the flashing pattern "Blink, Blink, Pause" then the cycle begins again. I figured I'd try it again and did so about 8 times - battery in, battery out, different USB ports, different computers, different usb cables. still no luck. So I left it charging as someone suggested on another forum post for about 6hrs in hopes of something happening.nothing. I am now sitting on a bricked device with the Blink Blink pause flashing cycle and am not sure what my next moves are. Thank you for taking the time to read my issues and I would greatly appreciate ANY suggestions you might have to revive my z10 ! [img]http://i.imgur.com/CJbkxnT.png[/img]

Hello, Try again please... smoez1 wrote:
I attempted to download the file although it was being bottle necked by the server and going painfully slow. So a quick google search found an official BB site with autoloaders:http://developer.blackberry.com/blackberry10devalpha/allautoloaders.html
Never never never use those. Those are, as the link says, for developers...which means they are typically crippled one way or another. They are official only for developers, not ever for end users. Instead, clever users have created AutoLoaders from the fully functioning BB code...here is a useful archive:http://forums.crackberry.com/bb10-leaked-beta-os-f395/bb10-os-archive-943672/Give it another try. Also...smoez1 wrote:
When the autoloader finished I managed to capture a screenshot of it saying "OS blocked". The device than began the flashing pattern "Blink, Blink, Pause" then the cycle begins again. I figured I'd try it again and did so about 8 times - battery in, battery out, different USB ports, different computers, different usb cables. still no luck. So I left it charging as someone suggested on another forum post for about 6hrs in hopes of something happening.nothing. I am now sitting on a bricked device with the Blink Blink pause flashing cycle and am not sure what my next moves are. Thank you for taking the time to read my issues and I would greatly appreciate ANY suggestions you might have to revive my z10 ! [img]http://i.imgur.com/CJbkxnT.png[/img]Given that, it is likely your device already had 10.3.2 installed on it...which means you cannot go back to 10.3.1 or earlier. 10.3.2 contains the implementation of the government required "kill switch" anti-theft feature, which mandates that this new feature not be able to be bypassed...falling back to an older OS would eliminate the feature, thereby bypassing what the law now requires. So, if you were on 10.3.2, you cannot go back, and must use only a 10.3.2 AutoLoader. Good luck!

2.6.21.rt8 - failed to parse block device

Hi there!
I need an rt-kernel for some audio production and was told 2.6.21.rt8 should work (there are, apparently, a lot of problems with the newer ones). I picked up the package from one of the repos for Arch ProAudio http://arch.madfire.net/proaudio/i686/ and installed it without any problems.
However, upon booting I run into the "failed to parse block device"-error. I realize quite a few people have had this error for one reason or the other. I have, of course, tried a lot of the solutions mentioned in the forum already but as I'm quite new to this I'm not quite sure of what might be causing the problem. My kernel for everyday-work is 2.6.28-ARCH which works perfectly but has too low a system timer resolution etc. for audio production.
Please let me know what conf's to post.
Any help would be greatly appreciated.
Cheers!

Note: Probably better to open up a new topic on this Ineluki and describe the details as best as you can.
http://wiki.archlinux.org/index.php/For … Bumping.27

Lucreate fails with: Root slice device ... for BE ... is not a block device

Hi,
I'm running lucreate on a Sol10u7 x86 system as I wanted to get it to u8 level. I installed:
SUNWlucfg
SUNWlur
SUNWluu
from u8 and then a patch: 121431-58
System is not zoned and it is on ZFS with following pools:
pool: rpool
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
c1t0d0s0 ONLINE 0 0 0
errors: No known data errors
pool: spool
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
spool ONLINE 0 0 0
c0t0d0 ONLINE 0 0 0
This is what happens:
Creating Alternative Boot Environment..
lucreate -n s10x_u8
Checking GRUB menu...
Analyzing system configuration.
No name for current boot environment.
INFORMATION: The current boot environment is not named - assigning name <s10x_u7wos_08>.
Current boot environment is named <s10x_u7wos_08>.
Creating initial configuration for primary boot environment <s10x_u7wos_08>.
The device </dev/dsk/c1t0d0s0> is not a root device for any boot environment; cannot get BE ID.
PBE configuration successful: PBE name <s10x_u7wos_08> PBE Boot Device </dev/dsk/c1t0d0s0>.
Comparing source boot environment <s10x_u7wos_08> file systems with the
file system(s) you specified for the new boot environment. Determining
which file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
Creating configuration for boot environment <s10x_u8>.
Source boot environment is <s10x_u7wos_08>.
Creating boot environment <s10x_u8>.
Cloning file systems from boot environment <s10x_u7wos_08> to create boot environment <s10x_u8>.
Creating snapshot for <rpool/ROOT/s10x_u7wos_08> on <rpool/ROOT/s10x_u7wos_08@s10x_u8>.
Creating clone for <rpool/ROOT/s10x_u7wos_08@s10x_u8> on <rpool/ROOT/s10x_u8>.
Setting canmount=noauto for </> in zone <global> on <rpool/ROOT/s10x_u8>.
Creating snapshot for <rpool/ROOT/s10x_u7wos_08/var> on <rpool/ROOT/s10x_u7wos_08/var@s10x_u8>.
Creating clone for <rpool/ROOT/s10x_u7wos_08/var@s10x_u8> on <rpool/ROOT/s10x_u8/var>.
Setting canmount=noauto for </var> in zone <global> on <rpool/ROOT/s10x_u8/var>.
ERROR: Root slice device </dev/dsk/c1t0d0s0> for BE <s10x_u8> is not a block device: .
ERROR: Cannot make file systems for boot environment <s10x_u8>.
Please help,
Cheers,
Tom

devfsadm fixed the issue,

SRW248G4 Problem: failed reading device id on device 0

I have a SRW248G4 that crashed, and now is continually booting. Any ideas? Preparing to decompress... 100% Decompressing SW from flash 100% OK Running from RAM... ******************************************************************* *** Running SW Ver. 1.2.1b Date 31-Aug-2006 Time 13:47:21 *** ******************************************************************* HW version is 00.03.00 Base Mac address is: 00:1a:70:2b:de:5e Dram size is : 32M bytes Dram first block size is : 16969K bytes Dram first PTR is : 0xF6D840 Flash size is: 8M 01-Jan-2000 01:01:02 %CDB-I-LOADCONFIG: Loading startup configuration. 01-Jan-2000 01:01:04 %ERHG-F-SEND: BOXP_perform_smi_scan_of_devices_in_slot - failed reading device id on device 0 ***** FATAL ERROR ***** Reporting Task: ROOT. Software Version: 1.2.1b (date 31-Aug-2006 time 13:47:21) ------ Performing the Power-On Self Test (POST) ------ UART Channel Loopback Test........................PASS Testing the System SDRAM..........................PASS Boot1 Checksum Test...............................PASS Boot2 Checksum Test...............................PASS Flash Image Validation Test.......................PASS BOOT Software Version 1.0.2 Built 17-Aug-2006 14:55:46 ::: ::: ::: ::: ::: ::: ::::: :::::::::: ::: ::: :::::::::: ::: ::: ::::: ::: ::: ::::: :::: ::: :::: :::: :::: ::: ::: ::: ::: ::: ::: :::::::: :::: :::::::: :::: ::: ::: ::: :: ::: :::::::::: :::::::::: :::: :::::::::: ::: ::: ::: :::::: ::: :::: ::: :::: ::: :::::::::: ::: ::: :::: ::: :::: :::......::: :::: :::......::: ......... ... ... ... ... .... .......... .... .......... Linksys SmartSwitch based on 88E6218 with ARM946E-S. 32MByte SDRAM. I-Cache 8 KB. D-Cache 8 KB. Cache Enabled. Autoboot in 2 seconds - press RETURN or Esc. to abort and enter prom. [2J Startup Menu [1] Download Software [2] Erase Flash File [3] Password Recovery Procedure [4] Enter Diagnostic Mode [5] Set Terminal Baud-Rate [6] Back Enter your choice or press 'ESC' to exit: The diagnostic will be activated after the system startup. ==== Press Enter To Continue ==== [2J Startup Menu [1] Download Software [2] Erase Flash File [3] Password Recovery Procedure [4] Enter Diagnostic Mode [5] Set Terminal Baud-Rate [6] Back Enter your choice or press 'ESC' to exit: [2J Exit from boot menu. Continue with flow. Preparing to decompress... 100% Decompressing SW from flash 100% OK Running from RAM... ******************************************************************* *** Running SW Ver. 1.2.1b Date 31-Aug-2006 Time 13:47:21 *** ******************************************************************* HW version is 00.03.00 Base Mac address is: 00:1a:70:2b:de:5e Dram size is : 32M bytes Dram first block size is : 16969K bytes Dram first PTR is : 0xF6D840 Flash size is: 8M 01-Jan-2000 01:01:02 %CDB-I-LOADCONFIG: Loading startup configuration. 01-Jan-2000 01:01:04 %ERHG-F-SEND: BOXP_perform_smi_scan_of_devices_in_slot - failed reading device id on device 0 ***** FATAL ERROR ***** Reporting Task: ROOT. Software Version: 1.2.1b (date 31-Aug-2006 time 13:47:21) ------ Performing the Power-On Self Test (POST) ------ UART Channel Loopback Test........................PASS Testing the System SDRAM..........................PASS Boot1 Checksum Test...............................PASS Boot2 Checksum Test...............................PASS Flash Image Validation Test.......................PASS BOOT Software Version 1.0.2 Built 17-Aug-2006 14:55:46 ::: ::: ::: ::: ::: ::: ::::: :::::::::: ::: ::: :::::::::: ::: ::: ::::: ::: ::: ::::: :::: ::: :::: :::: :::: ::: ::: ::: ::: ::: ::: :::::::: :::: :::::::: :::: ::: ::: ::: :: ::: :::::::::: :::::::::: :::: :::::::::: ::: ::: ::: :::::: ::: :::: ::: :::: ::: :::::::::: ::: ::: :::: ::: :::: :::......::: :::: :::......::: ......... ... ... ... ... .... .......... .... .......... Linksys SmartSwitch based on 88E6218 with ARM946E-S. 32MByte SDRAM. I-Cache 8 KB. D-Cache 8 KB. Cache Enabled. Autoboot in 2 seconds - press RETURN or Esc. to abort and enter prom. Preparing to decompress...

Hello,
i know that this threat is a little bit old but we had the same problems with that model.
What i detected by opening the switch was that the electrolytic capacitors are damaged.
Normally they are plain on the top but i counted 15 which were not.
Thats the reason i think that the switch doesn't work properly.

Can't have ASM mark a NFS file as an ASM disk : -is not a block device

Hello,
I’m trying to experiment with ASM for learning purpose. Because I don’t have access to a SAN, I am trying to use NFS files but I can’t manage to have ASM mark those files as ASM disks.
[root@localhost /]# /etc/init.d/oracleasm createdisk ASM_DISK_1 /mnt/asm_dsks/dg1/disk1
Marking disk "ASM_DISK_1" as an ASM disk: [FAILED]
The oracleasm log says: File "/mnt/asm_dsks/dg1/disk1" is not a block device
OK, more context now:
I am trying to install ASM on a RHEL5 virtual machine (on vmware).
[root@localhost /]# uname -rm
2.6.18-8.el5 x86_64
I followed this document:
http://www.oracle.com/technology/pub/articles/smiley-11gr1-install.html until I got stuck at the following command:
/etc/init.d/oracleasm createdisk ...
Now, the NFS filesystem comes from a Solaris 10 system (the only one that's available) running on a physical sun box (this one is not a virtual system).
I have tried many combinations. I tried creating the files on the linux VM, using dd. As root, as oracle. I tried creating them on the Solaris side, using mkfile... no matter what I try, I always get the same issue.
I tried to follow this document: Creating Files on a NAS Device for Use with ASM (http://download.oracle.com/docs/html/B10811_05/app_nas.htm#BCFHCIEC)
But nothing seems to work.
Any idea, recommendations?
Thanks,
Laurent.

Hi buddy,
I guess the metalink note 731775.1 should help You.
In fact the procedure is:
- Create the disk devices on your NFS directory (using dd)
- Adjuste the permissions over those files (in this case, oracle:dba)
- Adjust the ASM_DISKSTRING at the ASM instance and setting the NFS directory in the discovery path
- Verify if they are available at v$asm_disk view
- Create the diskgroup using the the NFS disks that You have created.
Hope it helps,
Cerreia

[SOLVED] /dev/root is not a valid block device

After trying to boot my system after a few days of it remaining off, it fails to boot with:
Booting the kernel.
ERROR: resume: hibernation device '/dev/sda9' not found
mount: /dev/root is not a valid block device
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off.
[rootfs /]#
The sda9 error has been around for quite some time, even back when it was working and I've been ignoring it all these days.
Last edited by SgrA (2013-03-28 18:00:35)

I did try that. Now after a few suggestions on #archlinux, I'm using LABEL's instead of device names, and SYSLINUX. The scene isn't much different, now it complains that it can't find "LABEL=Arch" instead. Here's the current fstab:
# <file system> <dir> <type> <options> <dump> <pass>
LABEL=Boot /boot ext2 defaults 0 1
UUID=c9e24897-af78-4768-bf67-2302ebf17a2b /mnt/Algenib ext4 defaults 0 1
LABEL=Arch / ext4 defaults 0 1
UUID=2cc33548-62ef-4c22-a2c8-13bb5a979273 /mnt/Acrux ext4 defaults 0 1
UUID=cd53f792-f142-45b2-aa0c-ab314950b53b /mnt/Mimosa ext4 defaults 0 1
UUID=122606f2-7ef7-4746-a688-806caaacc86f /mnt/Gacrux ext4 defaults,noauto 0 1
UUID=5b4c6ccb-b90c-488b-aa5d-135a2e98eaf0 swap swap defaults 0 0
and here's syslinux.cfg:
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# * poweroff.com - shutdown the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: [url]https://wiki.archlinux.org/index.php/Syslinux[/url]
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 0 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to [url]http://syslinux.zytor.com/wiki/index.php/Doc/menu[/url]
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=LABEL=Arch ro
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=LABEL=Arch ro
INITRD ../initramfs-linux-fallback.img
LABEL algenib
MENU LABEL Algenib
LINUX ../vml-alg
APPEND root=UUID=c9e24897-af78-4768-bf67-2302ebf17a2b
INITRD ../ini-alg
#LABEL windows
# MENU LABEL Windows
# COM32 chain.c32
# APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL off
MENU LABEL Power Off
COMBOOT poweroff.com
This is what happens:
http://i.imgur.com/cVh1l1l.jpg
Last edited by SgrA (2013-03-28 13:20:22)

I wrote a filter driver over block device.

HI,
I wrote a virutal volume driver over block device , simlar with LVM,
I call it "vraid" ,I can create PV,VG,LV,it's working well.
However I cannot acess the sector over 2G , I can use the system
command "newfs -s XXXX /dev/vlun/rdsk/vlun0" to create a 2G filesystem.
If I use newfs /dev/vlun/rdsk/vlun0 to create the file system in the whole LV size,I found
If LV>2G ,the sector beyond 2G will not be located correctly. output as below.
seek\:XXXXXX Invalid argument.
So I use the system c ommand "truss" to trace the command mkfs (newfs invoke mkfs finally) ,
I found the llseek() is the matter,
When llseek() is invoked, I trace d all system callings,I found if I use llseek() to
locate some sectors, however there is no any callings ocurred in my drvier besides the
calling open() and close()/
I wonder to know why I always failed to acess the sector over 2G .
thanks and happies.
I'm sorry my poor English/
I'm in China. and I'm a Chinese girl.
Ms. Anda

My makefile is the following.:
# CC = /opt/SUNWspro/bin/cc
CC = /usr/local/bin/gcc
LD = /usr/ucb/bin/ld
# 'uname -p' command
INST = i386
INCL = -I . -I $(TOPDIR)/include
#gcc
CFLAGS = -O $(INCL) -D_KERNEL -DOS_SOLARIS -Wall
TOPDIR = ../..
BUILD = vraid
OBJS = _vraid.o \
raid0.o \
raid1.o \
multicopy.o \
snapshot.o \
queue.o \
hash.o \
rand.o
$(BUILD) vraid_driver_setup.bin:$(OBJS)
$(LD) -r -o $(BUILD) $(OBJS)
sh -c ./generate_bin_install.sh
hash.o:hash.c
$(CC) $(CFLAGS) -o hash.o -c hash.c
_vraid.o:vraid.c
$(CC) $(CFLAGS) -o _vraid.o -c vraid.c
raid0.o:raid0.c
$(CC) $(CFLAGS) -o raid0.o -c raid0.c
raid1.o:raid1.c
multicopy.o:multicopy.c
$(CC) $(CFLAGS) -o multicopy.o -c multicopy.c
queue.o:queue.c
$(CC) $(CFLAGS) -o queue.o -c queue.c
snapshot.o:snapshot.c
$(CC) $(CFLAGS) -o snapshot.o -c snapshot.c
rand.o:rand.c
$(CC) $(CFLAGS) -o rand.o -c rand.c
clean:
rm -rf $(OBJS) $(BUILD) vraid_driver_setup.bin

RAC on EMC block devices

I have finished installing a 11g RAC on RHELv5 using EMC block devices for storage.
During installation i had partitioned the disks and changed ownership to oracle:dba
However everytime i reboot the server, the block devices ownership is reverted back to root and hence CRS doesnt fails to come up. So i end up doing a manual change in ownership and permission to bring up the CRS, ASM and finally the database.
Is there any way, i can automate this?
Thanks in Advance.

You can setup this in udev permissnion file. In OEL5 it looks like:
[root@rick oracle]# tail -8 /etc/udev/rules.d/50-udev.rules
KERNEL=="sdb1", OWNER="root", GROUP="oinstall", MODE="640"
KERNEL=="sdc1", OWNER="oracle", GROUP="oinstall", MODE="640"
KERNEL=="sdd1", OWNER="oracle", GROUP="dba", MODE="640"
KERNEL=="sde1", OWNER="oracle", GROUP="dba", MODE="640"
KERNEL=="sdf1", OWNER="oracle", GROUP="dba", MODE="640"
KERNEL=="sdg1", OWNER="oracle", GROUP="dba", MODE="640"

Managed device limit (110) devices has been reached. Unable to manage more.

I get this message when I am adding more devices after discovery. I have the WLSE 1130 that I just upgraded to 2.12fcs. Need help ASAP.

Earlier to this, I was upgrading from 2.11fc to 2.12, and the install failed and I had to download the 2.12 iso. I already have over 110 devices I was managing, and the show version does say device limit=110. It also says now I have a 1105 not a 1130 anymore. Since there is no replies yet, I'm going to try to restore again with 2.11.

Is it possible to block a number in iOS 6 but the same iphone number could be viewed as online on whatsapp application in the blocked device?

Is it possible to block a number in iOS 6 but the same iphone number could be viewed as online on whatsapp application in the blocked device?

Hi ChrisJ4203,
I see you didn't comment on editing the numbers in the keypad, I believe you have that problem too but you forgot to click "I have this question too".
By the way I've sent a couple feedback messages to Apple already and thanks for reminding me, I guess I'll have to be doing that more often.
Enjoy your day

IOS 7 ugrade failed " Error:Device disappeared during timed transition". Phone will not now turn on or sync with itunes, any ideas please?

iOS 7 ugrade failed " Error:Device disappeared during timed transition". Phone will not now turn on or sync with itunes, any ideas please?

if a Mac OSX Computer is in near - try iBackup Viewer.
This is free of charge and can read your backup.
and thats the main difference. Those tools are reading the saved Data in the backup
but itunes attempts to restore the data from the backup on your iphone. if there are any corrupted data in the backup - the backup restore goes wrong. this can happen during security software or wrong corrupt data already stored on the iphone.
if itunes messed up to restore from backup try this one :
- restore your iphone to factory settings using HT1808 or reset all settings and content direct from iphone
- rename your iPhone (e.g. iPhone Test)
- setup your iPhone as new device -> attempt to make a new backup - if successful -
- click in itunes on restore from backup... and choose your desired backup
or go to:
Mac: ~/Library/Application Support/MobileSync/Backup/
Windows XP: \Documents and Settings\(Username)\Application Data\Apple Computer\MobileSync\Backup\
Windows Vista - Windows 7: \Users\(Username)\AppData\Roaming\Apple Computer\MobileSync\Backup\
Pull your complete BackupFolder and try a different PC - copy the BackupFolder on this different PC in the same Path above - start iTunes and see if your Backup is there - attempt to restore from Backup again

Authentication failed on device 3 times. Failed to detect SSH version running on the device. PRIMARY-STARTUP config Fetch Operation failed for TFTP

I have devices loaded but new devices keep getting this error "Authentication failed on device 3 times. Failed to detect SSH version running on the device. PRIMARY-STARTUP config Fetch Operation failed for TFTP" - which trying to get configurations. I am using LMS 3.0.1
I tried to TELNET on devices via Putty port 22 no good. Please help?
Name Version License Status Size CiscoWorks Common Services 3.1.1 Licensed Not applicable Campus Manager 5.0.3 Purchased 1500 CiscoView 6.1.7 Licensed Not applicable CiscoWorks Assistant 1.0.1 Licensed Not applicable Device Fault Manager 3.0.3 Purchased 1500 Internetwork Performance Monitor 4.0.1 Purchased 1500 Integration Utility 1.7.1 Licensed Not applicable LMS Portal 1.0.1 Licensed Not applicable Resource Manager Essentials 4.1.1 Purchased 1500

Showing 1-1 of 1 records
Go to page:
of 1 pages
Device Name
SysObjectID
Model
Device Status
Inventory Status
Inventory Last Updated Time
Config Status
Config Last Updated Time
1.
R2020012_01
.1.3.6.1.4.1.9.1.576
Cisco 2811 Integrated Services Router
Normal
Success
Jan 13 2011 10:43:49 EST
Failed
Jan 13 2011 10:37:24 EST
Rows per page:
20 50 100 500
Go to page:
of 1 pages

SOLARIS 10 with iSCSI Problem "not a block device"

Hi Guys.
I almost reached it to build an iscsi connection with a Netgear readynas 2100.
But I have still one Point which makes me a Problem!!!
Everything works, except mounting the device....
It always Sais me: "not a block device"
At the bottom you can see an output of the whole configuration that I did.
Has anybody maybe a tip for me? Thanks in advance, Mischa
login as: root
Using keyboard-interactive authentication.
Password:
Last login: Fri Dec 18 01:18:30 2009 from pnm
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
Sourcing //.profile-EIS.....
root@sun001 # iscsiadm list discovery
Discovery:
Static: disabled
Send Targets: disabled
iSNS: disabled
root@sun001 # iscsiadm modify discovery -s enable
root@sun001 # iscsiadm modify discovery -t enable
root@sun001 # iscsiadm modify discovery -i enable
root@sun001 # devfsadm
root@sun001 # devfsadm -C
root@sun001 # ping 172.16.251.215
172.16.251.215 is alive
root@sun001 # iscsiadm list discovery
Discovery:
Static: enabled
Send Targets: enabled
iSNS: enabled
root@sun001 # iscsiadm add discovery-address 172.16.251.215
root@sun001 # iscsiadm list discovery-address
Discovery Address: 172.16.251.215:3260
root@sun001 # iscsiadm list discovery-address -v
Discovery Address: 172.16.251.215:3260
Target name: iqn.2009-12.Z-NAS-B0204:znaszim
Target address: 172.16.251.215:3260, 1
root@sun001 # format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t60014052E198270014ED001000000000d0 <DEFAULT cyl 65267 alt 2 hd 255 sec 63> znaszim1
/scsi_vhci/disk@g60014052e198270014ed001000000000
1. c3t0d0 <DEFAULT cyl 17747 alt 2 hd 255 sec 63>
/pci@7b,0/pci1022,7458@11/pci1000,3060@2/sd@0,0
2. c3t2d0 <DEFAULT cyl 17747 alt 2 hd 255 sec 63>
/pci@7b,0/pci1022,7458@11/pci1000,3060@2/sd@2,0
Specify disk (enter its number): ^C
root@sun001 # dev
devattr devfree devfsadm devinfo devlinks devnm devreserv
root@sun001 # dev
devattr devfree devfsadm devinfo devlinks devnm devreserv
root@sun001 # dev
devattr devfree devfsadm devinfo devlinks devnm devreserv
root@sun001 # devfsadm -c iscsi
root@sun001 # iscsiadm list target -S
Target: iqn.2009-12.Z-NAS-B0204:znaszim
Alias: LIO Target
TPGT: 1
ISID: 4000002a0000
Connections: 1
LUN: 0
Vendor: LIO-ORG
Product: FILEIO
OS Device Name: /dev/rdsk/c1t60014052E198270014ED001000000000d0s2
root@sun001 # mkdir /export/iscsi
root@sun001 # mount /dev/rdsk/c1t60014052E198270014ED001000000000d0s2 /export/iscsi/
mount: /dev/rdsk/c1t60014052E198270014ED001000000000d0s2 not a block device
root@sun001 #
-----------------------------------------------------------------

Ok. Sorry i have to explaine it in an other way.
The Storage Device is a Netgear Ready NAS 2100.
Netgear Ready NAS with a Linux os.
The OS Supports different Protocols like: CIFS / FTP / HTTP/ iSCSI etc...
Now im trying to use an other protocoll (cifs) to store the data on the Netgear NAS.
i found smbclient and was able to open a connection to the NAS.
root@sun001 # /usr/sfw/bin/smbclient //172.20.0.51/video_net -U usrvideo
Password:
Domain=[Z-NAS-A0111] OS=[Unix] Server=[Samba 3.4.5]
smb: \> ls
. D 0 Tue Feb 23 11:12:04 2010
.. D 0 Thu Feb 18 10:38:52 2010
172.22.1.58.lnk A 747 Fri Feb 19 19:18:37 2010
172.22.1.55.lnk A 747 Fri Feb 19 18:41:07 2010
65535 blocks of size 33553920. 65535 blocks available
smb: \>
Is there a way to mount the smb connection when the server starts up?
I have to find a way to attach the NAS like a local folder...
And that is why i choose iSCSI before..
Regards
mischa
Edited by: mischu on Feb 26, 2010 2:34 AM

ISE Alarm (WARNING): Dynamic Authorization Failed for Device

Hi all,
I am posting this discussion as previous posts that I have found in this forum have never been resolved or the resolution is not applicable to me.
I am using ISE 1.1.1.268 and WLC 7.2.111.3 and NAC agent version 4.9.1.6 on Windows 7 Client machines.
About once a day i get the error "ISE Alarm (WARNING): Dynamic Authorization Failed for Device".
The device it is reffering to is my NAD, a WLC 5508 running 7.2.111.3
I have looked at the logs and I cannot see anything in the logs which correcponds to this message so that I can troubleshoot further. Maybe I can if I am enabling the correct logging level on the correct ISE component.
Can someone suggest the components and the logging level that I should set to get some more detail about this error?
At the moment, I have only set debug logging on Active Directory. I have TRACE logging set on Posture, Runtime AAA & prrt-JNI.
I do not want to enable too much debug logs, so I was wondering whether anyone can help with a specific element that I should be debugging.
I thought debugging the posture element would be enough but when I look at the logs there is nothing there that relates to this message.
Can anyone help?
thanks
Mario

Firstly, I wouldn't run a production deployment of ISE on 1.1.1.... 1.1.3 Patch 1 or 1.1.4 is the way to go.
Secondly, this error happen a lot, especially with Wireless, and it's not worth worrying about. I've had a couple of TAC cases opened for this and some similar errors, generally they're caused by a Client going to sleep, leaving the coverage area or otherwise leaving the WLC while ISE is trying to do something with it.
Only worry if you actually have a Client-impacting problem, which by the sounds of it, you don't.

Z10 Autoloader failed/blocked, Device Bricked (110 Flash Pattern)

Similar Messages

Maybe you are looking for