RUCKUS Community Forums are now in READ-ONLY mode while we migrate to a new platform.
You will still be able to read posts and knowledge articles, but will be unable to post new content until Go Live on the new platform Monday August 17.
Lennar Smart Home customers: please contact [email protected] for assistance during the week of August 9-17.
03-14-2023 02:49 AM
Hello.
My SZ100 not boot normaly, now it boot lop, cant access via IP, so how to re-insatll firmware via USB drive for it ?
THank you.
Solved! Go to Solution.
03-14-2023 05:55 AM
Hi @QDoan
I see DRDY ERR errors in the boot process. Generally, these errors "{ DRDY ERR }" will generate when there is a hardware failure in the SZ.
You probably need to go for an RMA.
03-14-2023 04:47 AM
Hi @QDoan ,
Please try to access SZ100 using console cable and check if you can login or noticing any abnormal errors in the Console screen.
Regards,
Ajith
03-14-2023 05:41 AM
Hi @QDoan
You can access the SZ via console port, please try the below steps:
Connect the console cable from your PC to SZ's console port.
-Open PUTTY and Configure the serial connection settings as follows:
· Serial line to connect to: Type the COM port name to which you are connected
· Bits per second: 115200
· Data bits: 8
· Parity: None
· Stop bits: 1
· Flow control: None
If you are able to login from the console, you can try upgrading the SZ from the CLI. Below article explains the steps:
https://support.ruckuswireless.com/articles/000010458
03-14-2023 05:46 AM
Dear Kumar,
i can access sz100 via console cable, and get some information follow:
Welcome to CentOS
Starting udev: init: ip6defaultgw (lo) post-start process (890) terminated with status 1
[ OK ]
Setting hostname SZ: [ OK ]
Setting up Logical Volume Management: 1 logical volume(s) in volume group "vg00" now active
[ OK ]
ata1.00: exception Emask 0x0 SAct 0x200 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000008
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:48:38:17:40/01:00:14:00:00/40 tag 9 ncq 135168 in
res 41/40:08:d8:17:40/00:01:14:00:00/40 Emask 0x409 (media error) <F>
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
end_request: I/O error, dev sda, sector 339744728
EXT4-fs error (device dm-0): __ext4_get_inode_loc:
ata1.00: exception Emask 0x0 SAct 0x800 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000008
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/68:58:d8:17:40/00:00:14:00:00/40 tag 11 ncq 53248 in
res 41/40:68:d8:17:40/00:00:14:00:00/40 Emask 0x409 (media error) <F>
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
end_request: I/O error, dev sda, sector 339744728
ata1.00: exception Emask 0x0 SAct 0x1000 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000008
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/60:60:e0:17:40/00:00:14:00:00/40 tag 12 ncq 49152 in
res 41/40:60:e8:17:40/00:00:14:00:00/40 Emask 0x409 (media error) <F>
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
Could you help me to translate what the issues happened with my sz100 ?
thank you.
03-14-2023 05:55 AM
Hi @QDoan
I see DRDY ERR errors in the boot process. Generally, these errors "{ DRDY ERR }" will generate when there is a hardware failure in the SZ.
You probably need to go for an RMA.
