public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Andy Kennedy <akennedy@techmoninc.com>
To: linux-mtd@lists.infradead.org
Subject: Re: DiskOnChip 2000 (DOC 2000) woes.
Date: Thu, 09 Aug 2007 12:06:21 -0500	[thread overview]
Message-ID: <46BB498D.9040707@techmoninc.com> (raw)
In-Reply-To: <46BB21F1.3060109@techmoninc.com>

More information:

An oops on my locale computer as I was attempting to make a jumpdrive 
back to an vfat filesystem.  I needed to recreate the partition so I 
typed the following:

root@Andy:/# fdisk /dev/sdb1

Obliviously my mistake is just adding the partition number to the device 
-- it happens.  I get the following error:

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF 
disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.

Warning: invalid flag 0x0000 of partition table 4 will be corrected by 
w(rite)


I quit out of it but realize that this is the SAME error that I get on 
the DiskOnChip.  So, to me it looks like I'm hitting the first partition 
of the nftl in place of the device base.  This is the command I use:


root@winsys:~# modprobe nftl
root@winsys:~# fdisk /dev/nftla

And here are the results:

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF 
disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.

Warning: invalid flag 0x0000 of partition table 4 will be corrected by 
w(rite)

Command (m for help): q


So, am I getting the wrong device from the driver?  I cannot update the 
partition table on this unit -- it would make sense to me if I'm 
attempting to put a partition on the device /dev/nftla1 in place of 
/dev/nftla.  I created the block devices nftla{,1,2} using:
mknod /dev/nftla b 93 0
and I end up with a device:
brw-rw---- 1 root disk 93, 0 2007-08-09 10:52 /dev/nftla
So, am I seeing a driver error or am I the error?

Any help would be greatly appreciated.

Andy

  reply	other threads:[~2007-08-09 17:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06 18:57 DiskOnChip 2000 (DOC 2000) woes Andy Kennedy
2007-08-06 22:03 ` Andy Kennedy
2007-08-08 16:26 ` Andy Kennedy
2007-08-08 17:03   ` Bob Beers
     [not found]     ` <46BA05D6.4080605@techmoninc.com>
2007-08-08 19:30       ` Bob Beers
2007-08-09 14:17   ` Andy Kennedy
2007-08-09 17:06     ` Andy Kennedy [this message]
2007-08-09 17:52       ` Bob Beers
2007-08-09 18:00         ` Andy Kennedy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46BB498D.9040707@techmoninc.com \
    --to=akennedy@techmoninc.com \
    --cc=linux-mtd@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox