Search:

Any idea?? i can't get 5.1 to work

Yeah, finishing the upgrade to 16.04 worked... found this article too on my other issue
http://askubuntu.com/questions/196125/how-can-i-resize-an-lvm-partition-i-e-physical-volume

Alright, i finally managed to get into recovery mode and resume a runable session (I had to tap shift at the BIOS screen a number of times to get to the adv. grub screen)
I ctried upgrading and saw...

So i ran the check disk utility in the live CD and it found no errors... like i mentioned, from a live session i've ran e2fsck against the LVM my OS is on and gotten no issue.

BUT, after booting,...

I think i was staring at the machine too long and forgot about the check disk feature on the boot CD. I'll give that a shot.

As far as the server setup, all i know is i had a failed upgrade a...

Hey all,

I'm about out of ideas, but i have a 15.10 installation that won't boot. I tried upgrading this installation to 16.04 a few weeks ago but it failed because my boot partition was full. ...

I changed the resolution down to 1080p again and got a odd behavior with the screen repainting. I dropped down lower than that and back to 1920x1080 and it seemed to have fixed the painting issue. ...

Any thoughts? I'm still getting this issue and it makes this machine hard to manage remotely which i have to do frequently.

i've got a pretty new Ubuntu 15.10 build that i'm having some trouble with in regards to vino-server. Using multiple clients (remmina on my laptop, vnc-viewer on my phone) when i connect only the...

Just a feeler, i have 3x4TB drives in an external sata enclosuer and i've had it with it. These are new drives because i'd previously thought the drives were at fault for my weekly RAID degradation...

I think so too... i did some tweeking and got the resync up to 35Mb/s so it should be up by tomorrow morning, i can get the move started and hopefully have the data moved by EOD (no idea how long...

OK, its not degraded, i think its just doing building the initial parity set. However its taking forever to assemble.. running at 1 MB/s. Should i review my setup options? i picked a 512K chunk...

Hey all

I'm moving data from an old RAID5 (2TBx3) to a new RAID5 (4TBx3) and I'm wondering how to approach it.

I have a 5 bay external RAID enclosure. 3 bays are for the existing RAID. I'm...

Still getting an error, in roughly the same place.

I've ran e2fsck directly, passing -p, hoping that perhaps each run its able to get a little more and a little more done, but I don't think that's...

I've got an ext4 LUKS LVM running on a RAID5 setup with 3 2TB drives and i had a failure occur the other week.

After having the RAID not assemble properly i brought it up using --force and got a...

I'll probably start a new threat to track this issue, since it seems to be different, but i'll post any updates i have (and link to the new thread)

It looks like the underlying LUKS LVM got...

I did assemble the RAIDS in a weird order, yes... this was an old work around for when one of my drives would think the other to be faulty, when it appeared it was not (I don't think the drives i...

Also, the data scrub finished but the folders still have the same issue as before :-/

Would it be possible to run data recovery on the RAID? I was thinking about replacing the drives anyway (they...

So, I didn't rebuild the array... the same array came up having the much of the same data on it... i'm just seeing some folders and files missing as though the LVM is corrupted. I'm wondering if...

After a routine reboot the other day my RAID wouldn't assemble. Looking closer it said only 2/3 drives were included. Assembling with --force didn't fix this.

So i took one of the working...

Well, glad i didn't do anything rash :-)

After getting to a state described above (behavior changed from spinning up the RAID with only G,H to only F,G, caused by attempting to build the RAID with...

I think i should be OK just adding /dev/sdh1 to the array and letting it resync... it just seems like a waste of time and potentially an irrecoverable action. What does everyone think?

UPDATE: So i tried assembling with just F and G and got mdadm to update f's event count... but now it still won't build with this error:

xxx@xxxxxx:~$ sudo mdadm -A --force /dev/md0...

I just upgraded from 12.04 LTS to 14.04 LTS and when i tried to fire up my RAID it will not assemble... even using --force won't help, which is odd because yes the event counts are off but only by...

I've had an eSATA2 connected external enclosure that i've been running an mdadm managed RAID 5 on for the past 2 years. I've always had issues with the RAID entering a DEGRADED state every so...