That was interesting...Are sure you have installed Openmediavault onto /dev/sdb as you said before?

I only had one drive connected up when I installed OMV which was the 10gb drive, I used the smallest drive I had available because as far as I understand the operating system uses the entire drive, the boot drive can't be partitioned, but knowing me I could have got things mixed up

Graeme

Logged

If you can keep your head while all around are losing theirs, then you're not quite grasping the situation

Just to clarify /dev/sda (80gb) was the original drive in what is now the NAS, it contained a Windows and Linux Partition, I removed that drive and connected a 10gb Drive (sdb) for the Openmediavault OS, I then re-connected the 80gb drive after the installation, that's how I know openmediavault is installed on the 10gb drive (sdb)

Hope that makes sense

Graeme

Logged

If you can keep your head while all around are losing theirs, then you're not quite grasping the situation

That was interesting...Are sure you have installed Openmediavault onto /dev/sdb as you said before?

I only had one drive connected up when I installed OMV which was the 10gb drive, I used the smallest drive I had available because as far as I understand the operating system uses the entire drive, the boot drive can't be partitioned, but knowing me I could have got things mixed up

Graeme

That is OK then It looks like the /sda1 & 5 are mounted by fstab (in a very complex way)You might have trouble untangling them

If you changed nothing in the BIOS .. my guess is the BIOS is looking for a bootloader on /dev/sda, then when it doesn't find one it moves on to /dev/sdb finds a bootloader and boots from it .. luckily the boot stanza is using UUID's to identify the partitions, not device names.

are both HDD's SATA or IDE ?

if IDE .. are they on the same ribbon cable or separate ones ?

[EDIT]

OK, ignore that last question .. just checked the model numbers .. the 10GB is IDE, the 80GB is SATA .. the BIOS is obviously set to boot SATA first.

Your best bet would be to boot a livecd .. format the 80GB drive how you want it (because it now doesn't appear to have any partitions).

then reboot without the LiveCD, and if the webUI won't mount it for you, mount the drive manually in fstab.

So if it's booting from HDD1 then it's booting off the 10gb drive (secondary slave) that I installed it on

Quote

OK, ignore that last question .. just checked the model numbers .. the 10GB is IDE, the 80GB is SATA .. the BIOS is obviously set to boot SATA first.

That's not correct both HDD's are IDE there are no SATA ports on the motherboard that I can see.

But clearly I've done something to the boot drive because now when I start the NAS the boot sequence stops with this message

Quote

failed (code8)File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. ...failed!A maintenance shell will now bw started . CONTROL-D will terminate this shell and resume system boot. ...(warning).give root password for maintence (or type CONTROL-D to continue): flashing cursor

pressing CONTROL-D lets it boot and I can log into the Web GUI as usual but obviously thats no good for a NAS as it has to be headless

My gut feeling here is that I screwed up the installation in the first place by not having an active internet connection because I was too impatient and too lazy to set up an ethernet connection, so why don't we start from scratch wipe both drives clean and re-install (this time with an internet connection) ?, It's my own fault and I really don't mind doing that .

Many Thanks

Graeme

« Last Edit: March 08, 2013, 09:54:17 am by Emegra »

Logged

If you can keep your head while all around are losing theirs, then you're not quite grasping the situation

For the sake of sanity .. change the jumpers on those 2 drives .. so -

10GB = Master80GB = Slave

You're right and it was my intention to do just that.

Quote

And have them both connected at installation.

I read in the Openmediavault Wiki to only have one drive installed and to add drives after installation of the operating system, that's why I did it that way, that and to eliminate any possibility of installing on the wrong drive.

Quote

BTW, there's probably no need to format and start again.

Probably not but to be honest I would be happier if I did, that's if you don't mind helping me install the USB wireless adaptor again

I have the option of installing the os to a usb drive and booting from that but on some tutorials I've read some recommend it and some don't, if I did it would free up an IDE channel which could be usefull, can you tell me what you're thoughts are on that ?

Many thanks

Graeme

Logged

If you can keep your head while all around are losing theirs, then you're not quite grasping the situation

I can see no reason not to bung it on a USB pendrive IF (and that's a big if) your system can bot from USB sticks .. install it as a "proper" installation though.

Erm .. thinking about it, if the system is low on RAM it might be better off on a HDD as heavy use of the swap partition may prematurely wear out a pendrive .. ideally you could add other drives through USB with some cheap enclosures (?).

[EDIT]

Unless you already have another large IDE drive .. you may be better off getting a SATA controller card which will allow you to add (but probably not boot from) SATA HDD's