Yesterday I was happily setting up my newly installed Elyssa-r1 and today it repeatedly showed Busybox when I tried to boot. I feared that my editing of /etc/fstab had been fatal - but not so: after a day of trying to edit from Daryna and failing, it suddenly booted while I was trying to locate an .iso CD to install again! Grub simply timed out on its first option - I normally press Enter.
My screen was as I had set it up yesterday, except that one partition shown in fstab failed to mount. Here is my edited /etc/fstab:
theo@TJT4Elyssa / $ cat /etc/fstab
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
UUID=de22ad7a-2475-42cd-ae63-60c6460ccb74 / ext3 relatime,errors=remount-ro 0 1
UUID=da306c85-75a5-458a-b0cd-27779cb72477 /home ext3 relatime 0 2
UUID=cf721c13-6670-49e3-95a4-ef51eb7787af none swap sw 0 0
UUID=8b0c2f05-167c-4a4f-a0f2-0a0bebb28cfa none swap sw 0 0
UUID=879da11d-4d05-4c1c-8a60-dbc03454f2ac none swap sw 0 0
LABEL=(E)DI8:H7R /media/sdb1 ntfs defaults,umask=007,gid=46 0 1
LABEL=(Q)DI7:H7N /media/sdc2 ntfs defaults,umask=007,gid=46 0 1
LABEL=(R)DI8:H7R /media/sdc3 ntfs defaults,umask=007,gid=46 0 1
LABEL=Backups /media/sdd1 ntfs defaults,umask=007,gid=46 0 1
/dev/scd1 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/scd0 /media/cdrom1 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
and here is the initial state of the system:
theo@TJT4Elyssa / $ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sdb2 4.9G 2.3G 2.4G 50% /
varrun 502M 216K 502M 1% /var/run
varlock 502M 0 502M 0% /var/lock
udev 502M 124K 502M 1% /dev
devshm 502M 52K 502M 1% /dev/shm
lrm 502M 38M 464M 8% /lib/modules/2.6.24-16-generic/volatile
/dev/sdb4 30G 489M 28G 2% /home
/dev/sdb1 41G 23G 18G 56% /media/sdb1
/dev/sdc2 41G 18G 23G 45% /media/sdc2
/dev/sdc3 41G 23G 18G 56% /media/sdc3
gvfs-fuse-daemon 4.9G 2.3G 2.4G 50% /home/theo/.gvfs
which shows that /dev/sdd1 failed to mount,although it is called by /fstab.
[This is an ntfs partition; it has no label apart from that allocated in /fstab. The other labelled partitions had their labels created in Windows - no longer possible. Of course, the command e2label only works for ext2 & ext3 formats]
Since booting today I have mounted that partition - it now shows on the screen as 43.5 GB Media, and evidently "belongs" to me as I can edit it. But its Properties show it as a folder, the Perkissions tab shows: "The permissions of sdd1 could not be determined", and under the Volume tab the following appear: "Label: (blank), Size: 40.5 GB, Media: Hard Disk, UUID: 2044A85E4B03DE64" (typical for an ntfs partition), "File System: ntfs (3.1), Mount Point: /media/sdd1, File System: fuseblk. Mount Options: rw nosuid nodev noatime relatime user_id=0 group_id=0 allow_other, Settings" [All boxes blank]
BTW, I had to mkdir /media/sdd1 again although I had already done that yesterday.
I shall be most grateful for advice about getting this setup to behave as I want; also, most important, how do I avoid repeated Busybox appearances? Can I use any of the Busybox commands to resume booting? Is my difficulty related to those Mount Options? Where can I learn about changing them if so?
I've just looked in Linux Mint Wiki, and the only reference is in a post about True Crypt: "It appears that using the sync mount option (typing "sync" in the mount options field under preferences) prevents the stall, the transfer speed however gets pretty bad."
The HDs are b,c & d instead of a,b & c: I haven't seen anyone else commenting on this. To me it seems to be an illogical and annoying change. Why has it happened?