nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SZ100 boot lop, how to install firmware via USB

QDoan

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.

Find more posts tagged with

Accepted answers

sanjay_kumar

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.

All comments

Ajith_VS

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

sanjay_kumar

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

QDoan

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.

sanjay_kumar

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.