Ok I'm the village idiot..... How could I have missed something so simple, it was right there in front of my eyes.....
Thank you soooo much Charles, I just assumed bering had the ext3 fs compiled into the kernel, as soon as I loaded up jdb and ext3 modules, I re formatted at the device level /dev/sdb and it mounted perfectly. I only have one minor issue left, I tried adding ext3 and jdb into initrd.lrp but it broke the booting (it doesn't seem to create the ram disk file system), so I put them back into /lib/modules and added them to /etc/modules list, but again at boot up it doesn't seem to want to load them. If I login and do it manually via insmod etc it works fine. This is my /var/log/messages Dec 6 14:33:00 nas kernel: USB Mass Storage support registered. Dec 6 14:33:00 nas kernel: hub.c: new USB device 00:1d.0-1, assigned address 2 Dec 6 14:33:00 nas kernel: hub.c: new USB device 00:1d.2-1, assigned address 2 Dec 6 14:33:00 nas kernel: scsi0 : SCSI emulation for USB Mass Storage devices Dec 6 14:33:00 nas kernel: Partition check: Dec 6 14:33:00 nas kernel: sda: sda1 Dec 6 14:33:00 nas root: modutils module jdb could not be loaded Dec 6 14:33:00 nas root: modutils module ext3 could not be loaded Dec 6 14:33:00 nas kernel: Intel(R) PRO/100 Network Driver - version 2.3.43-k1 Dec 6 14:33:00 nas kernel: Copyright (c) 2004 Intel Corporation Dec 6 14:33:00 nas kernel: Dec 6 14:33:00 nas kernel: PCI: Found IRQ 11 for device 01:08.0 Dec 6 14:33:01 nas kernel: e100: eth0: Intel(R) PRO/100 Network Connection Dec 6 14:33:01 nas kernel: Hardware receive checksums enabled Anyone have any ideas why it can't load those 2 modules during boot up? Cheers Ad P.S Thanks again Charles I'm a very happy camper, my nice little 1TB (well 916.8G usable, *damn maths*) home NAS it's up and humming along just nicely. Sub 30seconds from turn on to being online (it boots from a usb stick). -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Charles Steinkuehler Sent: Thursday, 6 December 2007 2:09 PM To: Adam Niedzwiedzki Cc: leaf-user@lists.sourceforge.net Subject: Re: [leaf-user] HighPoint RocketRAID 174x (need help in formating/mounting the RAID) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adam Niedzwiedzki wrote: > Yeah that's what I thought, very weird.... > > nas# dd if=/dev/sdb1 of=/dev/null bs=512 count=256 > 256+0 records in > 256+0 records out > > nas# dd if=/dev/zero of=/dev/sdb1 bs=512 count=256 > 256+0 records in > 256+0 records out > > As for trying a statically built version of mount, that's a bit out of my > league.. I wouldn't know where/how to do that :( > > I'm only a semi-beginner with this stuff. One more wacky suggestion. Double and triple check the device files in /dev, making sure the sdb* entries in particular look correct. Check for the device type, major/minor device numbers, permissions, etc. You might also try making another device file for /dev/sdb1 somewhere other than /dev/, for instance: mknod /root/mytestdev b 8 16 mknod /root/mytestdev1 b 8 17 ...which correspond to /dev/sdb and /dev/sdb1, respectively. Then try: mount -t ext3 /root/mytestdev1 /mnt It's a long shot, but the problem could be something with your device files, rather than with the mount command... One more wacky idea: Call busybox directly, bypassing whatever symlinks you have setup. Typically something like the following, but I don't have a bering system on-line for testing, so paths may be wrong: /bin/busybox mount -t ext3 /dev/sdb1 /mnt And the final grasping at straws idea before I go to bed: You *DO* have the ext3 file-system driver loaded into the kernel, right? I don't think this is required for formatting, but *IS* required for mounting the partition (obviously). Bering doesn't include the ext3 filesystem compiled into the kernel, unlike most 'mainstream' (ie: HDD based) distributions. Check the installed filesystems using: cat /proc/filesystems ...sometimes the busybox error messages are less than intuitive, particularly for code paths that don't see a lot of use, so your "No such device" message could really mean "Couldn't mount because of some error", with no such device simply being the most common case. - -- Charles Steinkuehler [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHV2e0LywbqEHdNFwRAodIAJ9x6QtKxQdaFzCzIlLHXgvzEQSX2gCg+DN6 G7ZS8Tnfi73o9JzLPgu/eDE= =yAcY -----END PGP SIGNATURE----- ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/ ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
