Re: [digital-curation] Digest for digital-curation@googlegroups.com - 4 Messages in 1 Topic

37 views
Skip to first unread message

Doug Reside

unread,
Apr 27, 2012, 8:12:34 AM4/27/12
to digital-...@googlegroups.com

Is it a double density disk?  is there a hole at the  top directly across from the write protect tab?

On Apr 27, 2012 6:18 AM, <digital-...@googlegroups.com> wrote:

Group: http://groups.google.com/group/digital-curation/topics

    "Gueguen, Gretchen (gmg2n)" <gm...@eservices.virginia.edu> Apr 26 06:21PM  

    A question for anyone with more experience in disk imaging than me:
     
    I'm imaging some rather old 3.5" floppy disks (late-80s to early 90s) using FTK Imager. A handful of them do not have a recognized file system. Imager can successfully create an image, but the data in the image is completely blank (the hex file just shows all zeros).
     
    Am I correct in thinking then that these disks have been corrupted or wiped? Even though my operating system can't recognize a file system, the imaging software should still image whatever data is still there (if there is any), correct? Or should I be using some other method to image these disks?
     
    Thanks,
     
    Gretchen Gueguen
    Digital Archivist
    Albert and Shirley Small Special Collections Library
    University of Virginia
    PO Box 400110
    Charlottesville, VA 22904
    (434) 924-4073

     

    "Mark A. Matienzo" <mark.m...@gmail.com> Apr 26 03:02PM -0400  

    Hi Gretchen,
     
    On Thu, Apr 26, 2012 at 2:21 PM, Gueguen, Gretchen (gmg2n)
    > Even though my operating system can’t recognize a file system, the imaging
    > software should still image whatever data is still there (if there is any),
    > correct? Or should I be using some other method to image these disks?
     
    If I recall correctly, FTK Imager ultimately relies on the controller
    for the floppy drive to assist with interpreting the information on
    the media. If you're using a USB floppy drive, it may be able to image
    the disk "successfully."
     
    I'd try imaging the disk using another solution (i.e. Catweasel,
    KryoFlux, etc.) and see what you've got.
     
    Mark
     
    --
    Mark A. Matienzo
    Digital Archivist, Manuscripts and Archives, Yale University Library
    Technical Architect, ArchivesSpace

     

    Kam Woods <kamw...@gmail.com> Apr 26 03:13PM -0400  

    Slightly OT but if you're not currently a KryoFlux user (or dislike
    closed hardware solutions) there's a new(er) open source project,
    DiskFerret, that appears to be ramping up for distribution this
    summer. Hardware, firmware, software all available via the project
    page http://discferret.com/wiki/DiscFerret
     
    On Thu, Apr 26, 2012 at 3:02 PM, Mark A. Matienzo

     

You received this message because you are subscribed to the Google Group digital-curation.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

--
You received this message because you are subscribed to the Google Groups "Digital Curation" group.
To post to this group, send email to digital-...@googlegroups.com.
To unsubscribe from this group, send email to digital-curati...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/digital-curation?hl=en.

Gueguen, Gretchen (gmg2n)

unread,
Apr 30, 2012, 9:23:51 AM4/30/12
to digital-...@googlegroups.com

I’m having this problem with multiple disks. Some are high density, some double density. Some have the write protect tab punched, some don’t. I’ve also successfully imaged many identical disks, it just seems like the file system is corrupted on these. I’m wondering why my images are completely blank as if the disks have been wiped – if they really are blank or if the software/controller card won’t read them if it can’t detect the file system.

 

Thanks,

 

-Gretchen

Seth Shaw

unread,
May 2, 2012, 11:30:12 AM5/2/12
to digital-...@googlegroups.com
I have had a number of disks that show up seemingly completely wiped
as well using both FTK Imager (USB floppy drive attached) and our
Kryoflux; so what you're seeing certainly isn't unusual. I haven't
been able to find a satisfactory explanation though. Disks such as
these have been written off as DOA.

Elinor Robinson

unread,
May 31, 2012, 7:46:43 AM5/31/12
to Digital Curation
I had a similar issue with DD disks, as my external USB floppy drive
couldn't read them, it only specs for HD 1.4 MB disks. Tried the same
DD disks in an internal disk drive on another machine and FTK Imager
processed them fine.

All best,

Ellie

On Apr 27, 1:12 pm, Doug Reside <dougres...@gmail.com> wrote:
> Is it a double density disk?  is there a hole at the  top directly across
> from the write protect tab?
> On Apr 27, 2012 6:18 AM, <digital-...@googlegroups.com> wrote:
>
>
>
>
>
>
>
> >   Today's Topic Summary
>
> > Group:http://groups.google.com/group/digital-curation/topics
>
> >    - disk imaging <#136f34ef51761e47_group_thread_0> [4 Updates]
>
> >   disk imaging<http://groups.google.com/group/digital-curation/t/190172c4a07da453>
>
> >    "Gueguen, Gretchen (gmg2n)" <gm...@eservices.virginia.edu> Apr 26
> >    06:21PM
>
> >    A question for anyone with more experience in disk imaging than me:
>
> >    I'm imaging some rather old 3.5" floppy disks (late-80s to early 90s)
> >    using FTK Imager. A handful of them do not have a recognized file system.
> >    Imager can successfully create an image, but the data in the image is
> >    completely blank (the hex file just shows all zeros).
>
> >    Am I correct in thinking then that these disks have been corrupted or
> >    wiped? Even though my operating system can't recognize a file system, the
> >    imaging software should still image whatever data is still there (if there
> >    is any), correct? Or should I be using some other method to image these
> >    disks?
>
> >    Thanks,
>
> >    Gretchen Gueguen
> >    Digital Archivist
> >    Albert and Shirley Small Special Collections Library
> >    University of Virginia
> >    PO Box 400110
> >    Charlottesville, VA 22904
> >    (434) 924-4073
>
> >    "Mark A. Matienzo" <mark.matie...@gmail.com> Apr 26 03:02PM -0400
>
> >    Hi Gretchen,
>
> >    On Thu, Apr 26, 2012 at 2:21 PM, Gueguen, Gretchen (gmg2n)
> >    > Even though my operating system can’t recognize a file system, the
> >    imaging
> >    > software should still image whatever data is still there (if there
> >    is any),
> >    > correct? Or should I be using some other method to image these disks?
>
> >    If I recall correctly, FTK Imager ultimately relies on the controller
> >    for the floppy drive to assist with interpreting the information on
> >    the media. If you're using a USB floppy drive, it may be able to image
> >    the disk "successfully."
>
> >    I'd try imaging the disk using another solution (i.e. Catweasel,
> >    KryoFlux, etc.) and see what you've got.
>
> >    Mark
>
> >    --
> >    Mark A. Matienzo
> >    Digital Archivist, Manuscripts and Archives, Yale University Library
> >    Technical Architect, ArchivesSpace
>
> >    Kam Woods <kamwo...@gmail.com> Apr 26 03:13PM -0400
>
> >    Slightly OT but if you're not currently a KryoFlux user (or dislike
> >    closed hardware solutions) there's a new(er) open source project,
> >    DiskFerret, that appears to be ramping up for distribution this
> >    summer. Hardware, firmware, software all available via the project
> >    pagehttp://discferret.com/wiki/DiscFerret
> > You can post via email <digital-...@googlegroups.com>.
> > To unsubscribe from this group, send<digital-curati...@googlegroups.com>an empty message.
> > For more options, visit<http://groups.google.com/group/digital-curation/topics>this group.
Reply all
Reply to author
Forward
0 new messages