unable to mount secondary hard disks now
Paul Root
ptroot at iaces.com
Wed Apr 6 15:35:33 PDT 2005
I just noticed, this isn't going to the group. Always, keep the thread
with the group. I
don't know everything. In fact, I haven't done usb disks on FreeBSD.
Anyway, there's a couple of disturbing things here.
1. You need to find out which drive is which. Because, what we do could
be distructive
to the disk. Especially if it's not the disk you think it is.
Run dmesg and look for the da device references, maybe that will give
you an idea
as to which disk is which.
Ok, let's assume for a minute that da2 became da1. That would explain
why the
disklabel is wrong. Since it was configured as da2c not da2s1c.
try
disklabel da1
disklabel da2
disklabel da1s1
disklabel da2s1
mount
let's see what's what.
2. That disklabel is wrong. That's why you can't access the partition.
Back in the old days, it
was frowned upon to use 'C' as a live filesystem. It was always the
whole disk. I generally will
make an 'a' or 'e' or something that is also the whole disk
There are 2 problems with this disklabel, if it is the right disk.
1. The file type is unused. It should be 4.2BSD
2. The C partition extends past the end of the unit. That's probably
because it starts at 63
instead of 0. Which actually leads me to believe that this is the old da2.
Run the dmesg, disklabels and mount for us (the whole list, I can easily
miss things). And see
if we can't figure out what drive is what.
Paul.
Shea Frederick wrote:
>FileServer# disklabel /dev/da1s1c
># /dev/da1s1c:
>8 partitions:
># size offset fstype [fsize bsize bps/cpg]
> c: 156296322 63 unused 0 0 # "raw" part,
>don't edit
>partition c: partition extends past end of unit
>disklabel: partition c doesn't start at 0!
>disklabel: An incorrect partition c may cause problems for standard
>system utilities
>
>but something else interesting came up while i was poking around.....I
>went to write some files to my da2 drive, and noticed that the access
>light on drive da1 was blinking. So somehow after re-booting, my da1
>and da2 drives switched places (i sware i didnt switch the cables)
>
>-Shea
>
>
>On Apr 6, 2005 2:28 PM, Paul T. Root <ptroot at iaces.com> wrote:
>
>
>>Ok, so that was a bad guess.
>>
>>The disk may have gotten wiped. You can try running
>>fsck with the next superblock.
>>
>>fsck -b 32 /dev/da1s1c
>>
>>What does disklabel give you?
>>disklabel da1s1
>>
>>
>>Shea Frederick wrote:
>>
>>
>>>The first drive (da0) was setup using the instructions here...
>>>
>>>http://www.freebsd.org/doc/en_US.ISO8859-1/articles/formatting-media/article.html
>>>
>>>The 2nd drive (da1) was setup using sysinstall
>>>
>>>come to think of it, thats the only difference, so maybee thats part
>>>of the problem.
>>>
>>>I have no da1s4c
>>>
>>>FileServer# ll /dev/da*
>>>crw-r----- 1 root operator 4, 19 Apr 6 22:59 /dev/da0
>>>crw-r----- 1 root operator 4, 23 Apr 6 17:01 /dev/da0c
>>>crw-r----- 1 root operator 4, 20 Apr 6 22:59 /dev/da1
>>>crw-r----- 1 root operator 4, 65 Apr 6 22:59 /dev/da1a
>>>crw-r----- 1 root operator 4, 66 Apr 6 22:59 /dev/da1c
>>>crw-r----- 1 root operator 4, 34 Apr 6 22:59 /dev/da1s1
>>>crw-r----- 1 root operator 4, 55 Apr 6 22:59 /dev/da1s1c
>>>crw-r----- 1 root operator 4, 21 Apr 7 04:38 /dev/da2
>>>crw-r----- 1 root operator 4, 69 Apr 7 04:39 /dev/da2c
>>>
>>>I forgot to mention that drive 3 (setup just like da0) also works fine
>>>
>>>-Shea
>>>
>>>
>>>On Apr 6, 2005 1:42 PM, Paul T. Root <ptroot at iaces.com> wrote:
>>>
>>>
>>>
>>>>I'm not entirely sure, but it sure looks like da1s4c to me.
>>>>
>>>>Why is one drive da0c and the other da1s1c? How did you set them
>>>>up?
>>>>
>>>>Shea Frederick wrote:
>>>>
>>>>
>>>>
>>>>>Im running FreeBSD 5.3, its an almost fresh install. Its been running
>>>>>for about 7 days now. I have an internal IDE drive that the OS runs
>>>>>from, then I have two external firewire drives (da0, da1) that are
>>>>>only used as Samba shares.
>>>>>
>>>>>This morning i found that one of the firewire drives are no longer
>>>>>mounted (da1), this might have happened when I uninstalled Samba 2.x
>>>>>and installed 3.x yesterday, then rebooted. but im not sure, because i
>>>>>didnt check to see if the drive was still mounted after the reboot.
>>>>>
>>>>>So i figured i would just mount it again (even though da1 in the fstab)....
>>>>>
>>>>>FileServer# mount /dev/da1s1c /mnt/jabba
>>>>>mount: /dev/da1s1c on /mnt/jabba: incorrect super block
>>>>>
>>>>>So now im not realy sure what to do, this drive was working perfectly
>>>>>before the reboot.
>>>>>
>>>>>someone told me to run fsck on the drive, but that gives me the following error.
>>>>>
>>>>>FileServer# fsck /dev/da1s1c
>>>>>** /dev/da1s1c
>>>>>Cannot find file system superblock
>>>>>/dev/da1s1c: NOT LABELED AS A BSD FILE SYSTEM (unused)
>>>>>
>>>>>here is what fdisk returns...
>>>>>
>>>>>FileServer# fdisk /dev/da1s1c
>>>>>******* Working on device /dev/da1s1c *******
>>>>>parameters extracted from in-core disklabel are:
>>>>>cylinders=9728 heads=255 sectors/track=63 (16065 blks/cyl)
>>>>>
>>>>>Figures below won't work with BIOS for partitions not in cyl 1
>>>>>parameters to be used for BIOS calculations are:
>>>>>cylinders=9728 heads=255 sectors/track=63 (16065 blks/cyl)
>>>>>
>>>>>Media sector size is 512
>>>>>Warning: BIOS sector numbering starts with sector 1
>>>>>Information from DOS bootblock is:
>>>>>The data for partition 1 is:
>>>>><UNUSED>
>>>>>The data for partition 2 is:
>>>>><UNUSED>
>>>>>The data for partition 3 is:
>>>>><UNUSED>
>>>>>The data for partition 4 is:
>>>>>sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
>>>>> start 0, size 50000 (24 Meg), flag 80 (active)
>>>>> beg: cyl 0/ head 0/ sector 1;
>>>>> end: cyl 1023/ head 254/ sector 63
>>>>>
>>>>>Here are the relevant lines from my fstab...
>>>>>/dev/da0c /mnt/yoda ufs rw 2 2
>>>>>/dev/da1s1c /mnt/jabba ufs rw 2 2
>>>>>
>>>>>Thanks in advance
>>>>>
>>>>>
>>>>>
>>
>>
More information about the freebsd-questions
mailing list