Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
Results 11 to 15 of 15
Are you sure you added -l ... example output for ls /dev/disk/by-uuid -l Code: total 0 lrwxrwxrwx 1 root root 10 Apr 17 21:45 129f99b8-6366-4ad8-8933-843a6fce5da3 -> ../../sda8 lrwxrwxrwx 1 root ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Linux Guru Jonathan183's Avatar
    Join Date
    Oct 2007
    Posts
    3,043

    Are you sure you added -l ... example output for ls /dev/disk/by-uuid -l
    Code:
    total 0
    lrwxrwxrwx 1 root root 10 Apr 17 21:45 129f99b8-6366-4ad8-8933-843a6fce5da3 -> ../../sda8
    lrwxrwxrwx 1 root root 10 Apr 17 21:45 38bd7d43-c6fa-429d-bb64-a58ccb4af2b7 -> ../../sda4
    lrwxrwxrwx 1 root root 10 Apr 17 21:45 4754b485-e309-42ed-b87a-4f558c9edbcf -> ../../sda1
    lrwxrwxrwx 1 root root 10 Apr 17 21:45 85086f40-4229-41aa-8f4b-045524a9f724 -> ../../sda9
    lrwxrwxrwx 1 root root 11 Apr 17 21:45 864d0131-a7fd-4827-8336-7dd0c055e6d9 -> ../../sda10
    lrwxrwxrwx 1 root root 11 Apr 17 21:45 8d63595f-ffe7-4e9d-8715-fecc48581b0b -> ../../sda11
    lrwxrwxrwx 1 root root 10 Apr 17 21:45 929c7eed-350b-4b3a-9c32-3c666480366e -> ../../sda7
    lrwxrwxrwx 1 root root 11 Apr 17 21:45 96a5b08b-fd74-4ee0-a509-dcfac4c91ce7 -> ../../sda12
    lrwxrwxrwx 1 root root 10 Apr 17 21:45 c465dc06-83f3-447b-a424-9af4c5d2431a -> ../../sda6
    example output without -l
    Code:
    129f99b8-6366-4ad8-8933-843a6fce5da3
    38bd7d43-c6fa-429d-bb64-a58ccb4af2b7
    4754b485-e309-42ed-b87a-4f558c9edbcf
    85086f40-4229-41aa-8f4b-045524a9f724
    864d0131-a7fd-4827-8336-7dd0c055e6d9
    8d63595f-ffe7-4e9d-8715-fecc48581b0b
    929c7eed-350b-4b3a-9c32-3c666480366e
    96a5b08b-fd74-4ee0-a509-dcfac4c91ce7
    c465dc06-83f3-447b-a424-9af4c5d2431a
    So lets say this was your output, you would replace /dev/sda1 with /dev/disk/by-uuid/4754b485-e309-42ed-b87a-4f558c9edbcf in /etc/fstab.

  2. #12
    Just Joined!
    Join Date
    Jan 2008
    Posts
    53

    Cool

    Quote Originally Posted by waveform View Post
    Hello
    I don't understand why this is happening. I have two drives in this system, Drive A has Windows 7 on one half and the other half has ubuntu 9.10, both run great, no problems with boot-loader.

    I added another drive to this system and installed Debian 5.04 in headless mode, and the installation went well. I'm using the F12 key to boot the new drive. Reason I'm using the F12 by the way, is that the Debian boot-loader (grub) reported my windows7 copy as vista, and didn't see the ubuntu as being present on drive A.
    I didn't want to chance over writing the boot-loader on drive A. So I disconnected the drive A and reinstalled Debian on drv B.
    when I plug in the windows/ubuntu drive (drive-A) Debian boots with all kinds off errors saying that it can't find certain paths. mouthing dev root failed, no such file or directory.
    No init found, Can't access tty; job control turned off (initramfs)

    What makes no sense is that if I disconnect the drive A, and reboot the Debian drive using the F12 key, it automatically repairs itself and works again.

    I am still sort of new to Linux, and am doing all this to try and learn something. I'm not sure why the Debian boot-loader didn't see my ubuntu install on the other drive and reported windows7 as vista.
    I'm not sure how to approach this issue atm, and everything I'm finding on the net is not relevant to the issue. After all, I'm booting Debian from it's own drive so how could the other drive be interfering and causing Debian to loose it's paths when the other drive is plugged in?
    First at all, you must change everithing, and install it again, i think that when you unplug drive A you forgot how GNU/linux Works, and how does it interprete the booting and knoledge base of the whole hardware, is obvious why you are having all this problems.

    First at all when you had the drive A alone it is known as sda, adding another one it is labeled as sdb, when unplug A and let B alone, installing debian alone will be installed as sda not as sdb, it will work fine just in B plugged alone, conecting drive A of course wont run drive B , because is searching in drive A sda now and should be looking at sdb, giving you the problem because is obviously that debian is in drive B not in drive A.

    It is fixeable! I have not do this kind of changes, so i recomend you the easy way to reinstall debian with drive A plugged, what you need to do is to skip the grub installation part in that way you wont rewrite the boot loader of ubuntu just say no when the installation ask to do it, in that way you will preserve the ubuntu grub loader, then just go inside ubuntu and add the drive B loader point.

    The rush mode or the hard way is to go inside drive B alone and change everithing o be found in sdb not in sda, but it is a little hard i think so i think is easy reinstall debian if you do not have anithing important than changing everithing.

    Good luck!

  3. #13
    Linux Guru Jonathan183's Avatar
    Join Date
    Oct 2007
    Posts
    3,043
    Quote Originally Posted by waveform View Post
    by the way, I wanted to mention once more; when i moved the Debian drive to it's original location a few days ago, the problem seemed to be fixed. I'm just going through these instructions to learn how this works.
    Quote Originally Posted by rojoblandino View Post
    First at all, you must change everithing, and install it again, i think that when you unplug drive A you forgot how GNU/linux Works, and how does it interprete the booting and knoledge base of the whole hardware, is obvious why you are having all this problems.
    To update references should require update of grub config and /etc/fstab only. Re-install should not be required for this type of problem. uuid or label could be used instead of /dev/sda device references.

  4. $spacer_open
    $spacer_close
  5. #14
    Just Joined! waveform's Avatar
    Join Date
    Apr 2010
    Posts
    9

    Smile

    Quote Originally Posted by Jonathan183 View Post
    Are you sure you added -l ... example output for ls /dev/disk/by-uuid -l
    no, it was a 1, that was the problem Jonathan183. By the way, thanks again for all the help. Just to update this. I wanted to start using Debian to run a dedicated game server for the ArmA-II game in headless mode because I figured it would be efficient. I've got the server running now and the performance is excellent, much better than when I was running it on windows. I also picked up a unix/Linux book that has a huge command, switch reference section in the back and have been going through it while at work during off time. I'm a driver, don't worry, I'm not reading while driving.

    Anyway, like I said, everything seems to be working so far, but I'll look more into what you were explaining when i plug my other system back in again. This has been very helpful information, and I appreciate every bit of it

    Thanks Jonathan183 for sticking around so long!

  6. #15
    Linux Guru Jonathan183's Avatar
    Join Date
    Oct 2007
    Posts
    3,043
    Glad your sorted ... can you mark the thread solved

Page 2 of 2 FirstFirst 1 2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •