I’ve tried to run the 12.1 rc2 gnome live CD on two different machines and it fails the same way. This is the 32-bit live CD. The first attempt was on a Lenovo T400 laptop with 4gb ram, and the second was on a desktop PC (not a major brand, I built it) with Intel quad core 9300 and 8gb ram. Both have ATI video cards, so I tried nomodeset on the boot line, but this has no effect. It seems to fail in the same place … mounting some drive fails, its saying something about md (the multi-disk driver). Not sure what is going on, because its happening during boot of the live image I have no idea how to trap the output and display it here for you guys. Of course the laptop does not have multiple drives, or raid, so I am not sure what its doing with md. In both cases I am inserting the CD in the drive and then booting to it. I remade the CD rom again just to be sure it wasn’t a problem with the disk but it behaves the same. Any ideas?
Yes, I see that message too. The problem is, its difficult for people to understand what is an “ok” or expected error, vs what is “the bad error” that is getting in your way. I would not expect its ability to read an ntfs volume (that just happens to be there) to interfere with its ability to load the LIVE version, which should not be writing anything to the local disk. Even if it cannot mount it for read it should just let it go and move on.
I also have this problem with KDE 64-bit live disc the error messages I get are as follows:
systemd-fsck fsck: fsck.unknown: not found
fsck: error 2 while executing fsck.unknown for /dev/sda1
fsck failed with error code 8
mount: unknown filesystem type ‘unknown’
liveswap.mount mount process exited, code=exited status=32
Job liveswap-kikiswap.swap/start failed with result ‘dependency’
Job remote-fs.target/start failed with result ‘dependency’
Job local-fs.target/start failed with result ‘dependency’
Triggering OnFailure- dependency of local-fs.target
Unit liveswap.mount entered failed state
'/sbin/modprobe -bv pci: (then a long string of numbers)  terminated by signal 15 (Terminated)
'/sbin/modprobe -bv usb " random numbers, etc "
'/sbin/modprobe -bv pci “etc”
Welcome to emergency mode. Use “systemctl default” or ^D to activate default mode.
Press enter for login:
Then even after using systemctl default it still wont boot just gives same error messages.
Yeah I see the same thing. It certainly appears the failure of liveswap.mount causes the abort. I don’t know if the reason that fails has anything to do with the failed mount of the ‘unknown’ filesystem though. Logic would dictate that it shouldn’t.
This bug is listed as fixed, so the problem should be solved in the next release candidate (if there is one) or the GA release. Bummer for me since I don’t have any computer to try this on that does not have a hard drive with ntfs partitions on it. One thing I might try is to remove the hard drive completely from my laptop and then boot to the Live CD and see what happens.
Yeah that’s the bug. I was able to work around it by doing the following.
Find and edit the line that is something like:
/dev/sda1 /liveswap unknow defaults 11
now I didn’t like the idea of mounting my NTFS partition to write a swap file to. It could be perfectly fine but it seems somehow wrong to me. So if you’ve got a ton of RAM like I do, just create a ramdisk for the swap. So first I ran:
Absurd? Yes I agree. But I couldn’t find a way to get the installer to launch without having /liveswap mounted. It was dirty hack that allowed the installer to launch. I’m not suggesting doing this as a permanent measure.
What I find truly absurd is that this bug didn’t get caught before the release candidate was made available. There is no test which includes installing the image on a machine with at least one hard disk that has a windows partition on it? I find that hard to believe… if not an installation, at least testing the live image?
On 2011-11-10 01:16, ardob wrote:
> Absurd? Yes I agree. But I couldn’t find a way to get the installer to
> launch without having /liveswap mounted. It was dirty hack that allowed
> the installer to launch. I’m not suggesting doing this as a permanent
Ah, I see…
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
I installed 12.1 milestones and release candates on a machine with an MS-Windows (NTFS) partition and did not encounter the problem. So there must be other factors at work in addition to their being an NTFS partition on same PC, else many more of us would have encountered this problem.
Am 14.11.2011 06:46, schrieb oldcpu:
> I installed 12.1 milestones and release candates on a machine with
> an MS-Windows (NTFS) partition and did not encounter the problem. So
> there must be other factors at work in addition to their being an
> NTFS partition on same PC, else many more of us would have
> encountered this problem.
I can also confirm that, I ran live usb and also a full install of 12.1
RC1 and later RC2 for over a week on my netbook which has 3 windows
partitions (2 ntfs and one small fat) and there was no problem.
PC: oS 11.4 (dual boot 12.1) 64 bit | Intel Core email@example.comGHz | KDE
4.6.0 | GeForce GT 420 | 16GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom firstname.lastname@example.orgGHz | KDE 4.7.3 |
nVidia ION | 3GB Ram