May 24, 200719 yr For some reason, my unraid server can't get an ip address. I've turned DHCP off on my router, so I've already configured the network.cfg file manually, and I've also changed the workgroup in indent.cfg. I've also formatted the flash drive (a 512MB cruzer micro) with the HP formatting tool, and I made sure the name of the flash drive is 'UNRAID' Still, I get the "/boot/config/network.cfg: no such file or directory exists" etc errors that other people fixed by renaming the flash drive to 'UNRAID'. The NIC isn't dead, because I can manually assign it an ip address via command line and ping the server after I login. What step am I missing?
May 24, 200719 yr For some reason, my unraid server can't get an ip address. I've turned DHCP off on my router, so I've already configured the network.cfg file manually, and I've also changed the workgroup in indent.cfg. I've also formatted the flash drive (a 512MB cruzer micro) with the HP formatting tool, and I made sure the name of the flash drive is 'UNRAID' Still, I get the "/boot/config/network.cfg: no such file or directory exists" etc errors that other people fixed by renaming the flash drive to 'UNRAID'. The NIC isn't dead, because I can manually assign it an ip address via command line and ping the server after I login. What step am I missing? Everything you are describing would occur if the flash drive could not be mounted at /boot. only two causes I know for that are that the flash drive has U3 partitioning (or some other partitioning) on it and that it has more than one partition, unraid can't find the correct one to mount. or... the disk label on the flash drive is not set to UNRAID If your flash label (as set under windows) has the quotes you showed, or perhaps a trailing space, you might get the symptoms you described. Joe L.
May 24, 200719 yr Author I assume there's no other partition on the drive because I used the HP formatting tool (several times, both FAT and FAT32). There are no quotes around the flash label, and there are no trailing spaces. What else could prevent the flash drive to not be mounted at /boot? *edited for typo*
May 24, 200719 yr I assume there's no other partition on the drive because I used the HP formatting tool (several times, both FAT and FAT32). There are no quotes around the flash label, and there are no trailing spaces. The title is What else could prevent the flash drive to not be mounted at /boot? after you log in as root, type fdisk -l /dev/sda Odds are good it is at /dev/sda It will show you the partitioning... paste the results here and we will see... the HP tool probably does not have the ability to delete the U3 software present on some of the drives sold.
May 24, 200719 yr Author I tried that, and I just get the command line again. I tried fdisk /dev/sda and it said "unable to open..." Before I tried the HP formatting tool, nothing would boot at all. After I used the HP tool, it boots, but I guess it can't mount it. What else can I try?
May 24, 200719 yr type the following in a telnet window: cat /var/log/syslog Then copy the contents from the telnet window and paste it here... We can prorbably see what it is doing and what drive it thinks it is.
May 25, 200719 yr Right, need to see the syslog. Geek note: the flash does not necessarily show up as /dev/sda (under version 4.x). In an all-IDE system, yes it will, but if you have any SATA drives, it probably will not. This is the reason the Flash needs a volume label: in order for the software to determine which device is in fact the Flash after the system boots. Really geeky note: this has been a long-standing issue in linux (scsi device names changing) which has been solved pretty well by the 'udev' subsystem, which is now being used in unRAID. We use a 'udev' rule to assign the flash to /dev/flash based on volume label UNRAID. Really really geeky note: why does a USB Flash appear as a SCSI device in linux? That's a long story.....
May 27, 200719 yr I assume there's no other partition on the drive because I used the HP formatting tool (several times, both FAT and FAT32). There are no quotes around the flash label, and there are no trailing spaces. What else could prevent the flash drive to not be mounted at /boot? *edited for typo* The HP formatting tool will NOT remove the hidden partition from the Cruzer Micro. You have to go to their site and D/l this tool http://www.sandisk.com/Retail/Default.aspx?CatID=1415. I had the same problem.
May 29, 200719 yr Author thanks for the help guys. Unfortunately, it looks like the flash drive is bricked (good thing I picked it up for free from a friend) because I re-formatted with the HP tool, and the U3 Launchpad Removal Tool would just run ad infinitum, without actually doing anything. It's good to know what mistakes I made this time around though, so I don't repeat them in the future. And I was wondering why the flash drive was showing up as a SCSI device (thought that may have been the problem)...
May 31, 200719 yr Hello, I have a similar problem with a brand new Verbatim Professional stick. Here's what I'm getting: [...] Mounting non-root local filesystems: [] scsi 0:0:0:0: Direct-Access VBTM Sotre 'n' Go Pro 5.02 PQ: 0 ANSI: 0 CCS [] sd 0:0:0:0: Attached scsi removable disk sdd mount: special device /dev/desk/by-label/UNRAID does not exist Using /etc/random-seed to initialize /dev/urandom. INIT: Entering runlevel: 3 Going multiuser... Starting sysklogd daemons: /usr/sbin/syslogd -m0 /usr/sbin/klogd -c 3 -x /etc/rc.d/rc.inet1.conf: line 18: /boot/config/network.cfg: No such file or directory /etc/rd.c/rc.inet1.conf: line 19: /var/tmp/network.cfg: No such file or directory Welcome to Linux 2.6.20 (tty1) Tower login: I've used the HP format tool and the name is "UNRAID". As far as I know this specific USB stick doesn't have U3. Here's the syslog: USB hub found 2 ports detected Initializing USB Mass Storage driver... scsi0 : SCSI emulation for USB Mass Storage devices usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usb-storage: device found at 2 usb-storage: waiting for device to settle before scanning drivers/usb/input/hid-core.c: v2.6: USB HID core driver [...] scsi 0:0:0:0: Direct-Access VBTM Store 'n' Go Pro 5.02 PQ: 0 ANSI: 0 CCS sd 0:0:0:0: Attached scsi removable disk ssd usb-storage: device scan complete Here's what fdisk sais: Disc /dev/sdd: 521 MB, 521927192 bytes 17 heads, 59 sectors/track, 1016 cylinders Device Boot Start End Blocks Id System /dev/sdd1 * 1 1016 509494+ b W95 FAT32 Can anybody help me, please? Thanks!!
June 1, 200719 yr let's see what label it thinks you have on the flash drive... log in via telnet... then type; ls -l /dev/disk/by-label Report back what it says...
June 1, 200719 yr Here's what I get: /bin/ls: /dev/disk/by-lable: No such file or directory The same reply comes if I use "/dev/disk/blabla", so it seems to me that the tower doesn't understand this command. I did this directly on the tower by logging on as "root". Maybe I have to use telnet to use this command? I'm a total Linux noob. How can I make telnet work? I mean, due to because tower being unable to find the flash drive, the network is not up. Wouldn't the tower need to have an IP address for telnet to work? Thanks for your help!!
June 1, 200719 yr I've put in all new harddisks, none of which is partitioned/formatted yet. Would that cause "by-label" to fail working at all?
June 1, 200719 yr I'm sorry, that was a typo just here in the thread. I typed it correctly "label" when testing it. Just retried, just to be sure. Same result.
June 1, 200719 yr Some further results: (1) Removed all harddisks. No change. (2) Tested unRAID 3.0 and it finds the flash drive! I can do "cat /boot/config/network.cfg" and it shows me the correct contents of the network.cfg file. Unfortunately, unRAID 3.0 doesn't seem to support my motherboard's (Asus P5B-E) network chip. Here's some output of unRAID 3.0: /proc/scsi/scsi extensions not found. Fall back to scanning. Found /dev/scsi/sgh0-0c0i010 (Type 00) R on SCSI emulation for MSB Mass Storage devices Findscsidisk: 0 Another thing I noticed: With unRAID 3.0 the flash drive is "sda", with unRAID 4.0 the flash drive is "sdd", while "sda..sdc" are the 3 harddisks. In unRAID 3.0 the harddisks don't seem to be available at all. Maybe unRAID 3.0 also doesn't support my mainboard's SATA controller? Anyway, if unRAID 3.0 finds my USB stick, it is probably configured correctly - right? So why does unRAID 4.0 not find it?
June 1, 200719 yr Erase all on the flash, play stupid, print the instructions, and with a pen, tickmark every instructionstep. In troubleshooting: Assumtions are the mother of all mistakes. /Rene
June 1, 200719 yr Check your spelling of "label". Bill It looks like you mis-typed the command I suggested. It would work exactly the same logged in via the system console, or logged in via telnet.
June 1, 200719 yr Joe, I didn't mis-type. I repeatedly tried it again. Letter by letter as you told me. I only mis-typed the text I posted here in the forum. Anyway, I have new information, it's getting kind of crazy. This is what fdisk sais: Disc /dev/sdd: 521 MB, 521927192 bytes 255 heads, 63 sectors/track, 63 cylinders Device Boot Start End Blocks Id System /dev/sde1 * 1 64 509664 c W95 FAT32 (LBA) Now I've tried "mkdir /mnt/flash", followed by "mount -t vfat /dev/sde /mnt/flash". Here's what I got: mount: wrong fs type, bad option, bad superblock on /dev/sde, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so So I tried dmesg, here's the result: FAT: invalid media value (0xb9) VFS: Can't find a valid FAT filesystem on dev side This USB stock was compiled with the HP formatting tool. And now it gets even weirder: With unRAID 3.0 I can successfully mount this USB stick! I don't even have to use "-t vfat".
June 1, 200719 yr Argh, it's getting weirder every minute. Now I've formatted the flash inside of unRAID by using "mkdosfs" and it seemed to work just fine. Windows correctly handles this formatting, too. So I've done the usual syslinux + copying of unRAID to the flash. Booting up unRAID 4.0 works, but again UNRAID could not be found/mounted. This time mounting the stick manually with "-t vfat" works. However, fdisk now reports crazy results. fdisk finds lots of invalid partitions with crazy data. "ls -l /dev/disk/by-label" still doesn't work for me.
June 1, 200719 yr Sorry for posting so many comments. I hope you guys can bear with me... I've finally made some progress. I've partitioned and formatted the flash successfully from inside unRAID. Now I can perfectly mount it manually. And *THEN* also "ls -l /dev/disk/by-label" works!! Here's what I get now: lrwxrwxrwx 1 root root 10 Jun 1 10:51 UNRAID -> ../../sdd1 Unfortunately this only works after I manually mount partition 1 of the USB stick (partitions 2-4 are empty). It doesn't work without manual mounting. Because of that unRAID still doesn't boot up correctly. Shouldn't unRAID do the mounting automatically? Thanks guys. I'm dying to finally get unRAID to work.
June 1, 200719 yr Back to start, put your usbkey in your workstation: Do windows see it as a drive ? What filesystem does windows report it to have ? What label does it have ? Please dont assume, remember and speculate. Do, check and answer. /Rene
June 1, 200719 yr @Rene, XP sees it as FAT32, named "UNRAID". Linux (unRAID) does, too. Right now the only problem left seems to be that unRAID 4.0 doesn't automatically mount the stick for reasons unknown to me. FWIW, I've now also partitioned and formatted the 3 factory new harddisks the same way I did with the USB stick inside of unRAID with fdisk + mkdosfs. And unRAID 4.0 does mount these 3 harddisks automatically! And "ls -l /dev/disk/by-label" shows the harddisks, too. Linux/unRAID just doesn't mount my USB stick automatically, although it was partitioned and formatted exactly the same way as the harddisks. Again, unRAID 3.0 has no problems and automatically mounts my USB stick and detects it.
June 1, 200719 yr sorry for staying at the "bottom" :-). what is the effect of: same usb other hardware ? other usb, same hardware ? /Rene
Archived
This topic is now archived and is closed to further replies.