Professional Web Applications Themes

unable to mount secondary hard disks now - FreeBSD

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 ...

  1. #1

    Default unable to mount secondary hard disks now

    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
    -Shea
    Shea Guest

  2. #2

    Default Re: unable to mount secondary hard disks now

    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: 


    --
    ______ Paul T. Root
    / _ \ 1977 MGB
    / /|| \\
    ||\/ || _ |
    || || ||
    \ ||__//
    \______/

    Paul Guest

  3. #3

    Default Re: unable to mount secondary hard disks now

    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:
     
    >>
    >>[/ref][/ref]


    Paul Guest

Similar Threads

  1. Unable to connect to secondary site on shared hostingpackage
    By Fastdad2221 in forum Macromedia Contribute Connection Administrtion
    Replies: 0
    Last Post: January 29th, 01:57 PM
  2. Mount hard drive
    By Cueless in forum Ubuntu
    Replies: 8
    Last Post: November 10th, 11:12 PM
  3. Cant see secondary hard disk
    By renzki in forum Windows Server
    Replies: 4
    Last Post: August 26th, 09:58 PM
  4. WIN XP - How Do You Secure A Secondary Hard Drive
    By Miha in forum Windows Setup, Administration & Security
    Replies: 3
    Last Post: July 28th, 01:26 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139