Date: Mon, 21 May 2007 12:03:45 -0700 From: "Yanko Sanchez" <y@rem7.cc> To: "Garrett Cooper" <youshi10@u.washington.edu> Cc: questions@freebsd.org, Duane Hill <d.hill@yournetplus.com> Subject: Re: disk too big to mount Message-ID: <4d9d444a0705211203j7d9f508dn15070786a1f38751@mail.gmail.com> In-Reply-To: <4d9d444a0705211116j5fd6ca35o576c3cfa0df23bc3@mail.gmail.com> References: <4d9d444a0705201804yccf5975l206a75e889dd1a41@mail.gmail.com> <20070521113942.A38110@duane.dbq.yournetplus.com> <4651B6F4.5030007@u.washington.edu> <4d9d444a0705211116j5fd6ca35o576c3cfa0df23bc3@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for anyone that has helped so far, I'm a freebsd newbie coming from linux. So I basically re-compiled my kernel with the LARGE option on and it seems to mount the drive fine. I encountered another problem tho. Before I recompiled the kernel I updated the ports tree, basically cos I just wanted to see how it was done and it seemed to be successful. The problem is that after I recompiled the kernel a bunch of stuff stoped working. I have the server setup as a router and my to Network cards isn't showing up anymore (both being the same type of cards, I use to have rl0 and rl1) so It isn't routing anymore, and now im getting a bunch of DHCPREQUEST messages on startup which I wasn't getting before. And other errors saying that my network card isn't configured. I checked /etc/rc.conf and the lines for ifconfig are still in there... Did I upgrade the kernel sources by doing an upgrade to the ports? That would make sense, but what bugs me is that I copied the same kernel config and just added the MSDOSFS_LARGE option once I booted up I got the errors mentioned above. Shouldn't it have stayed pretty much the same? I'm just trying to get a better understand if what happened to that I don't make the same mistake. On 5/21/07, Yanko Sanchez <y@rem7.cc> wrote: > because when the hdd was first formated it was inside of a PowerPC and > we knew that it was going to be on a server but we didn't know of what > kind so we just formated FAT32. I don't really care what the fomrmat > it is, if I could switch it to UFS I'd do it, but I need a hdd as big > as that one to copy the files and then be able to reformat with a new > FS. > > On 5/21/07, Garrett Cooper <youshi10@u.washington.edu> wrote: > > Duane Hill wrote: > > > Disreguard my previous response. I didn't see your next response to Ray. > > > Sorry. > > > > > > On Sun, 20 May 2007, Yanko Sanchez wrote: > > > > > >> Hello, > > >> > > >> I have a 400GB seagate IDE hdd with backed up data that I need to load > > >> onto > > >> a machine running freebsd 6.2 > > >> > > >> The drive is formated for fat32 and when I run the command: > > >> > > >> mount -t msdos /dev/ad2s2 /mnt/audio/ > > >> > > >> I get the following error: > > >> > > >> "mountmsdosfs(): disk too big, sorry" > > >> > > >> Is there a solution to this? > > >> Thanks. > > > > Why on earth would you want to create a 400GB MSDOSFS formatted disk? > > MSDOSFS was quick but offered no protection against power outages or > > incomplete writes, and was horrible in terms of disk fragmentation.. > > > > If you really want MSDOSFS for whatever reason, just break up the disk > > into smaller chunks partition-wise (IIRC 100GB chunks are fine). > > > > -Garrett > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4d9d444a0705211203j7d9f508dn15070786a1f38751>