Help getting insall to hard drive working

[ocwasere]

Am I the only one to wipe his hard drive?
Drinking last night
booted xbmclive decided to make me a usb disk press the wrong number pushed y for yes
Cool that was ease.
Took the usb drive to boot other computer DID NOT BOOT
Went back to my pc switch it on xbmc boots up
Laughing now but not last night
I had win98 winxp mandriva 2008 all bootable NOW ALL GONE.:laugh::laugh:

ANYWAY

I have got a sata 160 GB hard drive and a 40 GB ide hard drive

So I installed xbmclive to my 40 GB drive

If I boot xbmclive from boot cd its fine
And if I disconnect the sata drive its fine

But with the sata drive I press f8 to change boot drive select the 40 GB drive
Xbmclive boots but stops at a black screen

Pressing alt ctrl f1

I get this loop

Mount: mounting /sda1 on /container failed: device or resource resource busy
Mount: mounting /sda1 on /container failed: device or resource resource busy
Mount: mounting /sda1 on /container failed: device or resource resource busy
Mount: mounting /sda1 on /container failed: device or resource resource busy
Mount: mounting /sda1 on /container failed: device or resource resource busy
Alt ctrl f2 black screen
Alt ctrl f3 black screen
Alt ctrl f4 black screen

Etc


Boot from cd again alt ctrl f2 login fdisk - l this is what I get



/dev/sda/ 160 gb
sda1 Hidden w95/fat32
sda2 hpfs/ntfs
sda3 hpfs/ntfs

/dev/sdb/ 40 gb
sdb1 system
sdb2 linuxswap/solris
sdb3 linux

[slacker666]

have you checked your bios settings? is your 40gb prior in boot order to your 160gb disk?

[ocwasere]

have you checked your bios settings? is your 40gb prior in boot order to your 160gb disk?

thanks but i have try that still no luck

[ocwasere]

just noticed

sata 160 GB hard drive getting detected as (sda) which is right
but my 40 GB drive IDE drive is also getting detected as (sda)
shouldn't it be (hda)

/dev/sda/ 160 gb
sda1 Hidden w95/fat32
sda2 hpfs/ntfs
sda3 hpfs/ntfs

/dev/sdb/ 40 gb should this be ditected as (hda) as it is an IDE drive
sdb1 system
sdb2 linuxswap/solris
sdb3 linux

[testitonanimals]

I am having the same issue. Has a solution been found? I just used the live cd to install to fixed disk, and when i start up the fixed disk XBMC distro I get a black screen. On TTY1 I get a repeated message reading

mound: Mounting /dev/sda1 on /mnt failed: Device or resource busy

I am not sure which hard drive it is looking at. I have in the system a 40GB drive that the distro is installed on, a 200GB drive, a 400GB drive, and 4 x 1TB drives. I'm not 'new' to linux, but I am not very good with it. If any further information is needed, just let me know. Thanks

[tim_wang]

The reason XBMC is not booting is because you have /dev/sda1 in your syslinux.cfg, and you have more than 1 drive attached. Say you have XBMC installed in the only drive in the system. Since there is only 1 drive, it will be assigned /dev/sda1 on boot up, and XBMC will boot fine. But if you install another drive for your media, and that drive gets assigned /dev/sda1 and your XBMC drive gets /dev/sda2 on boot up, XBMC will fail to load.

Here is a fool proof way of mounting as many IDE and SATA drives as you like, and always have XBMC boot off the correct drive every time.

Boot off the XBMC Live CD. Type mount to see which drives are mounted. Note the drives' corresponding device name. For example:

/dev/sda1 on /media/sda1 type vfat (rw,noexec,nosuid,nodev,fmask=0133,dmask=0022,uid= 1000,gid=1000)

This means the device /dev/sda1 is currently mounted at /media/sda1.

Then type ls -l /dev/disk/by-uuid to see the UUIDs for the corresponding devices. The UUID for a drive is unique and will not change no matter how many drives are attached. From the above example:

lrwxrwxrwx 1 root root 10 2008-11-24 08:19 1234567890ABCDEF -> ../../sda1

This means the device /dev/sda1 has an UUID of 1234567890ABCDEF.

If /dev/sda1 is where you installed XBMC, make the following change to your syslinux.cfg located in /media/sda1. From the above example:

Replace root=/dev/sda1 with root=UUID=1234567890ABCDEF

Now XBMC will always boot from the drive with UUID=1234567890ABCDEF, which never changes no matter how many drives you add later.

[testitonanimals]

I ran the XBMC live cd, switched to TTY1 and edited the syslinux.cfg file with

root=UUID=4982-6FDF

Which is the uuid of /media/sdf1, which is where XBMC was installed to disk, but when I save the file and restart without the live cd, it still says that mounting /dev/sda1 failed. I have tried 3 times, and I know the file is writing to the drive because it is the same the next time I edit it.

[testitonanimals]

It boots off of sda1, here is the output of cfdisk /sda

sda1 Boot Primary W95 FAT32 (LBA) 2056.32
sda2 Boot Primary Linux swap / Solaris 518.20
sda3 Boot Primary Linux ext3 37441.48



All disk UUID's:


lrwxrwxrwx 1 root root 10 2009-01-30 23:30 0b3142bb-8fb1-4c1e-96cc-7dab592e271b -> ../../sda3
lrwxrwxrwx 1 root root 10 2009-01-30 23:30 4982-6FDF -> ../../sda1
lrwxrwxrwx 1 root root 10 2009-01-30 23:30 5a4308fc-21b5-49e2-a47c-927905942996 -> ../../sdb1
lrwxrwxrwx 1 root root 10 2009-01-30 23:30 6064fee9-0b9b-4caf-bd88-4faf76225b4b -> ../../sda2

And this is how I edited syslinux.cfg:


# nVidia
label 1
kernel vmlinuz
append root=UUID=49826FDF initrd=initrd0.img boot=disk quiet splash xbmc=nvidia

# AMD
label 2
kernel vmlinuz
append root=UUID=49826FDF initrd=initrd0.img boot=disk quiet splash xbmc=amd

# Intel
label 3
kernel vmlinuz
append root=UUID=49826FDF initrd=initrd0.img boot=disk quiet splash xbmc=intel

# Install
label 0
kernel vmlinuz
append root=UUID=49826FDFinitrd=initrd0.img boot=disk quiet splash xbmc=install,nodiskmount

#Safe mode
label safe
kernel vmlinuz
append root=UUID=49826FDF initrd=initrd0.img boot=disk xbmc=nodiskmount

label toramintel
kernel vmlinuz
append root=UUID=49826FDF initrd=initrd0.img boot=disk quiet splash xbmc=intel,boottoram

label toramnvidia
kernel vmlinuz
append root=UUID=49826FDF initrd=initrd0.img boot=disk quiet splash xbmc=nvidia,boottoram

label toramamd
kernel vmlinuz
append root=UUID=49826FDF initrd=initrd0.img boot=disk quiet splash xbmc=amd,boottoram


default 1
timeout 1
CONSOLE 0
prompt 0



Is there something I missed? In this info, I have disconnected 5 sata drives, which when plugged in, are what causes it not to boot.

[tim_wang]

You need to make the following change to your syslinux.cfg. Replace

root=UUID=49826FDF

with

root=UUID=4982-6FDF

You also need to make the following change to your /etc/fstab. Replace

/dev/sda2 none swap sw,auto 0 0
/dev/sda3 /home ext3 defaults,auto 0 0

with

UUID=6064fee9-0b9b-4caf-bd88-4faf76225b4b none swap sw,auto 0 0
UUID=0b3142bb-8fb1-4c1e-96cc-7dab592e271b /home ext3 defaults,auto 0 0

[testitonanimals]

After making those changes, on reboot it still reads

"mount: Mounting /dev/sda1 on /mnt failed: Device or resource busy"

over and over again on tty1

[testitonanimals]

fstab:

unionfs / unionfs defaults 0 0
proc /proc proc defaults 0 0
UUID=6064fee9-0b9b-4caf-bd88-4faf76225b4b none swap sw,auto 0 0
UUID=0b3142bb-8fb1-4c1e-96cc-7dab592e271b /home ext3 defaults,auto 0 0


syslinux.cfg:

# nVidia
label 1
kernel vmlinuz
append root=UUID=4982-6FDF initrd=initrd0.img boot=disk quiet splash xbmc=nvidia

# AMD
label 2
kernel vmlinuz
append root=UUID=4982-6FDF initrd=initrd0.img boot=disk quiet splash xbmc=amd

# Intel
label 3
kernel vmlinuz
append root=UUID=4982-6FDF initrd=initrd0.img boot=disk quiet splash xbmc=intel

# Install
label 0
kernel vmlinuz
append root=UUID=4982-6FDF initrd=initrd0.img boot=disk quiet splash xbmc=install,nodiskmount

#Safe mode
label safe
kernel vmlinuz
append root=UUID=4982-6FDF initrd=initrd0.img boot=disk xbmc=nodiskmount

label toramintel
kernel vmlinuz
append root=UUID=4982-6FDF initrd=initrd0.img boot=disk quiet splash xbmc=intel,boottoram

label toramnvidia
kernel vmlinuz
append root=UUID=4982-6FD" initrd=initrd0.img boot=disk quiet splash xbmc=nvidia,boottoram

label toramamd
kernel vmlinuz
append root=UUID=4982-6FDF initrd=initrd0.img boot=disk quiet splash xbmc=amd,boottoram


default 1
timeout 1
CONSOLE 0
prompt 0

[testitonanimals]

I have even tried editing mtab with UUID's to no avail. I can not find any other type of config that is having an issue. I'm beginning to think that the issue is not xbmc mounting my primary hard drive, but maybe when I plug the new drives in, xbmc is trying to mount one of those and running in to problems. 4 of the drives are raid drives and if xbmc is trying to mount lets say /dev/sda1 which might be a linux raid autodetect hard drive, then it would probably fail. Is there any way to see if this is what is happening?

[testitonanimals]

No one has any advice? Is there some kind of service in xbmc live that automatically mounts drives that I can turn off? I'm almost positive that's what the issue is.

[tim_wang]

I had a bad feeling your 4 x 1TB drives were in raid. I am not sure that XBMC 8.10 Live includes the driver for your raid controller.

Try booting with only the drive containing XBMC connected. If that works, try booting with a second drive (not raid) connected. Repeat with a third drive (not raid) connected. If everything works up to this point, but fails to boot with the 4 x 1TB raid connected, then it is definitely a problem with the driver for your raid controller.

[talexone]

Hi,
There is solution to make your drive working:
1. Unpack initrd0.img to harddrive.

Mount XBMCLive Boot Partition:
mkdir /mnt/XBMCLive
mount -t vfat /dev/sdb1 /mnt/XBMCLive

Create a directory to put all the file into:
mkdir /home/initrd
cd /home/initrd
cat /mnt/XBMCLive/initrd0.img | gunzip - | cpio -i


2. Modify ../scripts/disk file:

Open file ../scripts/disk:
nano /home/initrd/scripts/disk

Find lines:
# Find the boot disk
while true; do
for device in 'hda' 'hdb' 'sda' 'sdb'; do

And replace by:
# Find the boot disk
while true; do
for device in 'hda' 'hdb' 'sdb' 'sda'; do

Ctrl-O to save and Ctrl-X to exit


3. Repack initrd0.img:

Type in the following commands:
cd /home/initrd
find . | cpio -H newc -o | gzip -9> /mnt/XBMCLive/initrd0.img

Then unmount /mnt/XBMCLive and remove directory

[l.capriotti]

Hi,
There is solution to make your drive working:


the issue was related to earlier version of Live. the instructions are correct but I would test the latest release first.