Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In my experience I recover low level storages (think dd or lower) in consumer and professional cameras, and cell phones.

I still find errors in FAT32 implementation when it comes to cameras, while phones have moved on to get specialized formats depending on the storage chips' design.

Cameras' firmware are decades behind.



>I still find errors in FAT32 implementation

I wonder if this results in issues when you plug a card into Windows, which then 'fix' the incorrect FAT32 data structures on the disk, which again will be corrupted by the camera in new and interesting ways.


Does it make your life easier or harder? (How easier is it to recover from FAT32 than from "specialized format")?

Does specialized format means you don't ever need to recover from them or noticeably less?


> Does it make your life easier or harder?

It makes my life harder because recovery has to be manually adjusted to work with the incorrect implementation.

It also makes the owners' life harder too. older file systems are not geared for chips and thrash the storage, making them fail significantly faster, be it removable or built-in.

> Does specialized format means you don't ever need to recover from them or noticeably less?

For my context, I recover them for forensics purposes. When I wrote "specialized format" (e.g., JFFS2, YaFFs, Target, F2F2, UBIFS) I was referring storage formats geared towards chip vs disk. mobile phones tend to be very easy to recover; almost plug-and-play. They are often are hardware modules where the entire storage can be removed, and connected through common, physical connectors to recovery device.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: