ott kernel: da0: WDC WD16 00BEVE-11UYT0 Fixed
Direct Access SCSI-0 device
Aug 10 18:23:57 ott kernel: da0: 40.000MB/s transfers
Aug 10 18:23:57 ott kernel: da0: 152627MB (312581808 512 byte sectors:
255H 63S/T 19457C)
Mounting the drive gives the following error:
# mount -t msdosfs /dev
On 10/08/2010 17:32, Ott Köstner wrote:
[...]
In the /var/log/messages the following message appears:
Aug 10 18:27:40 ott kernel: mountmsdosfs(): bad FAT32 filesystem
The drive is OK and works fine with Windows. Also, USB flash thumb
drives work fine, when used in the same manner with my
Antonio Vieiro wrote:
The fact that the drive is working on Windows does not mean it's FAT32
formatted. It may as well be NTFS formatted (man mount_ntfs).
Doublecheck you're running a FAT32 system: FreeBSD is saying you're not.
Thank You! Looks better now, but the volume is still unusable.
On Tue, Aug 10, 2010 at 11:37 AM, Ott Köstner o...@zzz.ee wrote:
Antonio Vieiro wrote:
The fact that the drive is working on Windows does not mean it's FAT32
formatted. It may as well be NTFS formatted (man mount_ntfs).
Doublecheck you're running a FAT32 system: FreeBSD is saying you're
Adam Vande More wrote:
On Tue, Aug 10, 2010 at 11:37 AM, Ott Köstner o...@zzz.ee wrote:
# df -H|grep da0
/dev/da0s1 160G 26G134G16%/mnt
...but all commands result with an error like this...
# ls -l /mnt/BACKUP
ls: /mnt/BACKUP: Argument list too long
That
On Tue, Aug 10, 2010 at 12:19 PM, Ott Köstner o...@zzz.ee wrote:
Adam Vande More wrote:
On Tue, Aug 10, 2010 at 11:37 AM, Ott Köstner o...@zzz.ee wrote:
# df -H|grep da0
/dev/da0s1 160G 26G134G16%/mnt
...but all commands result with an error like this...
# ls -l
Adam Vande More wrote:
On Tue, Aug 10, 2010 at 12:19 PM, Ott Köstner o...@zzz.ee wrote:
Adam Vande More wrote:
On Tue, Aug 10, 2010 at 11:37 AM, Ott Köstner o...@zzz.ee wrote:
# ls -ld /mnt/BACKUP
ls: /mnt/BACKUP: Argument list too long
Some directories are not big at
or use the 'force' option
ntfsmount -o force, or something like that
then, it would mount normally (without forcing)
btw, I didn't check, is ntfsprogs' mkntfs (or whatever the name) working
now?
Samuel Martín Moro
{EPITECH.} tek4
CamTrace S.A.S
(+033) 1 41 38 37 60
1 Allée de la Venelle
On Tue, Aug 10, 2010 at 1:13 PM, Ott Köstner o...@zzz.ee wrote:
2) After that...
# ntfsfix /dev/da0s1
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
NTFS volume version is 3.1.
NTFS partition /dev/da0s1 was processed successfully.
All ntfsfix does is mark
Adam Vande More wrote:
On Tue, Aug 10, 2010 at 1:13 PM, Ott Köstner o...@zzz.ee wrote:
2) After that...
# ntfsfix /dev/da0s1
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
NTFS volume version is 3.1.
NTFS partition /dev/da0s1 was processed successfully.
All
On Fri, 30 Mar 2007 18:54:13 +0200 Ivan Zenzerovi? [EMAIL PROTECTED]
wrote:
Ok, I think I understand, but tell me, is there any way I can read those
partitions from freebsd? If this helps, on that disk are no windows, there
are 3 ntfs partitions.
Ivan
On 3/30/07, Derek Ragona
Hi,
I'm trying to mount an ntfs drive with mount_ntfs. Now, the system sees the
second hard disk, but shows only one partition, ad1s1 wich is NTFS, but on
that disk there are 3 ntfs partitions and the system doesn't see them. On
windows they work fine.
Another thing, after a day or two I tried
You are able to mount the primary partition, not the extended
partitions. This is a also a limitation mounting ms-dos fat drives. The
extended partitions are done differently and are outside the partition table.
-Derek
At 07:58 AM 3/30/2007, =?ISO-8859-2?Q?Ivan_Zenzerovi=E6?= wrote:
Ok, I think I understand, but tell me, is there any way I can read those
partitions from freebsd? If this helps, on that disk are no windows, there
are 3 ntfs partitions.
Ivan
On 3/30/07, Derek Ragona [EMAIL PROTECTED] wrote:
You are able to mount the primary partition, not the extended
Not that I know of. The extended partitions are implemented as
linked-lists, and not in a partition table as standard partitions are and
the mount_ntfs is not written for the extended partitions.
You can move things back and forth using the one partition that you can access.
-Derek
Could I maybe fix this with trying to make the partitions again or something
like this from windows with partition magic? I supose that on the same way
freebsd does with it's partitions?
Ivan
On 3/30/07, Derek Ragona [EMAIL PROTECTED] wrote:
Not that I know of. The extended partitions are
You'd have to enlarge the primary partition and move the data from the two
extended partitions into that partition.
-Derek
At 12:27 PM 3/30/2007, =?ISO-8859-2?Q?Ivan_Zenzerovi=E6?= wrote:
Could I maybe fix this with trying to make the partitions again or something
like this from
Derek Ragona wrote:
You are able to mount the primary partition, not the extended
partitions. This is a also a limitation mounting ms-dos fat drives.
The extended partitions are done differently and are outside the
partition table.
-Derek
At 07:58 AM 3/30/2007,
out how I can overcome the windows XP limitation. I felt
that also I needed to understand what the term mounting a drive
actually meant, so that I could try to anticipate any unusual
behaviour, particularly with boot switching. From your email it
appears that mounting
. I felt
that also I needed to understand what the term mounting a drive
actually meant, so that I could try to anticipate any unusual
behaviour, particularly with boot switching. From your email it
appears that mounting implies letting the device driver know
I needed to understand what the
term mounting a drive
actually meant, so that I could try to
anticipate any unusual
behaviour, particularly with boot switching.
From your email it
appears that mounting implies letting the
device driver know the
address
Hallo
Could someone explain exactly what is meant by mounting a disk. I
understand that it is making a disk available for use, but would like
to understand the implications of the term and what abilities it
confers.
Part of the purpose of the question is that I am trying to find out
how
rs [EMAIL PROTECTED] wrote:
Could someone explain exactly what is meant by mounting a disk. I
understand that it is making a disk available for use, but would like
to understand the implications of the term and what abilities it
confers.
Hallo
Could someone explain exactly what is meant by mounting a disk. I
understand that it is making a disk available for use, but would like
to understand the implications of the term and what abilities it
confers.
Mounting connects the mount point to the device driver.
After the
[snip]
Hi and thanks for all help!
Seems like I have found a sollution (thanks to this excellent tutorial
http://freebsd.peon.net/tutorials/10/ and the help from the mailinglist
members):
One thing: I still don't understand how I should know that the device is
rda0 or rda0c or even da0
* Andreas Widerøe Andersen [2005-07-06 10:42 +0200]
Hi and thanks for all help!
Seems like I have found a sollution (thanks to this excellent tutorial
http://freebsd.peon.net/tutorials/10/ and the help from the mailinglist
members):
I didn't follow this thread from the beginning, so
Hi,
I'm having problems mounting a SCSI Iomega 100 Zip drive on my 4.11 RELEASE
system:
- From boot, this is what I see:
da0 at ncr0 bus 0 target 5 lun 0
da0: IOMEGA ZIP 100 E.08 Removable Direct Access SCSI-2 device
da0: 3.300MB/s transfers
da0: 96MB (196608 512 byte sectors: 64H 32S/T 96C)
On Tue, 05 Jul 2005 17:14:50 +0200
Andreas Widerøe Andersen [EMAIL PROTECTED] wrote:
Hi,
I'm having problems mounting a SCSI Iomega 100 Zip drive on my 4.11
RELEASE system:
- From boot, this is what I see:
da0 at ncr0 bus 0 target 5 lun 0
da0: IOMEGA ZIP 100 E.08 Removable Direct
At 17:19 05.07.2005, [EMAIL PROTECTED] wrote:
On Tue, 05 Jul 2005 17:14:50 +0200
Andreas Widerøe Andersen [EMAIL PROTECTED] wrote:
Hi,
I'm having problems mounting a SCSI Iomega 100 Zip drive on my 4.11
RELEASE system:
- From boot, this is what I see:
da0 at ncr0 bus 0 target 5 lun 0
Andreas Widerøe Andersen wrote:
At 17:19 05.07.2005, [EMAIL PROTECTED] wrote:
On Tue, 05 Jul 2005 17:14:50 +0200
Andreas Widerøe Andersen [EMAIL PROTECTED] wrote:
Hi,
I'm having problems mounting a SCSI Iomega 100 Zip drive on my 4.11
RELEASE system:
snip
did you try mounting it as
On Tue, Jul 05, 2005 at 05:44:17PM +0200, Andreas Wider?e Andersen wrote:
[...]
# mount /zip
mount: /dev/da0s4 on /zip: incorrect super block
Your ZIP disk hasn't been formatted as UFS, I would try `msdos'
instead.
--
Jonathan Chen [EMAIL PROTECTED]Once is dumb luck.
On Tue, 2005-07-05 at 15:35, Jonathan Chen wrote:
On Tue, Jul 05, 2005 at 05:44:17PM +0200, Andreas Wider?e Andersen wrote:
[...]
# mount /zip
mount: /dev/da0s4 on /zip: incorrect super block
Your ZIP disk hasn't been formatted as UFS, I would try `msdos'
instead.
Try mount -t msdos
hi there
how do I mount the hard drive from a live cd?
I\m using fressbie
thanks
=
_
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com
I found something funny regarding mounting floppy drive by normal user.
I set up everything needed for a normal user to mount a FDD according
to the handbook.
I booted up the box, type mount -t msdos /dev/fd0 ~/floppy and it
said I dont
have the permission. Then, I su and do that again
Hey,
I have a primary master disk drive which has winxp installed and is ad0s1
My secondary slave drive is ad2:
a) ad2s1 slice is a ntfs partition and
b) ad2s2a-f is freebsd!
I can mount without problems the ntfs slice ad2s1
When I try to mount my primary master which has xp installed I get the
35 matches
Mail list logo
