@mimosa,
That part of the results.txt is not enough to evaluate the problem, IMO. Besides posting here the complete report from BIS, do you see anything while trying to boot with the USB device? Any message / behavior?
If you are willing to delete any and all info from your USB device, I could give you manual instructions if you want (instead of using LiveClone or the scripts, that might be failing for some reason).
EDIT: I didn't see shador's post.
booting trouble
Re: booting trouble
Shador, I had feeling you might say just that. So here goes:
EDIT
In answer to your other question, I'm sorry, I don't remember exactly, but very early on there is a message saying Linux cannot be found. It looks like not even the kernel is loaded. However before that there appears something about syslinux and Peter Alvin.
Code: Select all
Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> Lilo is installed in the MBR of /dev/sda.
=> Lilo is installed in the MBR of /dev/sdb.
sda1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows XP: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP
Boot files: /boot.ini /ntldr /NTDETECT.COM
sda2: __________________________________________________________________________
File system: Extended Partition
Boot sector type: Unknown
Boot sector info:
sda5: __________________________________________________________________________
File system: vfat
Boot sector type: Windows XP: FAT32
Boot sector info: According to the info in the boot sector, sda5 starts
at sector 63. But according to the info from fdisk,
sda5 starts at sector 22523193. "63" and "2048" are
quite common values for the starting sector of a
logical partition and they only need to be fixed when
you want to boot Windows from a logical partition.
Operating System:
Boot files:
sda6: __________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
sda7: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Mounting failed: mount: /dev/sda7 already mounted or sda7 busy
sda8: __________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
sdb1: __________________________________________________________________________
File system: vfat
Boot sector type: SYSLINUX 3.84 3.84
Boot sector info: Syslinux looks at sector 768 of /dev/sdb1 for its
second stage. The integrity check of Syslinux failed.
According to the info in the boot sector, sdb1 starts
at sector 0. But according to the info from fdisk,
sdb1 starts at sector 2048.
Operating System:
Boot files: /boot/grub/grub.cfg /ldlinux.sys
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 60.0 GB, 60021399040 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117229295 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 * 63 22,523,129 22,523,067 7 NTFS / exFAT / HPFS
/dev/sda2 22,523,130 117,194,174 94,671,045 f W95 Extended (LBA)
/dev/sda5 22,523,193 73,722,284 51,199,092 b W95 FAT32
/dev/sda6 73,722,348 103,024,844 29,302,497 83 Linux
/dev/sda7 103,024,908 115,234,244 12,209,337 83 Linux
/dev/sda8 115,234,308 117,194,174 1,959,867 82 Linux swap / Solaris
Drive: sdb _____________________________________________________________________
Disk /dev/sdb: 4007 MB, 4007657472 bytes
61 heads, 21 sectors/track, 6110 cylinders, total 7827456 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sdb1 * 2,048 7,827,455 7,825,408 6 FAT16
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/sda1 82C4A392C4A3874F ntfs
/dev/sda5 A46A-931B vfat WINDATA
/dev/sda6 ce006792-c824-400b-8ed4-3570a224dac7 ext3
/dev/sda7 8ddf1617-83d4-411e-ab90-40824b98a753 ext4
/dev/sda8 a0759c66-4431-4b95-949c-f6d66b842fcb swap
/dev/sdb1 894D-A3BF vfat LEET
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/root / ext4 (rw,noatime,barrier=1,data=ordered)
/dev/sda1 /xp fuseblk (rw,allow_other,blksize=4096,default_permissions)
/dev/sda5 /windata vfat (rw,umask=000)
/dev/sda6 /home ext3 (rw)
================================ sda1/boot.ini: ================================
--------------------------------------------------------------------------------
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
--------------------------------------------------------------------------------
=========================== sdb1/boot/grub/grub.cfg: ===========================
--------------------------------------------------------------------------------
# vim: syn=sh et sw=2 st=2 ts=2 tw=0:
# if your keyboard does not respond after choosing the language, change this variable to "true"
set weird_usb_keyboard=false
set cfgprefix="($root)$basedir/boot/grub"
set debug=
set locale_dir="$cfgprefix/locale"
set gfxpayload=keep
set autologin=autologin
export cfgprefix debug locale_dir weird_usb_keyboard
source ${cfgprefix}/include.cfg
loadsettings
export autologin debug fromiso gfxpayload ibus kb kbnum lang langnum locale memonly numlock passwd proxy runlevel synaptics custom
if [ "$skiplang" = "true" ]; then
if [ -n "$kb" ]; then
if [ -n "$locale" ]; then
loadkeymap
configfile ${cfgprefix}/boot.cfg
fi
fi
fi
configfile ${cfgprefix}/lang.cfg
--------------------------------------------------------------------------------
=================== sdb1: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
?? = ?? boot/grub/grub.cfg 1
?? = ?? boot/initrd.xz 1
?? = ?? boot/vmlinuz 1
================= sdb1: Location of files loaded by Syslinux: ==================
GiB - GB File Fragment(s)
?? = ?? ldlinux.sys 1
======================== Unknown MBRs/Boot Sectors/etc: ========================
Unknown BootLoader on sda2
00000000 80 37 1b fd 87 c3 99 51 75 a9 64 10 f6 42 2d 90 |.7.....Qu.d..B-.|
00000010 f7 80 fa 48 1c 74 5e 3f 6d 27 7f fd ff 90 20 a0 |...H.t^?m'.... .|
00000020 e4 9b 7d 1c 49 cf fd 62 20 15 9f 67 a6 f2 c4 48 |..}.I..b ..g...H|
00000030 28 76 59 1a f3 e7 61 6e dd ac cb d1 30 53 70 f0 |(vY...an....0Sp.|
00000040 a9 aa 7b 9b d3 5a 17 a1 f2 77 39 26 ca ce 9e cf |..{..Z...w9&....|
00000050 61 0d 80 02 f0 6b 98 4d c6 ba 18 2c 51 00 0a 85 |a....k.M...,Q...|
00000060 0b 77 b7 3a 14 40 4b 7f c3 07 f7 f3 62 dd 06 06 |.w.:.@K.....b...|
00000070 06 05 a0 c0 c0 e0 ff 56 06 3e 7c f9 fb da 30 a9 |.......V.>|...0.|
00000080 bf 48 fb 8c 37 e9 88 bf 54 e6 bb f4 af 9f 3e a3 |.H..7...T.....>.|
00000090 5d f3 e7 3b 1d 3f f4 f9 6c 52 86 f6 ba e8 57 52 |]..;.?..lR....WR|
000000a0 44 74 e9 d3 da 54 86 d2 a5 19 d1 c7 f2 55 3f 55 |Dt...T.......U?U|
000000b0 4d d4 2b 15 d2 a9 a5 02 5b 14 a1 bd f9 e9 54 47 |M.+.....[.....TG|
000000c0 2a df 3a 7c e9 ed 31 2e 73 46 7c 85 35 95 4a 9f |*.:|..1.sF|.5.J.|
000000d0 57 53 0e 93 db 50 dc c3 b2 de 93 c7 8f 20 06 47 |WS...P....... .G|
000000e0 a4 e7 4f 09 56 1b 97 3f 96 8c f0 fb 55 41 26 cd |..O.V..?....UA&.|
000000f0 da ca 88 35 fe ec 3c b0 e8 d1 0b f6 ee c9 6f ec |...5..<.......o.|
00000100 2e cd 5c 4c 6a 3a 7b 00 2f ac 7c 07 9c 9a dd d8 |..\Lj:{./.|.....|
00000110 00 3f 6c 3e 15 10 22 e6 a4 83 6b 57 35 c1 ba ca |.?l>.."...kW5...|
00000120 62 34 ee ae 2e 8f 1c 7f 42 c1 fc bd 2a f2 da a9 |b4......B...*...|
00000130 32 3d 26 3a 78 4a a0 dc b9 fc b4 64 07 b0 51 cc |2=&:xJ.....d..Q.|
00000140 16 dd 23 ab d2 6f 21 80 00 50 ef 04 59 5e 94 48 |..#..o!..P..Y^.H|
00000150 41 ea ef ef 01 e0 0c f1 9f 0f 25 ab 47 39 0c 3f |A.........%.G9.?|
00000160 47 16 be 1b 9a 99 ce 73 28 21 1d 7c e8 7a cb af |G......s(!.|.z..|
00000170 9f 79 50 23 03 61 5e 01 e1 2e 36 ca 60 f3 9a c0 |.yP#.a^...6.`...|
00000180 7a 79 a0 95 b2 10 7e 76 b4 d5 05 04 61 a9 17 68 |zy....~v....a..h|
00000190 3b ad 90 8c bc d4 74 71 04 01 4e 8b 78 22 ca f4 |;.....tq..N.x"..|
000001a0 82 42 0f 57 83 78 00 1c 39 b7 76 eb 6c 94 1d 63 |.B.W.x..9.v.l..c|
000001b0 dd 66 00 00 3a bc 17 b4 3e 0e 3a ae 96 a9 00 01 |.f..:...>.:.....|
000001c0 c1 ff 0b fe ff ff 3f 00 00 00 74 3c 0d 03 00 00 |......?...t<....|
000001d0 c1 ff 05 fe ff ff b3 3c 0d 03 20 1f bf 01 00 00 |.......<.. .....|
000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200
=============================== StdErr Messages: ===============================
No volume groups found
mdadm: No arrays found in config file
In answer to your other question, I'm sorry, I don't remember exactly, but very early on there is a message saying Linux cannot be found. It looks like not even the kernel is loaded. However before that there appears something about syslinux and Peter Alvin.
Re: booting trouble
@mimosa,
Syslinux is not correctly "installed" (ldlinux.sys is there, but I'm not sure your VBR is pointing to the correct sector location; and syslinux.cfg is not recognized in the expected paths). Are you sure you used LiveClone?
Also, it seems you used FAT16 for that partition. Please use FAT32 for that partition size.
Anyway, here are some manual steps (and they will delete the current info in your USB device).
1_ Boot with your Salix LIVE system (the one you said it is correctly working).
2_ Start Gparted.
3_ Select the appropriate (USB) HDD. BEWARE: triple check that you are really selecting the correct (USB) HDD, where you are going to re-install Salix and that no data in that specific (USB) HDD is important (or that you already have a backup of such data).
4_ Once the correct (USB) HDD was selected, go to "Device" menu and "Create a new partition table". The "msdos" type should be the adequate one. Did I mention you should be sure about which (USB) HDD you selected before doing this?
5_ Still in Gparted, create a new FAT32 partition. Apply (please don't skip this “apply” step).
6_ Right click on the new partition just created and select “Format → FAT32”. Apply (please don't skip this “apply” step).
7_ Right click on the new partition just created and select “flags → boot”.
8_ Optionally, right click on the new partition just created and select “label” - > add a new relevant label. Apply (please don't skip this “apply” step).
9_ Right click on the new partition just created and select “Mount”. You can exit Gparted now.
10_ Copy the content of the Salix CD (or the content of the ISO image) onto the new partition of the USB device.
11_ If your new partition in the USB device is “sdb1”; AND
11.A_ you have syslinux version < 4.00, then run:
syslinux -f /dev/sdb1
11.B_ you have syslinux >= 4.00, then run:
syslinux -if /dev/sdb1
12_ If you received any error messages (like for example regarding mounted or unmounted fs), please report back.
13_ If all the steps were performed correctly and no error messages were received, unmount “sdb1”, "safely disconnect" it, log out from Salix, re-connect the USB device and reboot into it.
14_ Please report back.
EDIT: I forgot!!! Since this is a manual copy, you need to create the syslinux.cfg too. In your next post, ask for more info about it if you need it.
EDIT2: Edited very important typos. Sorry
Syslinux is not correctly "installed" (ldlinux.sys is there, but I'm not sure your VBR is pointing to the correct sector location; and syslinux.cfg is not recognized in the expected paths). Are you sure you used LiveClone?
Also, it seems you used FAT16 for that partition. Please use FAT32 for that partition size.
Anyway, here are some manual steps (and they will delete the current info in your USB device).
1_ Boot with your Salix LIVE system (the one you said it is correctly working).
2_ Start Gparted.
3_ Select the appropriate (USB) HDD. BEWARE: triple check that you are really selecting the correct (USB) HDD, where you are going to re-install Salix and that no data in that specific (USB) HDD is important (or that you already have a backup of such data).
4_ Once the correct (USB) HDD was selected, go to "Device" menu and "Create a new partition table". The "msdos" type should be the adequate one. Did I mention you should be sure about which (USB) HDD you selected before doing this?
5_ Still in Gparted, create a new FAT32 partition. Apply (please don't skip this “apply” step).
6_ Right click on the new partition just created and select “Format → FAT32”. Apply (please don't skip this “apply” step).
7_ Right click on the new partition just created and select “flags → boot”.
8_ Optionally, right click on the new partition just created and select “label” - > add a new relevant label. Apply (please don't skip this “apply” step).
9_ Right click on the new partition just created and select “Mount”. You can exit Gparted now.
10_ Copy the content of the Salix CD (or the content of the ISO image) onto the new partition of the USB device.
11_ If your new partition in the USB device is “sdb1”; AND
11.A_ you have syslinux version < 4.00, then run:
syslinux -f /dev/sdb1
11.B_ you have syslinux >= 4.00, then run:
syslinux -if /dev/sdb1
12_ If you received any error messages (like for example regarding mounted or unmounted fs), please report back.
13_ If all the steps were performed correctly and no error messages were received, unmount “sdb1”, "safely disconnect" it, log out from Salix, re-connect the USB device and reboot into it.
14_ Please report back.
EDIT: I forgot!!! Since this is a manual copy, you need to create the syslinux.cfg too. In your next post, ask for more info about it if you need it.
EDIT2: Edited very important typos. Sorry
Re: booting trouble
How did you setup that stick? The stick is definitely broken because of the missing syslinux.cfg and thus syslinux just falls back to loading a default linux kernel from /LINUX, I think.
Re: booting trouble
Thank you Adys. I did all that already, except for the syslinux part - which I imagine is covered by the install script.
Also as regards FAT various types, I tried all of them. This stick is 4 GB so FAT 16 should work, shouldn't it?
In this case, I certainly didn't use LiveClone. I just copied the expanded files from the .iso to the stick and executed the script.
Also as regards FAT various types, I tried all of them. This stick is 4 GB so FAT 16 should work, shouldn't it?
In this case, I certainly didn't use LiveClone. I just copied the expanded files from the .iso to the stick and executed the script.
Re: booting trouble
@ Shador
I wiped it, reformatted, copied the contents of the .iso, executed the install script, and rebooted.
EDIT
The very same .iso from which I successfully booted as a CD.
I wiped it, reformatted, copied the contents of the .iso, executed the install script, and rebooted.
EDIT
The very same .iso from which I successfully booted as a CD.
Re: booting trouble
Unfortunately, no . Well I should explain. The script under Linux uses one specific command for syslinux that may have not worked for your case (in fact, this is very possible). Moreover, the Windows-based script most probably fails when it runs the syslinux installation command.mimosa wrote:I did all that already, except for the syslinux part - which I imagine is covered by the install script.
No!!! You should use FAT32. It is recommended for even much smaller partitions, and surely for 4GB.Also as regards FAT various types, I tried all of them. This stick is 4 GB so FAT 16 should work, shouldn't it?
Since you clearly don't have syslinux.cfg, whatever you tried before has failed.In this case, I certainly didn't use LiveClone. I just copied the expanded files from the .iso to the stick and executed the script.
Re: booting trouble
Well, I can try again after reformatting with FAT32. All I can say is I never had these problems in the past, and I can't remember the exact steps I took (following the instructions). However I still suspect hardware in the case of the USB, and possibly some problrm with Maté.
However, can you explain why I shouldn't use FAT16 to format a 4 GB stick? I thought 4 GB was its limit.
However, can you explain why I shouldn't use FAT16 to format a 4 GB stick? I thought 4 GB was its limit.
Re: booting trouble
You already tried several methods. Since you have no problem deleting the info, I want to be perfectly clear: just re-formatting might work, but I would strongly suggest starting from step 1 above up to step 9 (included). Then reboot again and use LiveClone or unetbootin v.575 (or newer). Do NOT go straight to re-formatting; do all the steps up to #9 included.mimosa wrote:Well, I can try again after reformatting with FAT32.
I must repeat this: BEWARE of the specific (USB) HDD on which you apply your actions!!!
Well, that's why we are using this topic .All I can say is I never had these problems in the past, and I can't remember the exact steps I took (following the instructions). However I still suspect hardware in the case of the USB, and possibly some problrm with Maté.
Let me put it this way. Do you know the difference between theory and practice? In theory, there is none. In practice, there is.However, can you explain why I shouldn't use FAT16 to format a 4 GB stick? I thought 4 GB was its limit.
In theory, you could use 64KiB clusters, but "common" tools don't support it, and many times when such big cluster size is used, it gives more troubles than solutions.
"Common" standard tools can support 32KiB cluster size (which means 2GiB volume size for FAT16), but it is still wasting too much space (saving a file of 2 KiB occupies 32KiB anyway).
Then there is the performance aspect. For most common usage cases, you would find that FAT32 will have better performance than FAT16 when using volumes of more than 1GiB.
And finally, there is the limit for the amount of files. FAT16 will have a limit for the amount of files you can save in the partition much lower than FAT32, even if the partition still has free available space.
I know I am mentioning things without writing scientific or statistical proof, but that would make this post extremely long and would be off-topic. There are (too) many sites with info about FAT, including Wikipedia.
So, in short, for a volume of 4GiB, using FAT32 has mostly advantages over FAT16.
My recommendation would be to start from step #1 up to step #9 and to use FAT32, and then either LiveClone or the latest unetbootin (at least v.575 or newer). For now, avoid the "install-on-USB" scripts. Let us know the results.
Re: booting trouble
Try writing the iso to the stick with dd.
Obviously be very careful that you use your device's name, it doesn't have to be /dev/sdb...
Code: Select all
dd if=salixlive-mate-13.37-32.iso of=/dev/sdb