Re: 30GB ZIF Hitachi drive in Creative Zen Vision M

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 6 Feb 2020, Samuel Sieb wrote:

On 2/6/20 3:57 PM, Max Pyziur wrote:
On Thu, 6 Feb 2020, Samuel Sieb wrote:
If that's the drive, then that's not looking good for getting anything off of it.  What does this show:
dd if=/dev/sdb bs=1K count=1 | od -a

1+0 records in
1+0 records out
0000000   K   L   B   M nul stx nul nul   @   >   ~ etx nul nul nul nul
1024 bytes (1.0 kB, 1.0 KiB) copied, 0.00131726 s, 777 kB/s
0000020 nul dle soh nul soh nul nul nul   m   i   n   i   f   s nul nul
0000040   ?   .   | etx soh dle soh nul   c   f   s nul nul nul nul nul
0000060 nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul

It turns out that the device uses a "special" filesystem. I recommend making a copy of the hard drive and working with that. Here's a script that looks like it can get the files off:
https://gist.github.com/joemck/483969

Much thanks for your help on this.

Some progress, but no recovery yet. The script does run for a while, the ZIF caddy light blinks like a typical drive light, and then it exits after a minute or so with the following message:
Traceback (most recent call last):
File "/home/pyz/projects/Documents/VideosMP3s/ZenRecover/zenrecover.py", line 251, in <module>
    raise "Could not find the root inode"
TypeError: exceptions must be old-style classes or derived from BaseException, not str

From reading the python script, it requires four command line arguments.
The first of these, the argument for the disk, requires an offset for the filesystem start.

So far, I've used /dev/sdb but have not specified an offset since the brief help screen indicates that the default offset is 20M.

I'm uncertain if this (not specifying the offset) is the cause of the error.

Thanks again,

M
pyz@xxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux