Unable to boot after adding 2nd HD

[theredballoon]

First, background info: Amahi is running on Ubuntu Server 12.04 LTS and I've been accessing through putty without issue (made adjustments per install page to /etc/network/interfaces) running on a headless server.

I'm trying to add a second hard drive and I followed the directions on https://wiki.amahi.org/index.php/Adding ... o_your_HDA and when I went to reboot, it doesn't seem to working (no access through putty, no response to ping). I tried removing the 2nd hard drive and rebooting without success. Figuring I must have screwed up the /etc/fstab file, I mounted the boot disk using an Ubuntu LiveCD and commented out the added UUID line on /etc/fstab, but I'm still unable to access the server via putty nor will the server respond to pings. I'm a little at loss what to do now. Any thoughts? Will I need to reinstall Ubuntu and Amahi, thereby wiping all the files I carefully moved onto the drive already (please say this is not the solution).

[bigfoot65]

First of all, always a good idea to make a backup of the /etc/fstab file before editing it. If the only line added was the one you commented out, then all should be working.

It is possible to correct the /etc/fstab but you need to know how it appeared before making edits. Maybe try removing that one line you added and reboot.

If that does not work, then you may have no other choice but to reinstall.

[theredballoon]

First of all, always a good idea to make a backup of the /etc/fstab file before editing it. If the only line added was the one you commented out, then all should be working.

It is possible to correct the /etc/fstab but you need to know how it appeared before making edits. Maybe try removing that one line you added and reboot.

If that does not work, then you may have no other choice but to reinstall.

Well I thought I did make a backup of the /etc/fstab file (per the instructions) but couldn't find it when I searched the drive and deleting the line didn't fix it, so... looks like i'm reinstalling. Fortunately, I have a second 1TB drive I can put the ubuntu/amahi on, so I won't lose the files on the one that's messed up. Well at least now I can fix the lack of partitioning for using greyhole.

[billium]

Might be a little late now that you're reinstalling, but in response to not being able to access through putty or not getting a response from ping -

In Ubuntu when you attempt to boot after installing new drives and having edited /etc/fstab, if you have monitor hooked up directly to the machine and a drive fails to mount a prompt will come up detailing which drive failed to mount and asking you to either skip or reattempt the mount. Because it was likely stuck in this state, you never got to a point where you could even ping the server. It's always a good idea when you're getting things set up to keep the server in an easily accessible place for instances just such as this.

Assuming your fstab file was correct and you added the drive properly, there's a chance that you did not create the mountpoint in your filesystem. Ubuntu will not mount a drive at a point where a directory does not already exist, so if you tried to mount via fstab at /var/hda/files/drives/drive1 and /var/hda/files/drives/drive1 does not exist as a directory, this problem will occur.

[theredballoon]

In Ubuntu when you attempt to boot after installing new drives and having edited /etc/fstab, if you have monitor hooked up directly to the machine and a drive fails to mount a prompt will come up detailing which drive failed to mount and asking you to either skip or reattempt the mount. Because it was likely stuck in this state, you never got to a point where you could even ping the server. It's always a good idea when you're getting things set up to keep the server in an easily accessible place for instances just such as this.

Assuming your fstab file was correct and you added the drive properly, there's a chance that you did not create the mountpoint in your filesystem. Ubuntu will not mount a drive at a point where a directory does not already exist, so if you tried to mount via fstab at /var/hda/files/drives/drive1 and /var/hda/files/drives/drive1 does not exist as a directory, this problem will occur.

Thanks for the info- I haven't actually started reinstalling at this point (waiting for a new SATA docking station), but I'm installing on a headless server (that doesn't have a monitor port), so I can't view startup errors. Once the new docking station comes, I'll try give this a try before I reinstall.

[theredballoon]

Well I reinstalled Ubunta/Amahi on the other hard drive (I'll call it drive B) and everything is working nice, but now I want to move the files from the old drive (drive A) onto the drive B. I recreated the shares via http://hda and then followed the directions to mount shares locally (https://wiki.amahi.org/index.php/Mount_Shares_Locally). I connected drive A via an external docking station and used usbmount to mount it (I think- at least I can see when I do fdisk -l). The problem i'm running into is that I can't seem to navigate to the location of all my files on the old hard drive (/var/hda/files) in order to copy them onto the new drive. I'll admit I know just enough about linux to well and truly break things, but I'm probably missing some step along the way.

Alternatively, a good way to mount the drive A on a Windows 7 machine and then I can just copy over to greyhole pool. I've tried linux reader (along with explore2fs) , but it doesn't seem to allow save directly from the mounted drive A to \\hda\music (for example). Sorry I'm a total failure..

[bigfoot65]

Sorry to hear you are having issues. One potential fix would be to boot the HDA via Ubuntu Live CD. You can then mount both drives and should be able to move files back and forth on the HDA with no issues.