Linux User Group ( LUG ) - Cebu

[CentOS]

---

@benicio - unsay mogawas kung mag fdisk -l ka?

Can you also post your fstab?

[benicio]

root@benicio-ubuntu:/home/benicio# fdisk -l 

Disk /dev/sda: 20.1 GB, 20060135424 bytes
255 heads, 63 sectors/track, 2438 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0006c200

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1         131     1052226   82  Linux swap / Solaris
/dev/sda2   *         132        1175     8385930   83  Linux
/dev/sda3            1176        1958     6289447+  83  Linux
/dev/sda4            1959        2438     3855600   83  Linux
root@benicio-ubuntu:/home/benicio#

benicio@benicio-ubuntu:/etc$ cat fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
/dev/sda2       /               ext3    errors=remount-ro 0       1
# swap was on /dev/sda1 during installation
UUID=95566475-ad56-47e5-86b8-43aa35e8c8e7 none            swap    sw              0       0
benicio@benicio-ubuntu:/etc$

pero kung mag insert ko ug usd drive madetect ani.

[CentOS]

Wait, imong gusto makita sad sa df nga command ang slack nga partition? fdisk sees all disks, it's just not mounted because based on your fstab, only / on Ubuntu (sda2) is mounted. You need to add the other partitions as well. Also, use defaults,errors=remount-ro under options.

It's also safer to use UUID when mounting drives, so you might want to do that too.

[benicio]

thanks CentOS

murag naa y error gamay.. pero mamount na nako

benicio@benicio-ubuntu:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
/dev/sda2 / ext3 errors=remount-ro 0 1
/dev/sda3 /media/sda3 ext4 defaults 1 1
/sda4 /media/sda4 ext2 defaults 1 2
# swap was on /dev/sda1 during installation
UUID=95566475-ad56-47e5-86b8-43aa35e8c8e7 none swap sw 0 0

unsay buot pasabot anang error sa readonly sa sda2?
unsay maayu ani para way errors?

[CentOS]

Do a force check on your disk, naa diha imong problem.

errors=remount-ro tells the system that if it sees disk errors during boot, it will remount your directory (which in your case is /) as a Read Only file system.

You can actually remove errors=remount-ro on your fstab, then you will not be mounted as RO, but that just means na your ignoring the fact that your disk itself might be having problems and would probably worsen in the future if not attended to as early as possible.

[benicio]

okay na.
makuha na nako ang mga files sa /home sa slack to ubuntu thanks

[CentOS]

Anytime

[waterboy0911]

Thanks CentOS..

pati ako nakat.on.. hehehe

and sorry guys wala ko ka post sa first page..

dili lang sa ta mag meet karon kay medyo ting bitay karon..

[darkhero]

It's also safer to use UUID when mounting drives, so you might want to do that too.

i don't know what's the meaning of being safer pero murag equal ra man kung UUID ang gamiton versus specifying the exact path sa fstab. murag ang purpose sa UUID kay more on convenience man tingali, not on safety2x.

for example kung ang hdd kay naka-primary master, then imo siya i-balhin to primary slave. mausab na ang path sa block device, from hda/sda to hdb/sdb, so mas convenient kung UUID ang gamiton sa fstab para bisan asa pa siya ibalhin, ma-mount ra jafon ang intended filesystem ana nga hdd, di na kinghanlan i-edit utro ang fstab kay UUID nman ang gigamit, not the block device path.

[CentOS]

Safer is probably the wrong word, but rather "better".. well, in some scenarios.

- There's been some issues on using labels versus UUID's specially with systems with multiple USB drives. Dev names are assigned based on the order of loading the kernel modules during boot time and this automatic assignment are sometimes inconsistent... making your labels look different if you boot with one of your USB flash drives attached and then reboot after you've removed that flash drive.

- Labels doesn't work well when you are on a SAN setup because it's very prone to acquire duplicate names. Labels are mostly used on local machines to mount local drives like /boot.

These are just 2 of the most common reasons why UUID in some scenarios are better than labels, there's probably more. Even new Ubuntu releases are based on UUID's instead of Labels, otherwise, they would have stuck with labels.