[Problem] Dell R720xd iDRAC BIOS Recovery

BIOS/UEFI Modding BIOS Modding Guides and Problems
141


Yes, tftpboot requires network access and I left out the details of setting that up, you need to set and save a few environment variables to get the network going. Note the idrac can use either the idrac dedicated ethernet port, or it can be set to use port 1 of the host ethernet and having that setting wrong is sometimes why people can not access there idrac.

To set the IP stuff you need to modify these uboot env variables (I show the defaults values here):

1
2
3
4
5
6
 
ipaddr=192.168.0.120
serverip=192.168.0.100
gatewayip=192.168.0.1
netmask=255.255.255.0
netdev=eth0
 
 
I am not sure exactly what you mean by the "SD boot card" method. If you are referring to where I discuss extracting firmimg.d7 to the SD card I have done nothing more with that at this time, focusing my efforts on getting tftpboot to work.
142

Hello,
New guy here.
I just received my R720 today. Upgraded iDRAC and LCC to 2.21.21.
An upgrade (from within windows 10) to 2.40.40 failed and it suggested to reboot and retry. Well guess what? didn’t work and now it’s bricked.
And guess what? it’s bricked properly. No amber light, no nic activity (watching with wireshark). No nothing. Just a LOT of noise.
I tried the SD card loading, but to no avail.
Took a look at the UART and it goes directly to “Welcome to developer console!”.
I can get an interface up and ping, but that’s it.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
 
U-Boot 2009.08 (Nov 04 2015 - 11:28:55) Avocent (0.0.3) EVB
 
CPU: SH-4A
BOARD: R0P7757LC00xxRL (Cn step) board
BOOT: Secure, HRK generated
DRAM:  240MB
  (240MB of 256MB total DRAM is available on U-Boot)
ENV:   Using primary env area.
In:    serial
Out:   serial
Err:   serial
PCIe:  Bridge loaded with 0x18000 bytes
WDT2:  Booted Lower Vector, 'uboot1'
sh_mmcif: 0, sh-sdhi: 1
Net:   sh_eth.0, sh_g_eth.0
INFO: 00:002 Start-up -to- util_idrac_main()
INFO: 00:004 U-Boot 2009.08 (Nov 04 2015 - 11:28:55) Avocent (0.0.3) EVB
INFO: 00:007 U-Boot checkin date(08-04-2015) Version(1.1.31)
INFO: 00:006 iDRAC PPID <NULL>
INFO: 00:003 SPI NOR init 4096 KiB N25Q032 bus=0 cs=0, speed=1000000, mode=3
INFO: 00:007 SH-4A Product: Major Ver=0x31  Minor Ver=0x14 C4 Little endian
             Family=0x10    Major Ver=0x30  Minor Ver=0x0b
INFO: 00:139 BCM54610 OUI=0x00d897  Model=0x26  Revision=0x0a PhyAddr=1
INFO: 00:007 Dedicated monolithic mgmt NIC disabled
INFO: 00:005 SD CARD: is not found
INFO: 00:042 EMMC:   Device: sh_mmcif   Manufacturer ID: 90   OEM: 14a
             Name: HYNIX   Tran Speed: 25000000   Rd Blk Len: 512
             MMC ver 4.0   HC: Yes   cap(<2gb): 0  cap(>2gb): 7569408
             ext_rev: 5    rst_n: 0  ext[96]: 0
INFO: 00:023 CPLD: Major Ver=0x1  Minor Ver=0x0  Maint Ver=0x3
             Planar: Type=0x02  Rev=0x8  Rework=0x0  Scratch/PathRetry=0x00
PASS: 00:014 Coin cell detected good,  AD=0x38f low water=0x2c1
PASS: 00:008 PCIe SH7757_C0 Ver=0.15 MCTP en, CRC=0x8e9b6875 @0x8efbd704 cnt=0x18000
INFO: 00:008 Init PCIe mailbox(PCIe 0xFFEE0150=0x40010000)
INFO: 00:006 mode=normal
INFO: 00:002 reset_cause=BIOS
PASS: 00:005 Booted Lower Vector, 'uboot1' wdt2cnt=1
INFO: 00:005 wdt0cnt=0  cpld_recover_cnt=0  ddr_recover_cnt=0
PASS: 00:006 SMR0 no sermux env, default 0xd4
INFO: 00:005 GRACR=0x3c HISEL=0x00 SIRQCR5_D=0x03 SIRQCR6_D=0x01 LADMSK0=0xff2
             MRSTCR0=0xfedffe7f MRSTCR1=0xfff3ff0f MRSTCR2=0x6f80feff
             BARMAP=0x1 BCR=0x85000000 NCER=0x01fc NCMCR=0x0006 NCCSR=0x0303
PASS: 00:021 etherc0=F0:1F:AF:EB:92:3E
             getherc0=F0:1F:AF:EB:92:3F
INFO: 00:007 Fan logic is not modified on Non-AC power up
INFO: 00:053 Env and backup CRC'ed ok
*** no text signature found ***
INFO: 00:649 Sync eMMC/SPI NOR/Alternate u-boot images
PASS: 00:074 Current u-boot1 1.1.31 verified with 'ubootN'
             Trailer Struct - Missing start token, exp=0xc0de1111 rec=0x0
PASS: 05:847 Verify OS Images N: CRC32 OK: Kernel=0xc4135ec5 Rootfs=0x47eca7d
PASS: 00:007 Boot device=emmc  Boot partition1/N
             Boot Path Retry:P1/N=0 P5/N-1=0
INFO: 00:000 06:971
 

WDT2: Disabled
Initialization complete, proceed with boot
OS_WDT0_EN:180 seconds,  Re-load ILRAM:
SPI_WP: Not attempted.
EMMC_WP: Not attempted.
Boot Path Retry:P1/N=0 P5/N-1=0
Copying kernel image ... OK
## Booting kernel from Legacy Image at 88000000 ...
   Image Name:   sh-linux
   Image Type:   SuperH Linux Kernel Image (gzip compressed)
   Data Size:    2625419 Bytes =  2.5 MB
   Load Address: 80001000
   Entry Point:  80002000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
WDT2: Disable in do_bootm_linux()
 
Monolithic/DRB
systemd[1]: could not find module by name='autofs4'
systemd[1]: Failed to insert 'autofs4'
 
Welcome to developer console!
Type "journalctl -b" to view system logs. Type "systemctl reboot" to reboot.
/home/root #
 


So it seems the eMMC might still work. But dmesg gives me this:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
 
/home/root # dmesg
 1000/Full
<5>SCSI subsystem initialized
<6>Initializing USB Mass Storage driver...
<6>usbcore: registered new interface driver usb-storage
<6>USB Mass Storage support registered.
<4>mknod /dev/sh_pbi c 228 0
<4>sh_pbi: 4kb Shared memory @ ffcaa000, PBI registers @ ffca0000, IRQ 320
<6>usbmux_init():: Init ..
<3>sh_mmcif sh_mmcif.0: Error IRQ while waiting for DMA completion!
<3>mmcblk0: error -5 transferring data, sector 1991385, nr 40, cmd response 0x900, card status 0x0
<3>end_request: I/O error, dev mmcblk0, sector 1991385
<3>Buffer I/O error on device mmcblk0p12, logical block 98394
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 1991393
<3>Buffer I/O error on device mmcblk0p12, logical block 98395
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 1991401
<3>Buffer I/O error on device mmcblk0p12, logical block 98396
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 1991409
<3>Buffer I/O error on device mmcblk0p12, logical block 98397
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 1991417
<3>Buffer I/O error on device mmcblk0p12, logical block 98398
<4>lost page write due to I/O error on mmcblk0p12
<4>JBD: recovery failed
<3>EXT3-fs (mmcblk0p12): error loading journal
<3>sh_mmcif sh_mmcif.0: Error IRQ while waiting for DMA completion!
<3>mmcblk0: error -5 transferring data, sector 2260985, nr 32, cmd response 0x900, card status 0x0
<3>end_request: I/O error, dev mmcblk0, sector 2260985
<3>Buffer I/O error on device mmcblk0p12, logical block 1056752
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2260986
<3>Buffer I/O error on device mmcblk0p12, logical block 1056753
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2260987
<3>Buffer I/O error on device mmcblk0p12, logical block 1056754
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2260988
<3>Buffer I/O error on device mmcblk0p12, logical block 1056755
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2260989
<3>Buffer I/O error on device mmcblk0p12, logical block 1056756
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2260990
<3>Buffer I/O error on device mmcblk0p12, logical block 1056757
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2260991
<3>Buffer I/O error on device mmcblk0p12, logical block 1056758
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2260992
<3>Buffer I/O error on device mmcblk0p12, logical block 1056759
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2260993
<3>Buffer I/O error on device mmcblk0p12, logical block 1056760
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2260994
<3>Buffer I/O error on device mmcblk0p12, logical block 1056761
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2260995
<3>end_request: I/O error, dev mmcblk0, sector 2260996
<3>end_request: I/O error, dev mmcblk0, sector 2260997
<3>end_request: I/O error, dev mmcblk0, sector 2260998
<3>end_request: I/O error, dev mmcblk0, sector 2260999
<3>end_request: I/O error, dev mmcblk0, sector 2261000
<3>end_request: I/O error, dev mmcblk0, sector 2261001
<3>end_request: I/O error, dev mmcblk0, sector 2261002
<3>end_request: I/O error, dev mmcblk0, sector 2261003
<3>end_request: I/O error, dev mmcblk0, sector 2261004
<3>end_request: I/O error, dev mmcblk0, sector 2261005
<3>end_request: I/O error, dev mmcblk0, sector 2261006
<3>end_request: I/O error, dev mmcblk0, sector 2261007
<3>end_request: I/O error, dev mmcblk0, sector 2261008
<3>end_request: I/O error, dev mmcblk0, sector 2261009
<3>end_request: I/O error, dev mmcblk0, sector 2261010
<3>end_request: I/O error, dev mmcblk0, sector 2261011
<3>end_request: I/O error, dev mmcblk0, sector 2261012
<3>end_request: I/O error, dev mmcblk0, sector 2261013
<3>end_request: I/O error, dev mmcblk0, sector 2261014
<3>end_request: I/O error, dev mmcblk0, sector 2261015
<3>end_request: I/O error, dev mmcblk0, sector 2261016
<7>eth0: no IPv6 routers present
<3>sh_mmcif sh_mmcif.0: Error IRQ while waiting for DMA completion!
<3>mmcblk0: error -5 transferring data, sector 2269177, nr 32, cmd response 0x900, card status 0x0
<3>end_request: I/O error, dev mmcblk0, sector 2269177
<3>end_request: I/O error, dev mmcblk0, sector 2269178
<3>end_request: I/O error, dev mmcblk0, sector 2269179
<3>end_request: I/O error, dev mmcblk0, sector 2269180
<3>end_request: I/O error, dev mmcblk0, sector 2269181
<3>end_request: I/O error, dev mmcblk0, sector 2269182
<3>end_request: I/O error, dev mmcblk0, sector 2269183
<3>end_request: I/O error, dev mmcblk0, sector 2269184
<3>end_request: I/O error, dev mmcblk0, sector 2269185
<3>end_request: I/O error, dev mmcblk0, sector 2269186
<3>end_request: I/O error, dev mmcblk0, sector 2269187
<3>end_request: I/O error, dev mmcblk0, sector 2269188
<3>end_request: I/O error, dev mmcblk0, sector 2269189
<3>end_request: I/O error, dev mmcblk0, sector 2269190
<3>end_request: I/O error, dev mmcblk0, sector 2269191
<3>end_request: I/O error, dev mmcblk0, sector 2269192
<3>end_request: I/O error, dev mmcblk0, sector 2269193
<3>end_request: I/O error, dev mmcblk0, sector 2269194
<3>end_request: I/O error, dev mmcblk0, sector 2269195
<3>end_request: I/O error, dev mmcblk0, sector 2269196
<3>end_request: I/O error, dev mmcblk0, sector 2269197
<3>end_request: I/O error, dev mmcblk0, sector 2269198
<3>end_request: I/O error, dev mmcblk0, sector 2269199
<3>end_request: I/O error, dev mmcblk0, sector 2269200
<3>end_request: I/O error, dev mmcblk0, sector 2269201
<3>end_request: I/O error, dev mmcblk0, sector 2269202
<3>end_request: I/O error, dev mmcblk0, sector 2269203
<3>end_request: I/O error, dev mmcblk0, sector 2269204
<3>end_request: I/O error, dev mmcblk0, sector 2269205
<3>end_request: I/O error, dev mmcblk0, sector 2269206
<3>end_request: I/O error, dev mmcblk0, sector 2269207
<3>end_request: I/O error, dev mmcblk0, sector 2269208
<3>sh_mmcif sh_mmcif.0: Error IRQ while waiting for DMA completion!
<3>mmcblk0: error -5 transferring data, sector 2277369, nr 32, cmd response 0x900, card status 0x0
<3>end_request: I/O error, dev mmcblk0, sector 2277369
<3>end_request: I/O error, dev mmcblk0, sector 2277370
<3>end_request: I/O error, dev mmcblk0, sector 2277371
<3>end_request: I/O error, dev mmcblk0, sector 2277372
<3>end_request: I/O error, dev mmcblk0, sector 2277373
<3>end_request: I/O error, dev mmcblk0, sector 2277374
<3>end_request: I/O error, dev mmcblk0, sector 2277375
<3>end_request: I/O error, dev mmcblk0, sector 2277376
<3>end_request: I/O error, dev mmcblk0, sector 2277377
<3>end_request: I/O error, dev mmcblk0, sector 2277378
<3>end_request: I/O error, dev mmcblk0, sector 2277379
<3>end_request: I/O error, dev mmcblk0, sector 2277380
<3>end_request: I/O error, dev mmcblk0, sector 2277381
<3>end_request: I/O error, dev mmcblk0, sector 2277382
<3>end_request: I/O error, dev mmcblk0, sector 2277383
<3>end_request: I/O error, dev mmcblk0, sector 2277384
<3>end_request: I/O error, dev mmcblk0, sector 2277385
<3>end_request: I/O error, dev mmcblk0, sector 2277386
<3>end_request: I/O error, dev mmcblk0, sector 2277387
<3>end_request: I/O error, dev mmcblk0, sector 2277388
<3>end_request: I/O error, dev mmcblk0, sector 2277389
<3>end_request: I/O error, dev mmcblk0, sector 2277390
<3>end_request: I/O error, dev mmcblk0, sector 2277391
<3>end_request: I/O error, dev mmcblk0, sector 2277392
<3>end_request: I/O error, dev mmcblk0, sector 2277393
<3>end_request: I/O error, dev mmcblk0, sector 2277394
<3>end_request: I/O error, dev mmcblk0, sector 2277395
<3>end_request: I/O error, dev mmcblk0, sector 2277396
<3>end_request: I/O error, dev mmcblk0, sector 2277397
<3>end_request: I/O error, dev mmcblk0, sector 2277398
<3>end_request: I/O error, dev mmcblk0, sector 2277399
<3>end_request: I/O error, dev mmcblk0, sector 2277400
<3>sh_mmcif sh_mmcif.0: Error IRQ while waiting for DMA completion!
<3>mmcblk0: error -5 transferring data, sector 2293753, nr 32, cmd response 0x900, card status 0x0
<3>end_request: I/O error, dev mmcblk0, sector 2293753
<3>end_request: I/O error, dev mmcblk0, sector 2293754
<3>end_request: I/O error, dev mmcblk0, sector 2293755
<3>end_request: I/O error, dev mmcblk0, sector 2293756
<3>end_request: I/O error, dev mmcblk0, sector 2293757
<3>end_request: I/O error, dev mmcblk0, sector 2293758
<3>end_request: I/O error, dev mmcblk0, sector 2293759
<3>end_request: I/O error, dev mmcblk0, sector 2293760
<3>end_request: I/O error, dev mmcblk0, sector 2293761
<3>end_request: I/O error, dev mmcblk0, sector 2293762
<3>end_request: I/O error, dev mmcblk0, sector 2293763
<3>end_request: I/O error, dev mmcblk0, sector 2293764
<3>end_request: I/O error, dev mmcblk0, sector 2293765
<3>end_request: I/O error, dev mmcblk0, sector 2293766
<3>end_request: I/O error, dev mmcblk0, sector 2293767
<3>end_request: I/O error, dev mmcblk0, sector 2293768
<3>end_request: I/O error, dev mmcblk0, sector 2293769
<3>end_request: I/O error, dev mmcblk0, sector 2293770
<3>end_request: I/O error, dev mmcblk0, sector 2293771
<3>end_request: I/O error, dev mmcblk0, sector 2293772
<3>end_request: I/O error, dev mmcblk0, sector 2293773
<3>end_request: I/O error, dev mmcblk0, sector 2293774
<3>end_request: I/O error, dev mmcblk0, sector 2293775
<3>end_request: I/O error, dev mmcblk0, sector 2293776
<3>end_request: I/O error, dev mmcblk0, sector 2293777
<3>end_request: I/O error, dev mmcblk0, sector 2293778
<3>end_request: I/O error, dev mmcblk0, sector 2293779
<3>end_request: I/O error, dev mmcblk0, sector 2293780
<3>end_request: I/O error, dev mmcblk0, sector 2293781
<3>end_request: I/O error, dev mmcblk0, sector 2293782
<3>end_request: I/O error, dev mmcblk0, sector 2293783
<3>end_request: I/O error, dev mmcblk0, sector 2293784
<3>sh_mmcif sh_mmcif.0: Error IRQ while waiting for DMA completion!
<3>mmcblk0: error -5 transferring data, sector 2285561, nr 32, cmd response 0x900, card status 0x0
<3>end_request: I/O error, dev mmcblk0, sector 2285561
<3>end_request: I/O error, dev mmcblk0, sector 2285562
<3>end_request: I/O error, dev mmcblk0, sector 2285563
<3>end_request: I/O error, dev mmcblk0, sector 2285564
<3>end_request: I/O error, dev mmcblk0, sector 2285565
<3>end_request: I/O error, dev mmcblk0, sector 2285566
<3>end_request: I/O error, dev mmcblk0, sector 2285567
<3>end_request: I/O error, dev mmcblk0, sector 2285568
<3>end_request: I/O error, dev mmcblk0, sector 2285569
<3>end_request: I/O error, dev mmcblk0, sector 2285570
<3>end_request: I/O error, dev mmcblk0, sector 2285571
<3>end_request: I/O error, dev mmcblk0, sector 2285572
<3>end_request: I/O error, dev mmcblk0, sector 2285573
<3>end_request: I/O error, dev mmcblk0, sector 2285574
<3>end_request: I/O error, dev mmcblk0, sector 2285575
<3>end_request: I/O error, dev mmcblk0, sector 2285576
<3>end_request: I/O error, dev mmcblk0, sector 2285577
<3>end_request: I/O error, dev mmcblk0, sector 2285578
<3>end_request: I/O error, dev mmcblk0, sector 2285579
<3>end_request: I/O error, dev mmcblk0, sector 2285580
<3>end_request: I/O error, dev mmcblk0, sector 2285581
<3>end_request: I/O error, dev mmcblk0, sector 2285582
<3>end_request: I/O error, dev mmcblk0, sector 2285583
<3>end_request: I/O error, dev mmcblk0, sector 2285584
<3>end_request: I/O error, dev mmcblk0, sector 2285585
<3>end_request: I/O error, dev mmcblk0, sector 2285586
<3>end_request: I/O error, dev mmcblk0, sector 2285587
<3>end_request: I/O error, dev mmcblk0, sector 2285588
<3>end_request: I/O error, dev mmcblk0, sector 2285589
<3>end_request: I/O error, dev mmcblk0, sector 2285590
<3>end_request: I/O error, dev mmcblk0, sector 2285591
<3>end_request: I/O error, dev mmcblk0, sector 2285592
<7>eth1: no IPv6 routers present
<3>sh_mmcif sh_mmcif.0: Error IRQ while waiting for DMA completion!
<3>mmcblk0: error -5 transferring data, sector 1196854, nr 34, cmd response 0x900, card status 0x0
<3>end_request: I/O error, dev mmcblk0, sector 1196854
<3>end_request: I/O error, dev mmcblk0, sector 1196856
<3>end_request: I/O error, dev mmcblk0, sector 1196858
<3>end_request: I/O error, dev mmcblk0, sector 1196860
<3>end_request: I/O error, dev mmcblk0, sector 1196862
<3>end_request: I/O error, dev mmcblk0, sector 1196864
<3>end_request: I/O error, dev mmcblk0, sector 1196866
<3>end_request: I/O error, dev mmcblk0, sector 1196868
<3>end_request: I/O error, dev mmcblk0, sector 1196870
<3>end_request: I/O error, dev mmcblk0, sector 1196872
<3>end_request: I/O error, dev mmcblk0, sector 1196874
<3>end_request: I/O error, dev mmcblk0, sector 1196876
<3>end_request: I/O error, dev mmcblk0, sector 1196878
<3>end_request: I/O error, dev mmcblk0, sector 1196880
<3>end_request: I/O error, dev mmcblk0, sector 1196882
<3>end_request: I/O error, dev mmcblk0, sector 1196884
<3>end_request: I/O error, dev mmcblk0, sector 1196886
<3>Aborting journal on device mmcblk0p11.
<2>EXT3-fs (mmcblk0p11): error in ext3_new_inode: Journal has aborted
<3>mmcblk0: error -5 sending stop command, original cmd response 0x900, card status 0xd00
<3>mmcblk0: error -110 transferring data, sector 2291281, nr 8, cmd response 0x900, card status 0x0
<3>end_request: I/O error, dev mmcblk0, sector 2291281
<4>quiet_error: 150 callbacks suppressed
<3>Buffer I/O error on device mmcblk0p12, logical block 1087048
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2291282
<3>Buffer I/O error on device mmcblk0p12, logical block 1087049
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2291283
<3>Buffer I/O error on device mmcblk0p12, logical block 1087050
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2291284
<3>Buffer I/O error on device mmcblk0p12, logical block 1087051
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2291285
<3>Buffer I/O error on device mmcblk0p12, logical block 1087052
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2291286
<3>Buffer I/O error on device mmcblk0p12, logical block 1087053
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2291287
<3>Buffer I/O error on device mmcblk0p12, logical block 1087054
<4>lost page write due to I/O error on mmcblk0p12
<3>end_request: I/O error, dev mmcblk0, sector 2291288
<3>Buffer I/O error on device mmcblk0p12, logical block 1087055
<4>lost page write due to I/O error on mmcblk0p12
<3>mmcblk0: error -110 transferring data, sector 1196620, nr 2, cmd response 0x900, card status 0x0
<3>end_request: I/O error, dev mmcblk0, sector 1196620
<3>Buffer I/O error on device mmcblk0p11, logical block 290
<4>lost page write due to I/O error on mmcblk0p11
<3>JBD: I/O error detected when updating journal superblock for mmcblk0p11.
<3>mmcblk0: error -5 sending stop command, original cmd response 0x900, card status 0xd00
<3>mmcblk0: error -5 sending stop command, original cmd response 0x900, card status 0xd00
<3>mmcblk0: error -5 sending stop command, original cmd response 0x900, card status 0xd00
<3>mmcblk0: error -110 transferring data, sector 1196042, nr 2, cmd response 0x900, card status 0x0
<3>end_request: I/O error, dev mmcblk0, sector 1196042
<3>Buffer I/O error on device mmcblk0p11, logical block 1
<4>lost page write due to I/O error on mmcblk0p11
<3>EXT3-fs (mmcblk0p11): I/O error while writing superblock
<2>EXT3-fs (mmcblk0p11): error in ext3_create: Journal has aborted
<3>mmcblk0: error -5 sending stop command, original cmd response 0x900, card status 0xd00
<3>mmcblk0: error -5 sending stop command, original cmd response 0x900, card status 0xd00
<3>mmcblk0: error -5 sending stop command, original cmd response 0x900, card status 0xd00
<3>mmcblk0: error -5 sending stop command, original cmd response 0x900, card status 0xd00
/home/root #
 


Is there ANYTHING to be done? I've read all of this thread, most on reddit..
143

@oh2ftu Your in a similiar state to me, your actually ARE booting the Linux kernel, but it is not booting all the way. What does a "df" command show? I wonder how many of the file systems got mounted.

144

@rgrimes I will have to reboot the uBoot for that. Now it just shows hundreds of lines of the same mount-points. Same for ‘mount’ and ‘df’. I’m able to mount the sd-card and look at it’s contents (including firming.d7). Any idea how to boot it?
Mount:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
 
/home/root # mount
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=116100k,nr_inodes=29025,mode=755)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=//lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
tmpfs on /etc/machine-id type tmpfs (ro,relatime,mode=755)
mqueue on /dev/mqueue type mqueue (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
/dev/mmcblk0p9 on /flash/pd9 type squashfs (ro,noatime)
/dev/mmcblk0p14 on /flash/data2 type ext2 (rw,noatime,errors=continue)
tmpfs on /var/volatile type tmpfs (rw,relatime)
/dev/mmcblk0p15 on /mmc2 type ext3 (rw,noatime,errors=continue,barrier=1,data=ordered)
/dev/mmcblk0p13 on /mnt/cores type ext3 (rw,noatime,errors=continue,user_xattr,barrier=1,data=writeback)
/dev/mmcblk0p11 on /flash/data0 type ext3 (rw,noatime,errors=continue,barrier=1,data=ordered)
 


df:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
 
/home/root # df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                   91904     91904         0 100% /
/dev/root                91904     91904         0 100% /
devtmpfs                116100         0    116100   0% /dev
tmpfs                   116164         0    116164   0% /dev/shm
tmpfs                   116164       136    116028   0% /run
tmpfs                   116164         0    116164   0% /sys/fs/cgroup
tmpfs                   116164       136    116028   0% /etc/machine-id
tmpfs                   116164         8    116156   0% /tmp
/dev/mmcblk0p9            1024      1024         0 100% /flash/pd9
/dev/mmcblk0p14           2011       136      1855   7% /flash/data2
tmpfs                   116164         0    116164   0% /var/volatile
/dev/mmcblk0p15         604736     16880    587856   3% /mmc2
/dev/mmcblk0p13          48541      6036     42505  12% /mnt/cores
/dev/mmcblk0p11           3835      2899       896  76% /flash/data0
/home/root #
 
145

Alright. So I’m taking a few leaps here and there. I’m able to mount the SD-card. I can use dd, and dump something to the SD-card.
How should I go forth in dumping the SPI flash? which device is it? after that, I could try reflashing it (via the same console?) with a working dump?

146
Zitat von oh2ftu im Beitrag #144
@rgrimes I will have to reboot the uBoot for that. Now it just shows hundreds of lines of the same mount-points. Same for 'mount' and 'df'. I'm able to mount the sd-card and look at it's contents (including firming.d7). Any idea how to boot it?
Mount:

df:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
 
/home/root # df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                   91904     91904         0 100% /
/dev/root                91904     91904         0 100% /
devtmpfs                116100         0    116100   0% /dev
tmpfs                   116164         0    116164   0% /dev/shm
tmpfs                   116164       136    116028   0% /run
tmpfs                   116164         0    116164   0% /sys/fs/cgroup
tmpfs                   116164       136    116028   0% /etc/machine-id
tmpfs                   116164         8    116156   0% /tmp
/dev/mmcblk0p9            1024      1024         0 100% /flash/pd9
/dev/mmcblk0p14           2011       136      1855   7% /flash/data2
tmpfs                   116164         0    116164   0% /var/volatile
/dev/mmcblk0p15         604736     16880    587856   3% /mmc2
/dev/mmcblk0p13          48541      6036     42505  12% /mnt/cores
/dev/mmcblk0p11           3835      2899       896  76% /flash/data0
/home/root #
 


I am not sure why you say you need to reboot the uBoot to do the df, the df is a linux command. Anyway I see you got the output and your in much better shape than I am. My system does not mount ANY of the /dev/mmcblk0p* entries.

I have not completed the boot from sd-card, but I can say some of the instructions in other parts of this thread CAN destroy your SPI flash, so be warry of what you follow. I have more information, but I am intentionally NOT posting it until I have tested and verified that it works and does no damange.

BE VERY VERY careful with the uboot fwu utility if you try to use it!!!

Currently I am spending most of my time on this problem READING the dell open source release of the 1.57.57 idrac code so that I better understand what these commands and messages are really doing and what they are telling me.

One tidbit in reading that code is I have confirmed that Dell puts the emmc chip on the board BLANK, and that the uboot code, if working correctly, partitions the emmc and then goes into a poll mode looking for the firmimg.d7 file. This means that an actual repair of a failed emmc chip should be a mater of an expert with hot air rework replace the chip and someone doing the idrac recovery. One suspect as to a failure mechanism I have is that if this code decides the emmc is blank and does this partitioning at every boot cycle one could rack up a lot of write cycles on the same blocks pretty quickly, this may be a mechanism of wear out, though it should only start down this road if the emmc is already corrupted.
147

Leaving the system on will leave df and mount with hundreds of duplicate mount points.
I did manage to mount a SD-card and dump both SPI and emmc (possibly?):

1
2
3
4
5
6
7
8
 

mount /dev/mmcblk1p1 /media/card
cd /dev/
for i in mmcblk0boot*;do dd if=/dev/$i of=/media/card/$i.bin;done
for i in mmcblk0p*;do dd if=/dev/$i of=/media/card/$i.bin;done
for i in mtd*;do dd if=/dev/$i of=/media/card/$i.bin;done
umount /media/card
 
 

The last will dump the devices mtd_, mtd_ro and mtdblock_ - all seem identical.

I will have to look at the thread if someone has a pre 2.x version of the SPI-dump. What will need to be modified is at least:
- Service tag
- ethernet mac
- Licenses?

These might be located in multiple places.

I'm not sure if I've got fwu-utility, I only get the root shell of uboot.
Might just try to erase the emmc and see what that does.
The emmc seems to be 0,5 pitch, I've done TFBGA88 before without any issues. Reballing is a PITA, though a new chip would have the balls in place making it much easier.
148

Status report:
- Flashed v1.57 with SPI, no luck
- Flashed original (somewhere between 2.21 and 2.40) still the same.
Using the interrupt, I can now get to iDRAC8=>
Still:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
 

iDRAC8=> fwu check 0x81000000
Checking image header CRC ... OK
Checking platform env ID..... OK
Checking kernel image CRC ... OK
Checking rootfs image CRC ... OK
Checking u-boot image CRC ... OK
Skipping u-boot update ...... NO
Checking Platform image CRC . OK
Checking processor support .. OK
Done!
iDRAC8=> fwu mmc emmc
Erasing SPI flash at 0x100000...Writing to SPI flash...done
Erasing SPI flash at 0x110000...Writing to SPI flash...done
iDRAC8=> fwu update 0x81000000
 
*** Updating Partition 1 ***
Checking image header CRC ... OK
Checking platform env ID..... OK
Checking kernel image CRC ... OK
Checking rootfs image CRC ... OK
Checking u-boot image CRC ... OK
Skipping u-boot update ...... NO
Checking Platform image CRC . OK
Checking processor support .. OK
Copying kernel image ........ mmc write failed, err=-84
*** fail to write block to device ***
Fail
*** fail to update kernel image ***
*** fail to update image ***
iDRAC8=> mmcinfo
Device: sh_mmcif
Manufacturer ID: 90
OEM: 14a
Name: HYNIX
Tran Speed: 25000000
Rd Block Len: 512
MMC version 4.0
High Capacity: Yes
Capacity: 0
Bus Width: 8-bit
 

I guess it loads something from the emmc to SPI during boot, which is not ideal.

Here's what bothers me:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
 

INFO: 00:077 Env and backup CRC'ed ok
Erasing SPI flash at 0x100000...Writing to SPI flash...done
Erasing SPI flash at 0x110000...Writing to SPI flash...done
[b]*** no text signature found ***
[/b]INFO: 02:563 Sync eMMC/SPI NOR/Alternate u-boot images
[b]PASS: 00:262 Current u-boot1 1.1.31 verified with 'ubootN'
             Trailer Struct - Missing start token, exp=0xc0de1111 rec=0x0
             U-boot2 in sync with u-boot1 1.1.31[/b]
PASS: 05:803 Verify OS Images N: CRC32 OK: Kernel=0xc4135ec5 Rootfs=0x47eca7d
[b]PASS: 00:008 Boot device=emmc  Boot partition1/N
             Boot Path Retry:P1/N=0 P5/N-1=0[/b]
INFO: 00:071 No 'userexe' defined
 
 

I've ordered two blank emmc's and a few spi:s. But the SPI flashes are redundant now that I've borrowed a programmer.
149

Yeah @ldv mentioned it here Dell R720xd iDRAC BIOS recovery (6) where you could boot directly from the SD card. Basically an alternative to the tftp option.

I want to see if I can get mine to do the above SD card boot like @ldv mentioned. If not I’ll fall back to trying the tftp.

I have a hot air reworkstation and ordered the eMMC, so once it arrives I’m going to try to attempt to replace it.

To me it really doesn’t make sense that the eMMC died though.

150

When you boot from SD card does the system still have the issue of loud fans (for a long time) upon every restart? Or only if iDRAC loses power i.e. system gets unplugged

151

@alexthefifth if you are talking to me, I haven’t gotten it to boot directly from the SD card yet.

I have tried the util recover -emmc -from sd -f firmimg.d7but that fails with write errors. Running the mmcinfo command seems to indicate that the eMMC has failed.


So a litte update from me.

I can get into recovery mode (shorting SW2 procedure)

1
2
3
4
5
6
7
8
9
10
 

NOTE: After stopping u-boot in this development mode.  You may need to
      warm/cold reset the server when booting iDRAC manually as BIOS
      may have already viewed iDRAC as unresponsive.
 

 
RECOVER:Max retries occured for both N/N-1 paths, OR forced recover.
 
iDRAC7=>
 


I can also do tftpboot -f firmimg.d7
1
2
3
4
5
6
7
8
9
10
 

iDRAC7=> tftpboot -f firmimg.d7
reset PHY of sh_g_eth.0
1000Base/Full
Using sh_g_eth.0 device
TFTP from server 192.168.0.214; our IP address is 192.168.0.245
Filename 'firmimg.d7'.
Load address: 0x0
Loading:   60 MB
Bytes transferred = 63064294 (3c248e6 hex)
 


However, as soon as I do

1
 
go addr 0x81000000
 


It immediately tries booting and then starts polling for my flashcard instead of booting the actual firmimg.d7 image.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
 

U-Boot 2009.08-00088-g121cddc (Nov 17 2014 - 05:50:46) Avocent (0.0.3) EVB, Build: jenkins-idrac-yocto-release-505
 
CPU: SH-4A
BOARD: R0P7757LC00xxRL (C0 step) board
BOOT: Insecure, HRK not generated
DRAM:  240MB
  (240MB of 256MB total DRAM is available on U-Boot)
ENV:   Using primary env area.
In:    serial
Out:   serial
Err:   serial
PCIe:  Bridge loaded with 0x18000 bytes
WDT2:  Booted Lower Vector, 'uboot1'
sh_mmcif: 0, sh-sdhi: 1
Net:   sh_eth.0, sh_g_eth.0
INFO: 00:002 Start-up -to- util_idrac_main()
INFO: 00:005 U-Boot 2009.08-00088-g121cddc (Nov 17 2014 - 05:50:46) Avocent (0.0.3) EVB
INFO: 00:008 U-Boot checkin date(05-10-2013) Version(1.0.183)
INFO: 00:006 iDRAC PPID <NULL>
INFO: 00:003 SPI NOR init 4096 KiB N25Q032 bus=0 cs=0, speed=1000000, mode=3
INFO: 00:007 SH-4A Product: Major Ver=0x31  Minor Ver=0x14 C4 Little endian
             Family=0x10    Major Ver=0x30  Minor Ver=0x0b
PASS: 00:015 Dedicated monolithic mgmt NIC disabled
INFO: 00:129 BCM54610 OUI=0x3fffff  Model=0x3f  Revision=0x0f PhyAddr=1
INFO: 00:006 SD CARD: is not found
INFO: 00:042 EMMC:   Device: sh_mmcif   Manufacturer ID: 90   OEM: 14a
             Name: HYNIX   Tran Speed: 25000000   Rd Block Len: 512
             MMC version 4.0   High Capacity: Yes   Capacity: 0
INFO: 00:019 CPLD: Major Ver=0x1  Minor Ver=0x0  Maint Ver=0x4
             Planar: Type=0x07  Rev=0x4  Rework=0x0  Scratch/PathRetry=0x0f
PASS: 00:014 Coin cell detected good,  AD=0x399 low water=0x2c1
PASS: 00:007 PCIe C0 Ver=0.15 MCTP en, CRC=0x8e9b6875 @0x8efbf954 cnt=0x18000
INFO: 00:007 Init PCIe mailbox(PCIe 0xFFEE0150=0x40010000)
INFO: 00:006 mode=normal
INFO: 00:003 reset_cause=recover
PASS: 00:004 Booted Lower Vector, 'uboot1' wdt2cnt=0
INFO: 00:006 wdt0cnt=0
PASS: 00:002 SMR0 no sermux env, default 0xd4
INFO: 00:004 GRACR=0x3c HISEL=0x00 SIRQCR5_D=0x03 SIRQCR6_D=0x01 LADMSK0=0xff2
             MRSTCR0=0xfedffe7f MRSTCR1=0xfff3ff0f MRSTCR2=0x7f80feff
             BARMAP=0x1 BCR=0x85000000 NCER=0x01fc NCMCR=0x0006 NCCSR=0x0303
PASS: 00:021 etherc0=C8:1F:66:C0:DE:0D
             getherc0=C8:1F:66:C0:DE:0E
INFO: 00:008 Fan logic is not modified on Non-AC power up
INFO: 00:052 Env and backup CRC'ed ok
*** no text signature found ***
INFO: 00:650 Sync eMMC/SPI NOR/Alternate u-boot images
PASS: 00:075 Current u-boot1 1.0.183 verified with 'ubootN1'
             Trailer Struct - Missing start token, exp=0xc0de1111 rec=0x701070
PASS: 03:978 Verify OS Images N-1: CRC32 OK: Kernel=0x8c86b2b Rootfs=0xb0e73b0
FAIL: 00:007 Boot device=emmc  Boot partition5/N-1
             Boot Path Retry:P1/N=3 P5/N-1=3  Recover
INFO: 00:000 05:096
 

WDT2: Disabled
 

######################################################################
** No bootable iDRAC image is found **
** (System Health & ID LED is flashing amber at ~1/2 second rate).
To Recover iDRAC via an SD card.
1)  Format SD using FAT on a Windows box or EXT3 using Linux.
2)  Copy 'firmimg.d7' to root path.
3)  Insert SD card.
4)  System Health & ID button solid amber durning recover.
5)  Both boot paths are flashed.
######################################################################
 
Polling for SD card state change \
 


Is there something I'm missing to force it to boot from memory and the firmimg.d7 that tftp grabbed? I have a feeling that if I had a good emmc chip that as soon as I did what it asks it would flash the emmc with the firmimg.d7 file. However, I was just trying to get this thing to boot with tftpboot into an actual running idrac.
152

I slept over this.
Am I correct in seeing that some of the information from the eMMC is copied over to SPI during boot?
This would explain why a 1.57 flashed SPI would show iDRAC8=>.
And when the material at eMMC is not as it should, the whole shebang fails.
Still, it’s possibly I just have a faulty eMMC. I’d need to nuke it, to be sure. But booting up to linux will not allow me to release all partitions. DUH.
Maybe boot from SD-card? I guess I will try that today;
- using util recovery flash both SD and SPI with 1.57
- boot from SD
- mount emmc (mmcblk0) and nuke it

Apparently direct access via debug pins have been unsuccessful?
And I would need suitable hardware for it.

153

Well this might be the end of the road for me…I screwed up…royally and went completely backwards where I might not be able to recover.

I was trying to follow these instructions to validate I was getting a good image…

Dell R720xd iDRAC BIOS recovery (5)

However, prior to that I was messing with the fwu dev &lt;x&gt; command and I swapped to ‘fwu dev 4’…which is “FLASH”, which I am pretty damn sure is the 25Q03213 (U_IDRAC_SPI) chip flash memory…and NOT the CF card memory :(. This resulted in NOTHING working. The iDRAC does nothing, USB-to-UART was obviously working fine, however, after I get nothing. I short the pins, no output, I unplug and plug back in, nothing. Its just completely dead.

I ordered a Black CH341A programmer from Amazon. https://www.amazon.com/Organizer-EEPROM-…10089833&sr=8-3

I’m going to cross my fingers and pray that the dump from this post Dell R720xd iDRAC BIOS recovery will work on this chip (anyone else know of another U_IDRA_SPI dump), if it doesn’t them I’m completely SOL and can’t do anything as I didn’t make a backup or anything (no way to make a backup without ordering more stuff…but now was forced to…) of the U_IDRAC_SPI chip.

154


A fully functional sd card boot appears to be possible, which would mean the fan controls are working correctly, infact your system is "fixed" other than now you can not use the SD/vimage functionality for anything else. For me that is kinda a non-starter as I need the SD card for loading ReFind/Clover to support my PCIe/NVMe drives. To get the sd card working one person has posted here how to do it, though I would NOT fuss with the SPI/nor flash like he did, there is no reason to do that, he ended up restoring it anyway.

155


I cant get to my idrac right now, the SPI flash should show up in /dev, to find out what is stored where on spi and emmc use:

1
 
util info -flashmap"
 

From what I see of your system @oh2ftu it appears to me that there is NOTHING wrong with your SPI, and I would back it up, and leave it alone. Critical env values can be obtained easily with a uboot "printenv" command and saved off to a text file.
156


Do NOT do the setenv bootcmd recommend in this and other messages UNTIL you have tested it working from the command line, it can be a royal pain to break out of a uboot boot loop caused by a bad bootcmd setting. Especially those saying to put a tftpboot command in bootcmd.

157
Zitat von oh2ftu im Beitrag #147
Leaving the system on will leave df and mount with hundreds of duplicate mount points.
I did manage to mount a SD-card and dump both SPI and emmc (possibly?):
1
2
3
4
5
6
7
8
 

mount /dev/mmcblk1p1 /media/card
cd /dev/
for i in mmcblk0boot*;do dd if=/dev/$i of=/media/card/$i.bin;done
for i in mmcblk0p*;do dd if=/dev/$i of=/media/card/$i.bin;done
for i in mtd*;do dd if=/dev/$i of=/media/card/$i.bin;done
umount /media/card
 
 

The last will dump the devices mtd_, mtd_ro and mtdblock_ - all seem identical.

I will have to look at the thread if someone has a pre 2.x version of the SPI-dump. What will need to be modified is at least:
- Service tag
- ethernet mac
- Licenses?

These might be located in multiple places.

I'm not sure if I've got fwu-utility, I only get the root shell of uboot.
Might just try to erase the emmc and see what that does.
The emmc seems to be 0,5 pitch, I've done TFBGA88 before without any issues. Reballing is a PITA, though a new chip would have the balls in place making it much easier.

IIRC the /dev/mtd* devices are the SPI flash. You should be able to get WHOLE device type backups with using /dev/mmcblk0 (emmc) and /dev/mtd0 in a dd command. You have done each partition and probably got some duplicated date, more better to have more than less! And yes, mtd_, mtd_ro and mtdblock_ would appear identical to a dd command, they are used for different things in different ways by linux, this is the old mtd nor interface, which is the SPI chip.

Since you appear to have good backups it would seem safe to erase the emmc, I can not get the dd to work, it fails with an error before it reads any data at all.
You should not need to touch your SPI, it seems to me to be entact and working correctly, if you want to save critical values the uboot "printenv" command prints out all the values.
Idrac license... hummm.. not sure where that is stored yet. God I hope not in the emmc.

fwu-utility is in uboot, "help fwu", I actually went through the "help" commands read all that, and then read several of the help on sub commands.

I've just gotten hot air, so very little experience and defanitly not ready to try and reballing! I have tons of scrap to practice on though.
158

Huh? Do you mean flashed EMMC with v.1.57.57?

Zitat

- Flashed original (somewhere between 2.21 and 2.40) still the same.
Using the interrupt, I can now get to iDRAC8=>
Still:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
 

iDRAC8=> fwu check 0x81000000
Checking image header CRC ... OK
Checking platform env ID..... OK
Checking kernel image CRC ... OK
Checking rootfs image CRC ... OK
Checking u-boot image CRC ... OK
Skipping u-boot update ...... NO
Checking Platform image CRC . OK
Checking processor support .. OK
Done!
iDRAC8=> fwu mmc emmc
Erasing SPI flash at 0x100000...Writing to SPI flash...done
Erasing SPI flash at 0x110000...Writing to SPI flash...done
iDRAC8=> fwu update 0x81000000
 
*** Updating Partition 1 ***
Checking image header CRC ... OK
Checking platform env ID..... OK
Checking kernel image CRC ... OK
Checking rootfs image CRC ... OK
Checking u-boot image CRC ... OK
Skipping u-boot update ...... NO
Checking Platform image CRC . OK
Checking processor support .. OK
Copying kernel image ........ mmc write failed, err=-84
*** fail to write block to device ***
Fail
[/quote]This is the same thing I get anytime I try to write to the emmc.[quote]
*** fail to update kernel image ***
*** fail to update image ***
iDRAC8=> mmcinfo
Device: sh_mmcif
Manufacturer ID: 90
OEM: 14a
Name: HYNIX
Tran Speed: 25000000
Rd Block Len: 512
MMC version 4.0
High Capacity: Yes
Capacity: 0
Bus Width: 8-bit
 

I guess it loads something from the emmc to SPI during boot, which is not ideal.

Here's what bothers me:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
 

INFO: 00:077 Env and backup CRC'ed ok
Erasing SPI flash at 0x100000...Writing to SPI flash...done
Erasing SPI flash at 0x110000...Writing to SPI flash...done
[b]*** no text signature found ***
[/b]INFO: 02:563 Sync eMMC/SPI NOR/Alternate u-boot images
[b]PASS: 00:262 Current u-boot1 1.1.31 verified with 'ubootN'
             Trailer Struct - Missing start token, exp=0xc0de1111 rec=0x0
             U-boot2 in sync with u-boot1 1.1.31[/b]
PASS: 05:803 Verify OS Images N: CRC32 OK: Kernel=0xc4135ec5 Rootfs=0x47eca7d
[b]PASS: 00:008 Boot device=emmc  Boot partition1/N
             Boot Path Retry:P1/N=0 P5/N-1=0[/b]
INFO: 00:071 No 'userexe' defined
 
 

I've ordered two blank emmc's and a few spi:s. But the SPI flashes are redundant now that I've borrowed a programmer.

WHAT in that last block bothers you? The "nouserexe" is normal from what I can tell., so is the no text signature which is related to ancient uboot kernels that are not in a uimage format.
159



sigh Ok, let me put this out there, and maybe a mod can go fix that post, DO NOT, REPEAT DO NOT attempt to write firmware images to SPI, that is a BRICK that well need jtag to reprogram the SPI. There is NO reason to fuss with the SPI, in all cases I have seen here the SPI is working just fine. All of these issues are centered around emmc failures. I have not looked to see if we can get your system back by a dip switch that would cause it to load uboot from the emmc, there are multiple copies of uboot in a system, 2 in SPI and 2 in emmc:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
 
iDRAC7=> util info -flashmap
 
Flash Address Map EMMC:
Image    Start   End     Blk      Size in     Start       Last       Filename:
Name:    Blk:    Blk:    Cnt:     Bytes:      Address:    Address:
 
mbr      0x00000 0x00000 0x00001  0x00000200  0x00000000  0x000001ff
kernelN  0x00001 0x08001 0x08000  0x01000000  0x00000200  0x010001ff kernel.bin
rootfsN  0x08001 0x3fc01 0x37c00  0x06f80000  0x01000001  0x07f80000 rootfs.squashfs
ubootN   0x3fc01 0x40001 0x00400  0x00080000  0x06f88001  0x07008000 u-boot.bin
ext      0x40001 0x40001 0x00001  0x00000200  0x000bfc01  0x000bfe00
kernelN1 0x40002 0x48002 0x08000  0x01000000  0x00040201  0x01040200 kernel.bin
rootfsN1 0x48003 0x7fc03 0x37c00  0x06f80000  0x00048202  0x06fc8201 rootfs.squashfs
ubootN1  0x7fc04 0x80004 0x00400  0x00080000  0x0007fe03  0x000ffe02 u-boot.bin
scratch  0x80005 0x120005 0xa0000  0x14000000  0x00080204  0x14080203
pdataN   0x120006 0x122006 0x02000  0x00400000  0x00120205  0x00520204
pdataN1  0x122007 0x124007 0x02000  0x00400000  0x00122206  0x00522205
ps       0x124008 0x126008 0x02000  0x00400000  0x00124207  0x00524206
maser    0x126009 0x3e700a 0x2c1001  0x58200200  0x00126208  0x58326407
core     0x3e700b 0x3fed84 0x17d79  0x02faf200  0x003e720a  0x03396409
freshair 0x3fed8b 0x3ffd8b 0x01000  0x00200000  0x003ff985  0x005ff984
extmaser 0x401d8d 0x52dd8d 0x12c000  0x25800000  0x007fff8c  0x25ffff8b
part1    0x00001 0x40001 0x40000  0x000bfc00  0x00000200  0x000bfdff
part5    0x40002 0x80002 0x40000  0x000bfc00  0x00040201  0x000ffe00
part1_5  0x00000 0x80002 0x80002  0x10000400  0x00000000  0x100003ff
non_os   0x80005 0x3e700a 0x367005  0x6ce00a00  0x00080204  0x6ce80c03
1gig     0x00000 0x200000 0x200000  0x40000000  0x00000000  0x3fffffff
2gig     0x00000 0x400000 0x400000  0x80000000  0x00000000  0x7fffffff
3gig     0x00000 0x600000 0x600000  0xc0000000  0x00000000  0xbfffffff
 

Flash Address Map SPI NOR:
Image    Start End   Sect Size in     Start       Last       Filename:
Name:    Sect: Sect: Cnt: Bytes:      Address:    Address:
 
uboot1   000   007   008  0x00080000  0x00000000  0x0007ffff u-boot.bin
uboot2   008   015   008  0x00080000  0x00080000  0x000fffff u-boot.bin
env1     016   016   001  0x00010000  0x00100000  0x0010ffff
env2     017   017   001  0x00010000  0x00110000  0x0011ffff
fru      018   018   001  0x00010000  0x00120000  0x0012ffff fru12g.bin
res1     019   019   001  0x00010000  0x00130000  0x0013ffff
pt       020   027   008  0x00080000  0x00140000  0x001bffff
lcl      028   051   024  0x00180000  0x001c0000  0x0033ffff
res2     052   063   012  0x000c0000  0x00340000  0x003fffff
4meg     000   063   064  0x00400000  0x00000000  0x003fffff 12G_SPINOR.bin
UTIL PASS
iDRAC7=> version
 
160



I 100% agree with you that there is no need to do anything with the SPI. It was working fine. I was NOT intentionally trying to do with the SPI. I was trying to get the idrac to boot via the tftpboot command. But accidentally wrote it to the SPI it appears.



100% agree and I was not intentionally trying to do what I did.

I was trying to get it to boot with tftpboot or straight off the SD card. However, I accidentally wrote it out to the SPI.



I don’t think my eMMC has anything on it, it appears to be faulty, which is what brought me here in the first place, so I don’t think trying to load anything from the eMMC will work.

At this point though, I was hoping I could reprogram the 25Q03213 with the Black CH341A with one of the firmware ROMs posted here. Is there something else I’m missing that I should need besides the CH341A to at least try it? At this point I don’t have anything else to lose.