I have a raid setup (/dev/md0) and decided I wanted to add another SATA drive to my system. I attached the same size drive and booted up. When trying to load, it crashes on loading /dev/md0 and drops to a busybox shell with initramfs. Disconnect the new drive, boots just fine. I have my raid setup on SATA 2-4. The new drive was being attached to SATA 1. Any ideas why I cannot add a new drive? And by new I mean brand spanking new, just bought it two days ago.
Added new HD and system crashed.
-
- OMV 2.x
- chillyw13
-
-
No one? Bueller? Bueller?
-
That is a very strange problem...
Check your sata cable.
Try putting the array on sata 1-3.
Check the settings in your bios. -
I'll try moving the drives over to the other SATA ports. Wasn't sure if doing that would break my raid or not.
-
raid uses the uuid of the drives. So, it doesn't matter what port it is on. I have moved raid arrays to different motherboards without issue before.
-
Ok, moved drives over to SATA 1 - 3. Added new drive on SATA 4. No dice. Repalce SATA cable, no dice. This is the output I get when I try to boot with the new drive installed.
-
I don't remember what kind of system this is? What is the boot drive and how is it connected? Are there only four total sata ports on the board? Are you using the backports kernel?
-
This is an OMV 2.1 straight up with Plex and Tvheadend installed. 4 SATA ports, 3 in use with Raid. The boot drive is a USB stick. No CDRom, no floppy. 600 watt power supply.
-
Install the backports kernel from omv-extras button in Kernel tab, shut the system down, install the 4th drive, turn it back on. See if that works.
-
So why would a backports kernel have anything to do with a new drive being installed? Just trying to understand what the underlying issue could be.
-
I would only add that if the drive you are adding is not brand new (as in it have been used before) I would try and do a full drive wipe on other compouter.
something like dd -if=?dev/null? for whole drive before adding to the system.
sometimes if drive have an MBR on it the system gets confused and try to boot from wrong drive -
I recommend a newer kernel because it has newer and/or better drivers that may eliminate the problem.
Wiping the drive is a good idea if you can put it in a different system to do that.
-
Hmmm...never thought of wiping it. I guess from the error, now that you mention it, the OS can't determine which one has the MBR on it. Not sure why that would be the case with a brand new drive, but it is possible.
-
A new drive probably has an MBR but it wouldn't be marked as bootable. While wiping doesn't hurt, I don't think it will fix this issue.
-
actually it depends on where you get the drive from.
some companies pre-format their drives before shipping.
also some bios, reset the boot order of the devices if proper HDD is detected on SATA-1.
I have a gigabyte MB that does just that. if I move my drives around and move the boot drive from SATA-1
I have to go into BIOS and specifically change my boot device to proper hard drive.
any other drives are fine, and if I leave SATA-1 empty it finds the boot drive ok too.
but if I connect anything to SATA-1 it assumes it is a preferred boot device regardless if there is no MBR or anything on it until I do a boot order change in BIOS.
exception to the rules is CD/DVD drive. if I have that connected to SATA-1 it will find the hard drive to boot from ok. but I always have my boot order like:
CD/DVD
USB
HDDso it works ok.
-
Tried to install backport, but it ended with errors, so never installed.
-
What were the errors?
-
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
firmware-linux : Depends: firmware-linux-nonfree (= 0.43~bpo70+1) but 0.36+wheezy.1 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). -
The backports repo didn't get added or apt-get update didn't work. What is the output of
cat /etc/apt/sources.list.d/backports.list
apt-get update -
deb http://ftp.debian.org/debian wheezy-backports main contrib non-free
deb http://packages.omv-extras.org/debian/ stoneburner-backports mainI ran apt-get -f install and retried. here is the output:
Updating...
Install backports 3.16 kernel and headers
Reading package lists...
Building dependency tree...
Reading state information...
linux-base is already the newest version.
initramfs-tools is already the newest version.
initramfs-tools set to manually installed.
The following packages were automatically installed and are no longer required:
libappconfig-perl libcxxtools8 libelf1 libextractor3 liblcms1 liblua5.1-0
libnspr4 libnss3 libopenjpeg2 libpcrecpp0 libpoppler19 librpm3 librpmio3
libtemplate-perl libtemplate-plugin-javascript-perl libtiff4 libtntnet10
sendemail vdradmin-am w-scan
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 64 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
firmware-linux-free is already the newest version.
linux-headers-3.16.0-0.bpo.4-amd64 is already the newest version.
linux-image-3.16.0-0.bpo.4-amd64 is already the newest version.
The following packages were automatically installed and are no longer required:
libappconfig-perl libcxxtools8 libelf1 libextractor3 liblcms1 liblua5.1-0
libnspr4 libnss3 libopenjpeg2 libpcrecpp0 libpoppler19 librpm3 librpmio3
libtemplate-perl libtemplate-plugin-javascript-perl libtiff4 libtntnet10
sendemail vdradmin-am w-scan
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
firmware-linux-nonfree
The following NEW packages will be installed:
firmware-linux
The following packages will be upgraded:
firmware-linux-nonfree
1 upgraded, 1 newly installed, 0 to remove and 63 not upgraded.
Need to get 0 B/2594 kB of archives.
After this operation, 3608 kB of additional disk space will be used.
(Reading database ... 54750 files and directories currently installed.)
Preparing to replace firmware-linux-nonfree 0.36+wheezy.1 (using .../firmware-linux-nonfree_0.43~bpo70+1_all.deb) ...
Unpacking replacement firmware-linux-nonfree ...
dpkg: error processing /var/cache/apt/archives/firmware-linux-nonfree_0.43~bpo70+1_all.deb (--unpack):
trying to overwrite '/lib/firmware/v4l-cx25840.fw', which is also in package dvb-firmware-osmc 1.0.1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Selecting previously unselected package firmware-linux.
Unpacking firmware-linux (from .../firmware-linux_0.43~bpo70+1_all.deb) ...
Errors were encountered while processing:
/var/cache/apt/archives/firmware-linux-nonfree_0.43~bpo70+1_all.deb
Creating index of upgradeable packages ...
Creating index of openmediavault plugins ...
E: Sub-process /usr/bin/dpkg returned an error code (1)
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!