Okay I shouldn’t have been messing with the software, but it was just so tempting because I’ve been doing a lot of server work on a Debian server, and when I discovered MBL is running Debian I just couldn’t resist adding features. I started out with adding a few simple commands like ftp and screen. (Screen and a few other commands are really useful for moving files directly from one MBL to another without running the data through your computer.) Then I began writing PHP scripts (I do a lot of website design) and ended up writing a whole suite of very useful tools. Then came the straw that broke the camel’s back. I wanted to write a PHP script to unzip an archive (no problem) and downsize the images to lower resolution, then zip them back up in a new, smaller zipfile. But I ran into a problem, the MBL’s PHP didn’t have the php5-gd (graphics) module I needed. I had to add another archive to my apt-get sources.list to get a repository that has the module.
Needless to say, things went poorly. Now I have some unresolvable dependencies and can’t figure out how to resolve them. Here’s the last part of the install process:
[quote]dpkg: warning: files list file for package
ramlog' missing, assuming package has no files currently installed. dpkg: warning: files list file for packagelibparted0’ missing, assuming package has no files currently installed.
(Reading database … 19458 files and directories currently installed.)
Preparing to replace dpkg 18.104.22.168 (using …/dpkg_1.16.16_powerpc.deb) …
Unpacking replacement dpkg …
dpkg: error processing /var/cache/apt/archives/dpkg_1.16.16_powerpc.deb (–unpack):
trying to overwrite ‘/etc/logrotate.d/dpkg’, which is also in package wd-nas 02.50.00-142897
Processing triggers for man-db …
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)[/quote]
I had fixed a couple of missing deb keys etc. but in the end I have some missing dependencies and Apache won’t run. I’ve spent 4-5 half days working on it and I’m practically ready to give up (i.e. get a bigger hammer).
First, if anybody knows how I can fix my missing dependencies problem I’d appreciate some advice. I really wish I could get that php5-gd module in, but I’d settle for restoring my MBL DUO back to the factory Debian configuration.
If I can’t get any help on that or get help but it doesn’t work out, what do you think of my alternate plan?
I have like 5 MBLs, four of them DUOs in RAID config. Right now I’m moving files off the problem MBL to other MBLs and intend to eventually have all my user data moved to other MBLs. I have my most recently purchased MBL which was almost empty so I’m clearing it off to other drives too.
Both the new MBL and problem MBL are 8TB DUOs set up as 4TB RAID. I figure if I get both the problem one and new one empty, I have two equivalent drives except the software in one is messed up. So in the problem drive I remove the HDDs and format one HDD (or maybe just remove the partitions to turn it into the equivalent of a virgin drive). Then I put it in the problem MBL and remove a HDD from the new MBL and use that as the other drive, and then presumably it will rebuild the formatted drive and come up running with the same config as the new MBL. Then I remove the new MBL’s HDD and put it back where it belongs, format the other problem HDD and put that in the problem MBL and let it rebuild again.
Unless my theory is wrong I should now have two identical MBL DUOs and all I have to do is leave one powered down while I change the IP address etc of the previously broken one back to its old settings. Then I power up the new MBL and if all works okay I should have two MBLs with identical configurations (except IP address etc) both empty, and I can move my files back to the previously broken MBL and I’m good to go.
So (1) can you figure out any suggestionss on fixing the config of my broken MBL? Or (2) do you think my scenario of rebuilding the broken MBL off a working MBL is a good idea?