I'm following the "Cosmos OpenSSD Software User Guide"

From OpenSSDWiki
Viewed 6449 times, With a total of 11 Posts
Jump to: navigation, search

Clicked A Few Times
Threads 2
Posts 9
I'm proceeding the "Cosmos OpenSSD Software User Guide"

In "4.1.5 Formatting", when I type "mkfs.ext4 /dev/pcissda1",

error message appear on the hyperterminal

...
!!! a failure was detected in previous 2 operation - 2,3 !!!
!!! a failure was detected in previous 2 operation - 3,3 !!!
!!! a failure was detected in previous 2 operation - 2,1 !!!
!!! a failure was detected in previous 2 operation - 1,1 !!!
!!! a failure was detected in previous 2 operation - 2,1 !!!
!!! a failure was detected in previous 2 operation - 3,1 !!!
!!! a failure was detected in previous 2 operation - 0,2 !!!
!!! a failure was detected in previous 2 operation - 1,2 !!!
...

I use "greedy FTL v1.2.0"

I wish to solve this problem...

Thank you!

Clicked A Few Times
Threads 2
Posts 24
The "Cosmos OpenSSD Software User Guide" is replaced with Demo Guide v1.0.

Please refer to the following document.
http://166.104.36.35:10080/Cosmos_OpenSSD/documents/tutorial/Demo%20Guide%20v1.0.pdf

I recommend you to proceed the Demo Guide v1.0 from the beginning.

Thanks.

Clicked A Few Times
Threads 2
Posts 9
I retry to follow the Demo Guide v1.0, but I have still same problem.

=============================================================
when I type "mkfs.ext4 /dev/pcissda1",

error message appear on the hyperterminal

...
!!! a failure was detected in previous 2 operation - 2,3 !!!
!!! a failure was detected in previous 2 operation - 3,3 !!!
!!! a failure was detected in previous 2 operation - 2,1 !!!
!!! a failure was detected in previous 2 operation - 1,1 !!!
!!! a failure was detected in previous 2 operation - 2,1 !!!
!!! a failure was detected in previous 2 operation - 3,1 !!!
!!! a failure was detected in previous 2 operation - 0,2 !!!
!!! a failure was detected in previous 2 operation - 1,2 !!!
...
=============================================================

What should I do?

What kind of problem.. hardware or software?

Thanks.
Edited On 4:41:44 AM - Mon, Jul 6th 2015 by Chuminsung

Clicked A Few Times
Threads 2
Posts 24
Could you capture UART messages from the beginning?

I think bad block checking at booting time isn't properly done.
I want to see initialization messages.

Thanks.

Clicked A Few Times
Threads 2
Posts 9
Thank you, your reply :)
I will show my UART messages.

I try "Run as > 1 Launch on Hardware(GDB)"
and Host PC(Linux) is turned on.

UART Message is below.

Contents

==============================================





SSD firmware start -------




[ ssd NAND device reset complete. ]
[ ssd page map initialized. ]
Bad block mark is checked at: Ch 0 Way 0 Block 0
Bad block mark is checked at: Ch 1 Way 0 Block 0
Bad block mark is checked at: Ch 2 Way 0 Block 0
Bad block mark is checked at: Ch 3 Way 0 Block 0
Bad block mark is checked at: Ch 0 Way 1 Block 0
Bad block mark is checked at: Ch 1 Way 1 Block 0
Bad block mark is checked at: Ch 3 Way 1 Block 0
Bad block mark is checked at: Ch 0 Way 2 Block 0
Bad block mark is checked at: Ch 1 Way 2 Block 0
Bad block mark is checked at: Ch 3 Way 2 Block 0
Bad block mark is checked at: Ch 1 Way 3 Block 0
Bad block mark is checked at: Ch 3 Way 3 Block 0
Bad block mark is checked at: Ch 0 Way 0 Block 1
Bad block mark is checked at: Ch 1 Way 0 Block 1

...

Bad block mark is checked at: Ch 1 Way 0 Block 2112
Bad block mark is checked at: Ch 2 Way 0 Block 2112
Bad block mark is checked at: Ch 3 Way 0 Block 2112
Bad block mark is checked at: Ch 0 Way 1 Block 2112
Bad block mark is checked at: Ch 0 Way 2 Block 2112
Bad block mark is checked at: Ch 1 Way 2 Block 2112
Bad block mark is checked at: Ch 3 Way 2 Block 2112
Bad block mark is checked at: Ch 0 Way 0 Block 2113
Bad block mark is checked at: Ch 1 Way 0 Block 2113
Bad block mark is checked at: Ch 2 Way 0 Block 2113
Bad block mark is checked at: Ch 3 Way 0 Block 2113
Bad block mark is checked at: Ch 0 Way 1 Block 2113
Bad block mark is checked at: Ch 0 Way 2 Block 2113
Bad block mark is checked at: Ch 1 Way 2 Block 2113
Bad block mark is checked at: Ch 3 Way 2 Block 2113
Bad block mark is checked at: Ch 3 Way 0 Block 2114
Bad block mark is checked at: Ch 0 Way 2 Block 2114
Bad block mark is checked at: Ch 1 Way 2 Block 2114
Bad block mark is checked at: Ch 2 Way 2 Block 2114
Bad block mark is checked at: Ch 0 Way 3 Block 2114
[ Bad blocks are checked. ]
[ ssd entire block erasure completed. ]
[ ssd block map initialized. ]
[ ssd die map initialized. ]
[ ssd gc map initialized. ]
[ Initialization is completed. ]
[ Bad block size : 2228MB. ]
[ Storage size : 128810MB. ]

==============================================

Then, I followed next step. everything is OK

but, When I try Disk Formatting, "Type 'mkfs.ext4 /dev/pcissda1'

Following Message is appeared on UART Messages

==============================================
....
!!! a failure was detected in previous 2 operation - 0,0!!!
!!! a failure was detected in previous 2 operation - 3,0!!!
!!! a failure was detected in previous 2 operation - 0,1!!!
!!! a failure was detected in previous 2 operation - 0,0!!!
!!! a failure was detected in previous 2 operation - 3,0!!!
!!! a failure was detected in previous 2 operation - 0,1!!!
!!! a failure was detected in previous 2 operation - 0,0!!!
!!! a failure was detected in previous 2 operation - 3,0!!!
!!! a failure was detected in previous 2 operation - 0,1!!!
!!! a failure was detected in previous 2 operation - 0,0!!!
!!! a failure was detected in previous 2 operation - 3,0!!!
!!! a failure was detected in previous 2 operation - 0,1!!!
!!! a failure was detected in previous 2 operation - 0,0!!!
!!! a failure was detected in previous 2 operation - 3,0!!!
!!! a failure was detected in previous 2 operation - 0,1!!!
!!! a failure was detected in previous 2 operation - 0,0!!!
!!! a failure was detected in previous 2 operation - 3,0!!!
!!! a failure was detected in previous 2 operation - 0,1!!!
!!! a failure was detected in previous 2 operation - 0,0!!!
!!! a failure was detected in previous 2 operation - 3,0!!!
!!! a failure was detected in previous 2 operation - 0,1!!!
!!! a failure was detected in previous 2 operation - 0,0!!!
!!! a failure was detected in previous 2 operation - 3,0!!!
!!! a failure was detected in previous 2 operation - 0,1!!!
!!! a failure was detected in previous 2 operation - 0,0!!!
!!! a failure was detected in previous 2 operation - 3,0!!!
!!! a failure was detected in previous 2 operation - 0,1!!!
!!! a failure was detected in previous 2 operation - 0,0!!!
!!! a failure was detected in previous 2 operation - 3,0!!!
!!! a failure was detected in previous 2 operation - 0,1!!!
!!! a failure was detected in previous 2 operation - 0,0!!!
!!! a failure was detected in previous 2 operation - 3,0!!!
!!! a failure was detected in previous 2 operation - 0,1!!!
!!! a failure was detected in previous 2 operation - 0,0!!!
!!! a failure was detected in previous 2 operation - 3,0!!!
!!! a failure was detected in previous 2 operation - 0,1!!!
!!! a failure was detected in previous 2 operation - 0,0!!!
...
===========================================================
This message appears infinitely...

I hope you find solution

Thanks
Edited On 7:05:22 AM - Mon, Jul 6th 2015 by Chuminsung

Clicked A Few Times
Threads 2
Posts 24
Have you run the board with the greedy FTL whose version is lower than v1.1.0?

Bad block problem can occur when using the released FTL version after using old version.

Thanks.

Clicked A Few Times
Threads 2
Posts 9
Yes, I used the greedy_FTL_v1.0.0.

When I start OpenSSD project first, I could use the only one kind of version.

In My case, I already used v1.0.0

How to solve this problem?

Clicked A Few Times
Threads 2
Posts 24
File:Block clear.zip

Run the board with attached firmware and you can see following.
Ignore failure messages and their number can be different according to NAND flash module.




SSD firmware start -------




[ ssd NAND device reset complete. ]
!!! a failure was detected in previous 3 operation - 0,0!!!
!!! a failure was detected in previous 3 operation - 1,0!!!
!!! a failure was detected in previous 3 operation - 2,0!!!
!!! a failure was detected in previous 3 operation - 3,0!!!
!!! a failure was detected in previous 3 operation - 0,1!!!
!!! a failure was detected in previous 3 operation - 1,1!!!
!!! a failure was detected in previous 3 operation - 2,1!!!
!!! a failure was detected in previous 3 operation - 3,1!!!
!!! a failure was detected in previous 3 operation - 0,2!!!
!!! a failure was detected in previous 3 operation - 1,2!!!
!!! a failure was detected in previous 3 operation - 2,2!!!
!!! a failure was detected in previous 3 operation - 3,2!!!
!!! a failure was detected in previous 3 operation - 0,3!!!
!!! a failure was detected in previous 3 operation - 1,3!!!
!!! a failure was detected in previous 3 operation - 2,3!!!
!!! a failure was detected in previous 3 operation - 3,3!!!
!!! a failure was detected in previous 3 operation - 0,0!!!
!!! a failure was detected in previous 3 operation - 1,0!!!
!!! a failure was detected in previous 3 operation - 2,0!!!
!!! a failure was detected in previous 3 operation - 3,0!!!
!!! a failure was detected in previous 3 operation - 0,1!!!
!!! a failure was detected in previous 3 operation - 1,1!!!
!!! a failure was detected in previous 3 operation - 2,1!!!
!!! a failure was detected in previous 3 operation - 3,1!!!
!!! a failure was detected in previous 3 operation - 0,2!!!
!!! a failure was detected in previous 3 operation - 1,2!!!
!!! a failure was detected in previous 3 operation - 2,2!!!
!!! a failure was detected in previous 3 operation - 3,2!!!
!!! a failure was detected in previous 3 operation - 0,3!!!
!!! a failure was detected in previous 3 operation - 1,3!!!
!!! a failure was detected in previous 3 operation - 2,3!!!
!!! a failure was detected in previous 3 operation - 3,3!!!
!!! a failure was detected in previous 3 operation - 0,3!!!
!!! a failure was detected in previous 3 operation - 3,2!!!
!!! a failure was detected in previous 3 operation - 2,1!!!
!!! a failure was detected in previous 3 operation - 2,0!!!
!!! a failure was detected in previous 3 operation - 1,0!!!
!!! a failure was detected in previous 3 operation - 2,0!!!
!!! a failure was detected in previous 3 operation - 2,1!!!
!!! a failure was detected in previous 3 operation - 2,0!!!
!!! a failure was detected in previous 3 operation - 2,0!!!
!!! a failure was detected in previous 3 operation - 3,2!!!
!!! a failure was detected in previous 3 operation - 1,3!!!
!!! a failure was detected in previous 3 operation - 2,0!!!
!!! a failure was detected in previous 3 operation - 2,0!!!
!!! a failure was detected in previous 3 operation - 2,0!!!
[ ssd entire block erasure completed. ]
[ ssd block map initialized. ]


Then, run the greedy FTL v1.1.0 or later.
I'm sorry to confuse you.

Thanks.
Edited On 12:56:16 PM - Mon, Jul 6th 2015 by Enclab

Clicked A Few Times
Threads 2
Posts 9
I use "Block clear" firmware, but I still have same problem.

I tried following process, tell me why I fault.., please



First, I follow the all processes "Demo Guide" with "Block clear" firmware.

then, UART message is...




SSD firmware start -------




[ ssd NAND device reset complete. ]
[ ssd entire block erasure completed. ]
[ ssd block map initialized. ]

It is different from your messages. but I continue...


Second, I try same process with "greedy FTL v1.1.0"

(I make new workspace in SDK)

In this case, UART messages are the same when I don't use "Block clear" firmware.




SSD firmware start -------




[ ssd NAND device reset complete. ]
[ ssd page map initialized. ]
Bad block is detected on: Ch 1 Way 0 Block 0
Bad block is detected on: Ch 2 Way 0 Block 0
Bad block is detected on: Ch 3 Way 0 Block 0
Bad block is detected on: Ch 0 Way 1 Block 0
Bad block is detected on: Ch 1 Way 1 Block 0
Bad block is detected on: Ch 2 Way 1 Block 0
Bad block is detected on: Ch 3 Way 1 Block 0
Bad block is detected on: Ch 0 Way 2 Block 0
Bad block is detected on: Ch 1 Way 2 Block 0
Bad block is detected on: Ch 2 Way 2 Block 0
...
Bad block is detected on: Ch 0 Way 1 Block 2114
Bad block is detected on: Ch 1 Way 1 Block 2114
Bad block is detected on: Ch 2 Way 1 Block 2114
Bad block is detected on: Ch 3 Way 1 Block 2114
Bad block is detected on: Ch 0 Way 2 Block 2114
Bad block is detected on: Ch 1 Way 2 Block 2114
Bad block is detected on: Ch 2 Way 2 Block 2114
Bad block is detected on: Ch 0 Way 3 Block 2114
Bad block is detected on: Ch 1 Way 3 Block 2114
Bad block is detected on: Ch 2 Way 3 Block 2114
Bad block is detected on: Ch 3 Way 3 Block 2114
Bad block is detected on: Ch 0 Way 1 Block 2115
[ Bad block Marks are saved. ]
[ ssd entire block erasure completed. ]
[ ssd block map initialized. ]
[ ssd die map initialized. ]
[ ssd gc map initialized. ]
[ Initialization is completed. ]
[ Bad block size : 4268MB. ]
[ Storage size : 126770MB. ]

I really want to solve this problem.

If you need, I can shoot video that you can see my all process.

Thanks
Edited On 8:23:29 AM - Tue, Jul 7th 2015 by Chuminsung

Clicked A Few Times
Threads 2
Posts 24
Do you have another new NAND flash module?
This problem would be easily solved with the new one.

If you don't have any, I want to see the video which contains your all processes.

Thanks.
Edited On 11:10:25 AM - Tue, Jul 7th 2015 by Enclab

Clicked A Few Times
Threads 2
Posts 9
This problem is finally solved, Thanks!!!
Accoding to your answer,

I change the NAND flash module, and I use "greedy FTL v1.2.0", then Cosmos board is operated well.

but, when I use "greedy FTL v1.1.0", It's failed.

Thank you for your kindness.

Clicked A Few Times
Threads 2
Posts 24
I'm glad your problem is solved well.

But, I want to check one more thing.
Using new NAND flash module, which failure occurred with "greedy FTL v1.1.0"? same as previous one?


Forum >> Cosmos OpenSSD Platform >> Cosmos General Issues



Who's here now Members 0 Guests 0 Bots/Crawler 0


AWC's: 2.5.12 MediaWiki - Stand Alone Forum Extension
Forum theme style by: AWC
Views
Personal tools